https://issues.apache.org/bugzilla/show_bug.cgi?id=45187
--- Comment #10 from Ruediger Pluem <[EMAIL PROTECTED]> 2008-06-12 14:26:20 PST --- (In reply to comment #7) > Yes. > > The filename testing occurs in the "directory walk". Any module which And this happens *after* applying the server wide mod_rewrite rules (not the ones configured per directory or in .htaccess) So it is quite astonishing that the reporter says that the request does not even hit his rewrite rules. > is configured to avoid this altogether, e.g. mod_proxy using ProxyPass > redirection, should dodge the filename testing. > > That's not how mod_jk works, but you should try mod_proxy_ajp as a suitable > replacement which should solve your issue, provided you don't encounter > similar > problems on Tomcat. mod_jk (1.2.26) also should not hit the "directory walk" as it has its own map_to_storage hook handler that stops the processing of the hook before the directory walk if a valid mapping for the uri was found. So all the above increases my feeling that the server is simply misconfigured and that this is the reason why the request does not get to the application. Second point is that that ENAMETOOLONG IMHO does not necessarily mean that the file does not exist (this would be indicated by ENOENT IMHO). It seems to indicate that path supplied to the stat call is too long which would open up the possibility to change to the appropriate directory and do a local stat there. Since httpd does not do this it smells something suspicious here and returns FORBIDDEN which is ok in this situation. BTW: Replying with not found also could drive the user of httpd nuts if the file is present. And to be honest what I don't get is: Does it really matter if you get FORBIDDEN or NOT FOUND. In both cases you do not get the file and this is not what you want an expect. You expect your content to be delivered. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
