I'm working on a PHP script for my website. I use a mod_rewrite rule, so that all requests within a directory end up calling my script. My script then parses the URI, and determines the proper action.
I'm working on an admin area, and login and logout functionality. So in my script I check with the URI ends in "/admin" or "/login" or "/logout". With all other URI's my script get called appropriately however it seems with these certain URIs (and maybe others), something else (another module?) is preempting mod_rewrite. It seems like this other module is checking to see if the path exists (it doesn't, nothing exists besides my script), and returning a 404. If I add some dummy files named appropriately named, mod_rewrite does it's magic and my script gets called. Other random paths I use also don't exist, but mod_rewrite works fine and my script gets called appropriately.
A quick grep for "logout" through my Apache modules directory doesn't reveal much.
Does anybody know which module is preempting mod_rewrite? Or how I can disable this behavior?
I'm working on an admin area, and login and logout functionality. So in my script I check with the URI ends in "/admin" or "/login" or "/logout". With all other URI's my script get called appropriately however it seems with these certain URIs (and maybe others), something else (another module?) is preempting mod_rewrite. It seems like this other module is checking to see if the path exists (it doesn't, nothing exists besides my script), and returning a 404. If I add some dummy files named appropriately named, mod_rewrite does it's magic and my script gets called. Other random paths I use also don't exist, but mod_rewrite works fine and my script gets called appropriately.
A quick grep for "logout" through my Apache modules directory doesn't reveal much.
Does anybody know which module is preempting mod_rewrite? Or how I can disable this behavior?
Facebook
Twitter