Forcing HTTP in .htaccess

Question

I am trying to force my site to redirect from https to http, most of the tutorials out there do the opposite (force http to https), the few one's that I have come across haven't worked for me so far.

This is what my .htaccess file looks like right now

    RewriteEngine On 
    RewriteCond %{SERVER_PORT} 80 
    RewriteRule ^(.*)$ https://www.example.com/$1 [R,L]

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

    # END WordPress

Any of the answers below will work. Just replace one of them with your own and refresh your cache. — Joe, Jan 26 '17 at 12:48

score 1 · Answer 1 · answered Jan 26 '17 at 12:42

1

Use this to force HTTPs:

RewriteEngine On

RewriteCond %{HTTPS} !=on
RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [R,L]

Make sure you clear your cache before testing this.

answered Jan 26 '17 at 12:42

Joe

4,877
5
30
51

I got a response of "example.com redirected you too many times" – TobiSkillZ Jan 26 '17 at 13:23

score 1 · Answer 2 · answered Jan 26 '17 at 12:44

1

Use this to force to http:

RewriteEngine on
RewriteCond %{HTTPS} on 
RewriteRule ^ http://%{HTTP_HOST}%{REQUEST_URI} [NE,L,R=301]

answered Jan 26 '17 at 12:44

Croises

18,570
4
30
47

I got a response of "example.com redirected you too many times" – TobiSkillZ Jan 26 '17 at 13:23
Do you use HSTS, or proxy server (cloud) ? – Croises Jan 26 '17 at 13:59
Have you replaced your first 3 lines with these lines, and cleared the cache? – Croises Jan 26 '17 at 14:15

score 1 · Answer 3 · edited May 23 '17 at 12:09

1

You do exactly the opposite, namely if it comes from HTTP

RewriteCond %{SERVER_PORT} 80

redirect to HTTPS

RewriteRule ^(.*)$ https://www.example.com/$1 [R,L]

Remove these two lines and replace with the following.

First, you should not check for the port, but for %{HTTPS}, which is more reliable, e.g.

RewriteCond %{HTTPS} on

next redirect to HTTP (note the missing s)

RewriteRule ^(.*)$ http://www.example.com/$1 [R,L]

When everything works as it should, you may replace R with R=301. Never test with R=301.

edited May 23 '17 at 12:09

Community

1
1

answered Jan 26 '17 at 12:47

Olaf Dietsche

72,253
8
102
198

Much better answer. – Joe Jan 26 '17 at 12:48
I got a response of "example.com redirected you too many times" – TobiSkillZ Jan 26 '17 at 13:23
This could happen, when you keep the original rules in addition to the new ones. Then it will redirect from HTTPS to HTTP, the browser will request HTTP, and again will be redirected from HTTP to HTTPS, and so on. – Olaf Dietsche Jan 26 '17 at 14:36

Forcing HTTP in .htaccess

3 Answers3