Tomblog603

1. Apache Rewriterule Http To Https
2. Apache 2.4 Redirect Http To Https Mod_rewrite
3. Apache Rewriteengine Http To Https

1. The main difference is that RewriteRule is handled by modrewrite, whereas Redirect is handled by modalias. Uses RewriteRule and RewriteCond. Much more powerful, since it uses regular expressions to match and replace URLs. Can be more difficult to use. Might not be installed or enabled by default.
2. HTTP connections can be redirected to HTTPS using the apache modrewrite module. Modrewrite should be available in every apache installation. Apache HTTP to HTTPS Redirect. Create a file with the name.htaccess in the website root directory which contains the following lines.
3. What is modrewrite? HostGator uses Apache, the open source HTTP server software, to host your website. Apache can be customized via modules, and the modrewrite module is available for you to use yourself. Modrewrite can redirect one URL to another URL, rewrite requested URLs, limit access to your site and much more.

Apache’s modrewrite makes it easy to require SSL to be used on your site and to gently redirect users who forget to add the https when typing the URL. Using Apache to redirect http to https will make sure that your site (or a part of it) will only be accessed by your customers using SSL.

To automatically redirect all requests from HTTP to HTTPS you can use Apache's mod_rewrite module. This is a good solution to force your site visitors to use SSL. Besides this, you can also apply this solution on most shared hosting plans where you have access to the htaccess file.

I was reading through the Apache documentation the other day as part of work on one of my pet projects (Thumber.co) and came across the following little tidbit (emphasis added).

mod_rewrite should be considered a last resort, when other alternatives are found wanting. Using it when there are simpler alternatives leads to configurations which are confusing, fragile, and hard to maintain.

Apache Rewriterule Http To Https

–Apache docs

Apache 2.4 Redirect Http To Https Mod_rewrite

Well, this got me thinking. I was in the process of updating Thumber to have everything redirect to HTTPS with no WWW prefix. I had implemented this functionality with mod_rewrite, but after reading the above I felt like making this better so I set out to convert redirects to use the basic Redirect directive, as provided by mod_alias.

My mod_rewrite starting point before any changes looked something like the following:

With the above, if the HTTP virtual host was hit, it would redirect to the non-WWW HTTPS equivalent path. If the HTTPS virtual host was hit and www.thumber.co was the host then it would redirect to thumber.co. This seemed pretty clean as far as mod_rewrite go, but its still mod_rewrite. The following is what I came up with as a replacement.

Apache Rewriteengine Http To Https

Much more straightforward! The only gotcha in the above is that the If directive is new to Apache 2.4. If you’re running an older version, you may still be stuck with mod_rewrite for the HTTPS virtual host, though the HTTP virtual host could still use the Redirect directive in an older Apache version.