Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why is Apache Permanent Redirect removing the slash between the domain and the path?

Tags:

I'm using Apache 2.4, and I set up two virtual directories. One requires SSL, and the other one redirects to it.

If a user attempts to visit https://www.derp.com/derp without /derp existing, they correctly get a 404. But when a user visits http://www.derp.com/derp, Apache incorrectly redirects the user to https://www.derp.comderp, removing the slash between the path and the domain name.

I have no idea what would be causing this.

The following is the setup of my Virtual Host.

<VirtualHost *:443>     ServerAdmin [email protected]     ServerName www.derp.com     ServerAlias derp.com     DocumentRoot "C:\Users\derp\Documents\Web Projects\derp"     SSLEngine on     SSLCertificateFile "C:\Apache24\certs\cert.cer"     SSLCertificateKeyFile "C:\Apache24\certs\key.key" </VirtualHost>  <VirtualHost *:80>     ServerAdmin [email protected]     ServerName www.derp.com     ServerAlias derp.com     Redirect permanent / https://www.derp.com/ </VirtualHost>  <Directory "C:\Users\derp\Documents\Web Projects\derp">     Options Indexes FollowSymLinks Includes ExecCGI     AllowOverride All     Require all granted     SSLRequireSSL </Directory> 

Why would Apache be behaving this way?

Bonus Question: Should redirects be handled in my virtual host definition, or should it be handled in the .htaccess file in the web site's physical directory?


Edit:

I'm starting a Laravel project, and by default the public folder does contain a .htaccess file, so here's that guy:

<IfModule mod_rewrite.c>     Options -MultiViews     RewriteEngine On     RewriteCond %{REQUEST_FILENAME} !-d     RewriteCond %{REQUEST_FILENAME} !-f     RewriteRule ^ index.php [L] </IfModule> 

Edit Two:

I tried:

  • adding a slash at the end of the DirectoryRoot path
  • replacing the backslashes with forward slashes in the DirectoryRoot path
  • replacing the backslashes with double backslashes in the DirectoryRoot path

I also removed the .htaccess file from the directory completely.

It redirects correctly when you go from http://www.derp.com to https://www.derp.com. It's just when you specify a path and attempt https that it removes the slash between the domain and the path.


Edit Three:

I also attempted the following suggestion:

Redirect permanent / https://www.derp.com/  Try  RedirectMatch permanent /(.*) https://www.derp.com/$1  or  RedirectMatch permanent (.*) https://www.derp.com/$1 

... and instead of redirecting to https://www.derp.comderp, it instead does not redirect, attempts and gives a 404 for http://www.derp.com/derp, but using Apache's 404, instead of throwing a Not Found Exception, as Laravel does without configuration.


Edit Four:

I have also tried:

<IfModule mod_rewrite.c>     Options -MultiViews     RewriteEngine On     RewriteBase /     RewriteRule ^index\.php$ - [L]     RewriteCond %{REQUEST_FILENAME} !-f     RewriteCond %{REQUEST_FILENAME} !-d     RewriteRule . /index.php [L] </IfModule> 

In the .htaccess file and the behavior did not change at all.

like image 515
Nathan Lutterman Avatar asked Nov 18 '13 07:11

Nathan Lutterman


People also ask

How does Apache redirect work?

Using the Redirect Directive In Apache, you can implement single-page redirects using the “Redirect” directive, which is included in the mod_alias module that is enabled by default. This directive takes at least two arguments: the old URL and the new URL.

What is Apache 301 redirect?

htaccess 301 redirect is a server side redirect and is a permanent redirect. The . htaccess file is an Apache server configuration file.


2 Answers

I got it.

The issue did not lay with the rewriting at all, it was the SSLRequireSSL directive under my Directory definition that was causing the problem.

I simply removed this directive, refreshed the cache in all of my browsers, and the site then continued to work correctly. This was discovered through the process of elimination.

The documentation notes:

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 is present all requests are denied which are not using SSL.

The emphasis is my own. SSLRequireSSL may have Apache only return a 403 or 404 if HTTP over SSL is not enabled, interfering with the Redirect rule. A rewrite rule such as the one in this answer on Server Fault may be a better alternative depending on your use case:

RewriteEngine On RewriteCond %{SERVER_PORT} !443 RewriteRule ^(/(.*))?$ https://%{HTTP_HOST}/$1 [R=301,L] 
like image 107
Nathan Lutterman Avatar answered Oct 26 '22 16:10

Nathan Lutterman


My issue was related to browser caching.

I tried it in a different browser and it worked and then tried again in a private session in the first browser and it also worked.

like image 25
Kevin Sheehan Avatar answered Oct 26 '22 17:10

Kevin Sheehan