https://issues.apache.org/bugzilla/show_bug.cgi?id=45187
--- Comment #11 from Roman Garcia <[EMAIL PROTECTED]> 2008-06-12 15:51:27 PST --- I guess if our Apache was misconfigured, we would have noticed it earlier. We've been running this configuration for more than 5 years now. But it could be an option. I'm trying to understand here. Are you saying that there is a way to skip filesystem access? Even with mod_jk? Can you point me out some documents I can read for that? Examples on how to setup mod_jk to skip the FS? If that's the case, and the only reason Apache is accesing the FS is because it KNOWS for fact that the user is requesting a FS file (because it ruled out any other possibilities), then FORBIDDEN or whichever response you choose for this should be fine. But, if this is the case, then why does Apache check for ENOENT at that point and what does it do with that request, when the file was not found? Why doesn't it just reply a 404 right there? On the other hand, if Apache reacts this way WITHOUT KNOWING whether the user is requesting an FS file, a SymLink, or a virtual path, then that's simply wrong. Because this is my case, because we hit an URL which gets rewritten, which gets passed to a Tomcat, which is handled by a Java app. Which, BTW, works OK with the patch I submitted. I guess this could be easily tested, with a proper environment. It should be as simple as: Install Apache Do a GET for a long URL. Check the log Anyone wanna give it a try? ;) Román. -- 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]
