: Mod_rewrite for directories One of our developers who built the framework that our website uses is no longer with us and I appear to have a stack of issues across the site currently, one being

@Yeniel560

Now that I can see there were lines before what you had, I think you need to change the first lines of the file as such:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)/(.*)$ index.php?page_name=&sub= [NC,L]


The problem stems from the fact that RewriteRule ^(.*)/(.*)$ is running whether or not it's a file or directory, with the exception of everything in the preceeding RewriteCond %{REQUEST_URI} line. In my changes, I removed the RewriteCond %{REQUEST_URI} line because it accomplishes the same as the RewriteCond %{REQUEST_FILENAME} !-f, which should take care of any image, js, css, and other files itself. It won't hurt anything to leave it in there, but it is redundant.


I think the issue is that the RewriteCond need to go above the RewriteRule like so:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !(.[a-zA-Z0-9]{1,5}|/)$
RewriteRule ^(.*)/(.*)$ index.php?page_name=&sub= [NC,L]


The RewriteCond are the conditions that must first be met before the RewriteRule is engaged.


RewriteCond %{REQUEST_FILENAME} !-f checks to see if the 'file' part of the url is actually a real file on the server.
RewriteCond %{REQUEST_FILENAME} !-d is the same as the above, but specifically for directories.
RewriteCond %{REQUEST_URI} !(.[a-zA-Z0-9]{1,5}|/)$ checks to see if the request part of the URL ends in a '.' and an alphanumeric string.


If all of these conditions are met, then it does the rewrite. As you have it now, it does the rewriting and completely skips the conditions for the rewrite, hence why URLs to existing folders/files are getting rewritten.

Vote Up Vote Down