For Apache, you can use mod_ssl to force SSL with the SSLRequireSSL Directive: This directive forbids access unless HTTP over SSL (i.e. HTTPS) is enabled for the current connection. This is very handy inside the SSL-enabled virtual host or directories for defending against configuration errors that expose stuff that should be protected. When this directive … Read more
The below answer could potentially cause an infinite redirect loop… Here, this one redirects everything after the domain name on the URL to the exact same copy on the new domain URL: RewriteEngine on RewriteRule ^(.*)$ http://www.newdomain.com/ [R=301,L] www.example.net/somepage.html?var=foo redirects to: www.newdomain.com
You can use a rewrite rule that uses ^$ to represent the root and rewrite that to your /store directory, like this: RewriteEngine On RewriteRule ^$ /store [L]
Here are a few additional tips on testing rules that may ease the debugging for users on shared hosting 1. Use a Fake-user agent When testing a new rule, add a condition to only execute it with a fake user-agent that you will use for your requests. This way it will not affect anyone else … Read more
To first force HTTPS, you must check the correct environment variable %{HTTPS} off, but your rule above then prepends the www. Since you have a second rule to enforce www., don’t use it in the first rule. RewriteEngine On RewriteCond %{HTTPS} off # First rewrite to HTTPS: # Don’t put www. here. If it is … Read more
In order to use mod_rewrite you can type the following command in the terminal: sudo a2enmod rewrite Restart apache2 after sudo /etc/init.d/apache2 restart or sudo service apache2 restart or as per new unified System Control Way sudo systemctl restart apache2 Then, if you’d like, you can use the following .htaccess file. <IfModule mod_rewrite.c> RewriteEngine On … Read more