Web Hosting Talk : Web Hosting Main Forums : Programming Discussion : HTTP to HTTPS Redirect

[n0ts0smart]

Hi folks,

I had a script coded in CakePHP and I have just installed the SSL Cert on my particular page. I'm trying to create an HTTP to HTTPS redirect using the .htaccess file, but I only see the redirect on Google Chrome because Chrome automatically looks for the HTTPS. On all of the other browswers my redirect doesn't work.

My current .htaccess file looks like this:

# php_value memory_limit 256M

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteRule ^$ app/webroot/ [L]
RewriteRule (.*) app/webroot/$1 [L]
</IfModule>

-------------------------------------

I have tried using the following and variations of the following and nothing seems to work:

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

-------------------------------------

Any suggestions?

[fabin]

Try changing the condition to

RewriteCond %{HTTPS} off

[n0ts0smart]

Originally Posted by fabin

Try changing the condition to

RewriteCond %{HTTPS} off

That still doesn't work. It just sends the domain to http://www.domainname.com, not https://www.domainname.com.

[fabin]

write it above all existing rewrite rules

[n0ts0smart]

Originally Posted by fabin

write it above all existing rewrite rules

I'm still getting the same result. Just sends me to http://www.domain....

[foobic]

1. Clear your browser cache after each .htaccess edit - redirects can and will be cached.
2. Try a redirect to somewhere else (eg. http://google.com/?q=$1) just to make sure the rule is firing at all.

Also,

Originally Posted by n0ts0smart

My current .htaccess file looks like this:

# php_value memory_limit 256M

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteRule ^$ app/webroot/ [L]
RewriteRule (.*) app/webroot/$1 [L]
</IfModule>

that looks like a recipe for an endless rewrite loop (request -> app/webroot/request -> app/webroot/app/webroot/request etc). You'd normally use a condition before that last rule, something like:

RewriteCond %{REQUEST_FILENAME} !-f

I'd wonder if mod_rewrite (and / or .htaccess) is actually disabled, except that presumably the site wouldn't work without this rule?