htaccess rewrite causes 500 error instead of 404

Question

I\'ve recently added this little bit of code to my .htaccess file:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
Rewri         


        

Answer 1

The intention of these rules is, as you suggested, to allow someone to request a page without including the PHP extension. So if you had a file on example.com called about.php then someone would be able to use the URL http://example.com/about in order to access it.

However if someone requests http://example.com/about.php directly you don't want it to be rewritten as http://example.com/about.php.php. Similarly, you don't want requests for images, CSS stylesheets etc to be rewritten. This is where the 2 RewriteConds come in, they are conditions saying that the rewriting should only take place if the request doesn't match a file (!-f) or directory (!-d) that actually exists on the site.

To answer why you're getting a 500, this could be because the permissions in Apache are configured not to allow rewrite rules in an htaccess file or one of several other reasons. Check the end of your error_log to see if there are any messages in there.

Answer 2

First off, here is some reference to better understand the mod_rewrite module:

mod_rewrite Documentation

mod_rewrite Cheat Sheet

The problem you are seeing is that it is checking for both conditions, the default is [AND], when you only want to check for one, try this:

RewriteCond %{REQUEST_FILENAME} !-f [OR]
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ $1.php [L,QSA]

Answer 3

You should test if new path points to an existing file:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule ^(.*)$ $1.php [L,QSA]

Otherwise you will get an infinite recursion (error 500).