<div>
You can try:<br />
<br />
RewriteCond %{HTTPS} on<br />
RewriteCond %{REQUEST_URI}<br />
RewriteRule ^(.*)$ <a href="http://%" rel="ugc nofollow">http://%</a>{HTTP_HOST}%{REQUEST_URI} [R=301,L]<br />
<br />
Jeff
</div>


<div>
You need a SSL. You can get them pretty cheaply or even use a self signed SSL. Self signed SSL would probably create some sort of warning.<br />
<br />
Godaddy SSL - <a href="http://www.godaddy.com/ssl/ssl-certificates.aspx" rel="ugc">http://www.godaddy.com/ssl/ssl-certificates.aspx</a><br />
<br />
Apache self signed SSL - <a href="http://www.akadia.com/services/ssh_test_certificate.html" rel="ugc">http://www.akadia.com/services/ssh_test_certificate.html</a>
</div>


<div>
Note that some hosts give out a shared SSL for the server<br />
<br />
<a href="https://my.bluehost.com/cgi/help/126" rel="ugc">https://my.bluehost.com/cgi/help/126</a>&nbsp;- Bluehost shared SSL Certificate
</div>


<div>
Yes, you can do it via the rewrite engine, Here's an example of this..<br />
This is assuming you've got a standard *nix-Apache configuration where https uses port 443...<br />
<br />
<b>CODE</b><br />
<i>Options +FollowSymlinks<br />
RewriteEngine on<br />
RewriteCond %{SERVER_PORT} ^443$<br />
RewriteRule ^(.*)$ <a href="http://www.yourdomain.com/$1" rel="ugc">http://www.yourdomain.com/$1</a>&nbsp;[R=301,L]</i>
</div>


<div>
Why use port when you can use a check on https?
</div>


<div>
The rewrite options noted above are along the lines of what I've tried before, and they aren't working. It seems that any directive that is aimed at https or its port are not being processed before it checks for the SSL and errors out.<br />
<br />
I currently don't have the access to check their control panel or create an SSL, so am trying to work via the .htaccess file.
</div>


<div>
apache has to be setup to allow overrides<br />
<br />
<a href="http://httpd.apache.org/docs/2.0/mod/core.html#allowoverride" rel="ugc">http://httpd.apache.org/docs/2.0/mod/core.html#allowoverride</a><br />
<br />

<blockquote>
When this directive is set to None, then .htaccess files are completely ignored.
</blockquote>
<br />
<a href="http://www.yolinux.com/TUTORIALS/ApacheRedirect.html" rel="ugc">http://www.yolinux.com/TUTORIALS/ApacheRedirect.html</a><br />
<br />

<pre><code class="code-1 nolinks" id="code-20-38146329-1"><span>1	&lt;Directory /root-directory-of-web-site-to-be-redirected&gt;</span>
<span>2	AllowOverride All</span>
<span>3	&lt;/Directory&gt;</span>
</code></pre>
</div>


<div>
Apache is already handling other redirects via mod_rewrite, so it's not being ignored.
</div>


<div>
OK so it just doesn't redirect <a href="http" rel="ugc">http</a>: to <a href="https" rel="ugc">https</a>: ?<br />
<br />
If so check all your redirects to see if there is another rule effecting <a href="http" rel="ugc">http</a>:
</div>


<div>
No, per my original post, it's not redirecting https to http.
</div>


<div>
what rule in htaccess are you using to redirect https to http?
</div>


<div>
David,<br />
<br />
I tested my solution above on my server and could only find one circumstance where it did not work properly. That was if the request was going from a URL with www.mydomain.com&nbsp;to one with mydomain.com. I don't have the time at the moment to test trying a rule prior to the https rule to force the www, but that might work. You can also find good reading here:<br />
<br />
<a href="http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html" rel="ugc">http://httpd.apache.org/do<wbr />cs/2.0/mod<wbr />/mod_rewri<wbr />te.html</a>
</div>


<div>
@mtputers - I tried your script on another domain I control with a clean .htaccess file and it didn't work either. I get a &quot;Error 107 (net::ERR_SSL_PROTOCOL_ERR<wbr />OR): SSL protocol error.&quot; in both circumstances. From what I can see, it looks like the http request is being nixed because of the SSL before the .htaccess can even trigger.
</div>


<div>
Hi David,<br />
<br />
I have fixed the Error 107 Protocol Error on other computers when they have incorrect security settings. Can you verify that you have SSLv3 and TLSv1.0 checked and all others unchecked under the advanced tab (IE) and in options-&gt;under the hood (chrome). <br />
<br />
Not saying this the absolute fix, but worth checking. I will keep working on this and see if I can't come up with a better solution. Strange that I had no issues on my server with a domain that does not have an SSL installed.<br />
<br />
Can I ask you what kind of control panel you atre using?<br />
<br />
Jeff
</div>


<div>
Per my earlier post:<br />
<br />

<blockquote>
I currently don't have the access to check their control panel or create an SSL, so am trying to work via the .htaccess file.
</blockquote>
<br />
And yes, have the SSL setting set as such in Google Chrome.
</div>


<div>
I would contact the host to see what's going on with the http redirect.
</div>


<div>
David,<br />
<br />
I would totally agree with Number-1. Without access to the control panel, we are just taking shots in the dark. It does sound as if something is over-riding the .htaccess. I was able to use my code above on 3 different servers running different control panels and they all worked just fine. If they are running Plesk, simply turning off SSL support in older versions should achieve this quite easily without additional coding. There are just too many variables to take into consideration without even knowing what brand of control panel they use, let alone not having access to it.<br />
<br />
Jeff
</div>


<div>
<div class="content wysiwyg-content">
I wanted to see if it was possible using an .htaccess to redirect page requests from the https address to the http version. &nbsp;So <a href="https://www.example.com/page" rel="ugc">https://www.example.com/page</a>&nbsp;would instead go to <a href="http://www.example.com/page" rel="ugc">http://www.example.com/page</a>.<br />
<br />
I have tried many proposed solutions without success. The site does not have an SSL in place, so I don't know if that means it won't work without it, or if I'm doing something wrong.
</div>
</div>


I wanted to see if it was possible using an .htaccess to redirect page requests from the https address to the http version.  So https://www.example.com/page would instead go to http://www.example.com/page.

I have tried many proposed solutions without success. The site does not have an SSL in place, so I don't know if that means it won't work without it, or if I'm doing something wrong.

Apache redirect https to http

The Apache HTTP Server is a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards. Typically Apache is run on a Unix-like operating system, but it is available for a wide variety of operating systems, including Linux, Novell NetWare, Mac OS-X and Windows. Released under the Apache License, Apache is open-source software.

Apache Web Server

A web server refers to the software that helps to deliver web content that can be accessed either through the Internet or through an intranet. The primary function of a web server is to store, process and deliver web pages to clients. The communication between client and server takes place using the Hypertext Transfer Protocol (HTTP). The most common use of web servers is to host websites, but there are other uses such as gaming, data storage, running enterprise applications, handling email, FTP, etc.