Apache Redirect – All Requests to HTTPS WWW

apache-2.2redirect

This question has been asked, but I'm not finding the solution. I have very little apache experience. I need to set up my server to take the following requests

http://, http://www. and https:// and convert them to https://www.

So far this is what I have that is sorta working.

RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

However, it puts an extra www. in front of the url when I type http://www.domain.com (so it ends up looking like this in the url https://www.www.domain.com). What do I need to do to get this to work properly? And, I'm placing this in the global configuration edit config file httpd.conf. Is this the right place? It looks like I could possibly place it on the virtual host edit directive file, but I'm not sure? Again, I pretty new at apache. Thanks for any help.

Best Answer

This will work

RewriteEngine on

# redirect all http -> https
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteCond %{HTTP_HOST} ^([a-z.]+)$ [NC]
RewriteRule ^/(.*)$ https://www.%1/$1 [R=301,L]

First section is what you have which is fine for http->https

Next section

First line will ignore www second line will ignore if they input an ip address (can remove if you want) third does the redirect.

Related Solutions

Redirect all non-www subdomains to main www domain with Apache2

I'm no Apache expert, but have considered changing:

ServerName www.domain.com
ServerAlias domain.com domain2.com domain3.com *.domain.com *.domain2.com *.domain3.com

edit: On rereading the OP, it looks like you're already configuring www.domain.com in a different file, which I don't believe is allowed. That, however, may be part of the problem. If I'm following you correctly, the www.domain.com response is from that file, not the config posted here.

NGINX Redirect – How to Rewrite All HTTP Requests to HTTPS While Maintaining Sub-Domain

Correct way in new versions of nginx

Turn out my first answer to this question was correct at certain time, but it turned into another pitfall - to stay up to date please check Taxing rewrite pitfalls

I have been corrected by many SE users, so the credit goes to them, but more importantly, here is the correct code:

server {
       listen         80;
       server_name    my.domain.com;
       return         301 https://$server_name$request_uri;
}

server {
       listen         443 ssl;
       server_name    my.domain.com;
       # add Strict-Transport-Security to prevent man in the middle attacks
       add_header Strict-Transport-Security "max-age=31536000" always; 

       [....]
}

Best Answer

Related Solutions

Redirect all non-www subdomains to main www domain with Apache2

NGINX Redirect – How to Rewrite All HTTP Requests to HTTPS While Maintaining Sub-Domain

Correct way in new versions of nginx

Related Topic