First, using those multiple domains requires several DNS lookups. You’d be better off combining many of those images into a sprite instead of spreading the requests. Second, when I load your page, I see most of the blocking (~1.25s) on all.js. I see that begins with (an old version of) jQuery. You should reference that … Read more
In case you are on Ubuntu, edit the file /etc/apache2/apache2.conf (here we have an example of /var/www): <Directory /var/www/> Options Indexes FollowSymLinks AllowOverride None Require all granted </Directory> and change it to; <Directory /var/www/> Options Indexes FollowSymLinks AllowOverride All Require all granted </Directory> then, sudo service apache2 restart You may need to also do sudo … Read more
Change your configuration to this (add a slash): RewriteCond %{HTTP_HOST} ^example.com$ [NC] RewriteRule (.*) http://www.example.com/$1 [R=301,L] Or the solution outlined below (proposed by @absiddiqueLive) will work for any domain: RewriteEngine On RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L] If you need to support http and https and preserve the protocol choice try the following: … Read more
I have actually followed this example and it worked for me 🙂 NameVirtualHost *:80 <VirtualHost *:80> ServerName mysite.example.com Redirect permanent / https://mysite.example.com/ </VirtualHost> <VirtualHost _default_:443> ServerName mysite.example.com DocumentRoot /usr/local/apache2/htdocs SSLEngine On # etc… </VirtualHost> Then do: /etc/init.d/httpd restart
RewriteBase is only applied to the target of a relative rewrite rule. Using RewriteBase like this… RewriteBase /folder/ RewriteRule a\.html b.html is essentially the same as… RewriteRule a\.html /folder/b.html But when the .htaccess file is inside /folder/ then this also points to the same target: RewriteRule a\.html b.html Although the docs imply always using a … Read more
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]
For Laravel 5: Rename server.php in your Laravel root folder to index.php Copy the .htaccess file from /public directory to your Laravel root folder. That’s it!
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