https://issues.apache.org/bugzilla/show_bug.cgi?id=50734
Konstantin Kolinko <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #7 from Konstantin Kolinko <[email protected]> 2011-09-09 18:45:42 UTC --- (In reply to comment #6) > This patch has a side effect in my configuration that uses some technical > valves that will no longer be called if a context does not exist for the > requested URL (for example, my valve was able to report how many requests > failed due to invalid context mapping indicating some kind of hacking or > misconfiguration going on). 1. There is a number of other ways how a request can fail. AccessLogValve support was improved in 6.0.30. You may find all places in the code where access logging is triggered. Anyway, you do not provide much details, and I do not see why this use case may be of any importance. If you want to provide more details, open a new issue. This one is fixed. > > As a workaround, i had to declare a dummy ROOT context (pointing to an empty > directory) so that the v > 2. This is a valid workaround. I do not see any problem with it. In essence, any sane Tomcat installation must have a ROOT webapp. > I can understand we want to report a 404 but i consider patch should be > plugged I do not quite understand your proposal. I'd be better if you could provide a patch to illustrate it. > where 400 is reported (not so early) to report 404 only if no host is > matching. Re-closing as FIXED. -- 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]
