<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gravity Support Forums Topic: SSL certificate, upload, location, destination,</title>
		<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination</link>
		<description>Gravity Support Forums Topic: SSL certificate, upload, location, destination,</description>
		<language>en-US</language>
		<pubDate>Mon, 20 Apr 2026 03:26:01 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.1</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>https://legacy.forums.gravityhelp.com/search.php</link>
		</textInput>
		<atom:link href="https://legacy.forums.gravityhelp.com/rss/topic/ssl-certificate-upload-location-destination" rel="self" type="application/rss+xml" />

		<item>
			<title>Chris Hajer on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-77029</link>
			<pubDate>Sun, 23 Sep 2012 21:44:11 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">77029@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;OK, thank you for the update.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Joseph on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-77004</link>
			<pubDate>Sun, 23 Sep 2012 17:37:19 +0000</pubDate>
			<dc:creator>Joseph</dc:creator>
			<guid isPermaLink="false">77004@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;As you suggested. Also placed a username password on the folder!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-76947</link>
			<pubDate>Sun, 23 Sep 2012 02:15:57 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">76947@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;How did you resolve the problem Joseph?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Joseph on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-76915</link>
			<pubDate>Sat, 22 Sep 2012 23:31:46 +0000</pubDate>
			<dc:creator>Joseph</dc:creator>
			<guid isPermaLink="false">76915@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Just to say this is sorted now!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-75503</link>
			<pubDate>Sat, 15 Sep 2012 12:36:22 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">75503@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;The syntax looks OK.  I would put your rules right where blank line 2 is in the default WordPress .htaccess file.&#60;/p&#62;
&#60;p&#62;It's possible your host does not support these overrides in an .htaccess file.  You will need to contact your host or look at the Apache error logs to see what the problem is that is causing the 500 Internal Server error.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Joseph on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-75409</link>
			<pubDate>Fri, 14 Sep 2012 18:23:28 +0000</pubDate>
			<dc:creator>Joseph</dc:creator>
			<guid isPermaLink="false">75409@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi Chris,&#60;/p&#62;
&#60;p&#62;I pasted...&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteCond %{REQUEST_URI} wp-content/uploads/gravity_forms
RewriteRule ^(.*)$ &#38;lt;a href=&#38;quot;https://example.com/wp-content/uploads/gravity_forms/$1&#38;quot; rel=&#38;quot;nofollow&#38;quot;&#38;gt;https://example.com/wp-content/uploads/gravity_forms/$1&#38;lt;/a&#38;gt; [R,L]&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;but replacing the  the URL with my domain and wordpress install folder.&#60;/p&#62;
&#60;p&#62;However I get an internal server error.&#60;/p&#62;
&#60;p&#62;this is currently what my .htaccess file looks like&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;DirectoryIndex index.php

# BEGIN WordPress
&#38;lt;IfModule mod_rewrite.c&#38;gt;
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
&#38;lt;/IfModule&#38;gt;

# END WordPress&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;where exactly should it go so I so I don't get the internal error?&#60;/p&#62;
&#60;p&#62;I think I'm being lame here
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Joseph on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-73693</link>
			<pubDate>Mon, 03 Sep 2012 16:53:29 +0000</pubDate>
			<dc:creator>Joseph</dc:creator>
			<guid isPermaLink="false">73693@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;cheers chris!&#60;/p&#62;
&#60;p&#62;i will have a go.... I'm doing too many things here&#60;/p&#62;
&#60;p&#62;(rolling of eyes)
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-73682</link>
			<pubDate>Mon, 03 Sep 2012 16:17:00 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">73682@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;There is a lot to it, but I did it on an installation I have in about 30 minutes or so, including the form.  So, for a competent systems administrator, it should not take too long.  On shared hosting, it might take longer to accomplish, depending on the support you receive.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Joseph on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-73678</link>
			<pubDate>Mon, 03 Sep 2012 15:11:41 +0000</pubDate>
			<dc:creator>Joseph</dc:creator>
			<guid isPermaLink="false">73678@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Will have a look and try. Phew thats a long one.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "SSL certificate, upload, location, destination,"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ssl-certificate-upload-location-destination#post-73669</link>
			<pubDate>Mon, 03 Sep 2012 13:37:45 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">73669@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Protecting the uploads is not part of Gravity Forms.  However, you can do a couple things:&#60;/p&#62;
&#60;p&#62;1. You can force all access to the upload folder to be via https/SSL by adding this to your .htaccess file:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteCond %{REQUEST_URI} wp-content/uploads/gravity_forms
RewriteRule ^(.*)$ &#60;a href=&#34;https://example.com/wp-content/uploads/gravity_forms/$1&#34; rel=&#34;nofollow&#34;&#62;https://example.com/wp-content/uploads/gravity_forms/$1&#60;/a&#62; [R,L]&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;That will work if your host allows that type of override in an .htaccess file.  That will force any access to that folder via http to be redirected over https.  That protects the request during transit.&#60;/p&#62;
&#60;p&#62;2.  You can change the upload directory with the gform_upload_path filter: &#60;a href=&#34;http://www.gravityhelp.com/documentation/page/Gform_upload_path&#34; rel=&#34;nofollow&#34;&#62;http://www.gravityhelp.com/documentation/page/Gform_upload_path&#60;/a&#62;  That will put uploads into a new directory for you.  If you do that, the information in item 1 above will need to be adjusted to the new location and URL.&#60;/p&#62;
&#60;p&#62;3.  However, none of that will prevent someone with the URL from accessing the document directly.  They would just be directed to a secure connection and the download would continue. You can however, protect the upload directory with Apache Basic Authentication, which will force the visitor to log in with a username and password before they can download the file.  You can read more about Apache Basic Authentication here: &#60;a href=&#34;http://www.rahul.net/howto/basicauth.html&#34; rel=&#34;nofollow&#34;&#62;http://www.rahul.net/howto/basicauth.html&#60;/a&#62;  There are a lot of tutorials online.  There are two parts to it.  Create the .htpasswd file, and create the .htaccess file.  The .htaccess file will go in the upload directory for the form, and will look like this:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;Options -Indexes
AuthName &#38;quot;Protected Upload Directory&#38;quot;
AuthType Basic
AuthUserFile /path/on/server/to/file/htdocs/.htpasswd
require valid-user&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;And then in the file /path/on/server/to/file/htdocs/.htpasswd you will store the authentication information.&#60;/p&#62;
&#60;p&#62;This basic auth does not interfere with the uploads, just the access over http (and https).&#60;/p&#62;
&#60;p&#62;It's a worthwhile customization but will take a bit of work and the help of your system administrator maybe.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
