0

This is the weirdest problem I have encountered. I am using mod_rewrite in .htaccess in Apache/2.2.13 (Linux/SUSE), and it appears to not be called when there is no trailing slash in the URL. I tested by putting garbage in the .htaccess file, and only received 500 errors when the trailing slash was added, but 404 when omitted. I honestly have no idea why. 

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} -s [OR]
RewriteCond %{REQUEST_FILENAME} -l [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^.*$ - [NC,L]
RewriteRule ^.*$ index.php [NC,L]

/name fails with 404
/name/ is successful
user843739
  • 1
  • 1
  • Please provide your rules/.htaccess; example of problematic URL. Most likely it is your rule .. or some other Apache settings. – LazyOne Jul 14 '11 at 17:29
  • Is there a file or directory named /name/? Also, it seems like you want to match any URI -- if so, `^` as the pattern should suffice. – Dan Grossman Jul 14 '11 at 17:58
  • There is no directory "/name". The real issue is that the entire rewrite is not even executed when the trailing / is missing. – user843739 Jul 14 '11 at 18:07
  • How much control do you have over Apache? Can you edit config files (httpd.conf, httpd-vhost.conf)? If yes -- enable rewrite debugging (`RewriteLogLevel 9`) and check rewrite log -- something useful may be there. – LazyOne Jul 14 '11 at 19:59

1 Answers1

0

The issue is that /name is a file name that apache usually manages to map to the directory /name/, but sometimes this mechanism fails. I've had a remotely similar problem and followed the suggestions to solve the problem according to the Trailing Slash Problem section of the URL Rewriting Guide in Apache's documentation.

I'd think that in your case you could try to add the following lines (I'd suggest right after RewriteEngine On) to your Apache configuration file, if you have access to it:

 RewriteBase    /
 RewriteRule    ^name$  name/  [R]
mapto
  • 605
  • 9
  • 23