|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Stop making mediocre tutorials.The best tutorials are video! Camtasia Studio makes it easy to create engaging, buzz-building screen videos at any size, in any popular format. Download the free trial!
|
|
#1
|
|||
|
|||
|
I have encountered the same mod_rewrite issue in both Apache 1.3 and Apache 2.2 whereby a simple regex pattern can match ANY webroot directory name except the webroot directory named "scripts" (/home/user/public_html/scripts). Initially i thought there might simply be a conflicting Alias/ScriptAlias/ScriptAliasMatch directive in httpd.conf somewhere, but i haven't found any. I've looked at the apache log at loglevel debug and it gives me very little information other than that it thinks the directory doesn't exist (which of course it does).
Now i presume the issue still relates to some conflicting alias hidden somewhere deep in the bowels of the webserver that i haven't found - has anybody got any ideas where i might be able to look? There is absolutely nothing wrong with the regexp pattern, as it works flawlessly for every directory except "scripts". (it works with "script", "scripting" or any other possible variation of "scripts" just not "scripts"!) I'm using Cpanel/WHM. Thanks |
|
#2
|
||||
|
||||
|
So cPanel/WHM could have something somewhere that you don't know about, such as in an .htaccess file somewhere between / and /home/user/public_html/.
Does the Apache debug level not indicate that a request in /scripts/ is being Alias-ed or handled by Apache in some other way? I'm not sure it should, so I'm curious. You could create a RewriteLog if you have access to httpd.conf to see if that'll help, but you won't see anything there if Apache is hooking /scripts/ before it gets to mod_rewrite. I do believe, however, that your suspicions are most likely correct. I also believe that whatever you find that's causing it should not be removed or changed because it'll probably break cPanel/WHM.
__________________
# Jeremy Explain your problem instead of asking how to do what you decided was the solution. |
|
#3
|
|||
|
|||
|
Thanks for responding. I think you're right about leaving it be if it's caused by Cpanel/WHM (which it most likely is). It can't be a .htaccess file as i have Allow Overrides set to None. This most likely will remain an enigma forever.
Thanks again. |
![]() |
| Viewing: Dev Shed Forums > System Administration > Apache Development > mod_rewrite - Mod_rewrite Anomaly |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|
|