DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43409>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43409 ------- Additional Comments From [EMAIL PROTECTED] 2007-11-23 14:13 ------- (In reply to comment #8) > Of course there is no such literal statement. You just have to combine two > things: > 1. A web application may have several kinds of resources. Agreed. Further, I think we also agree that locations specified for error handlers can refer to any valid resource in the web app. > 2. The best match is served. The spec doesn't say this. SRV.9.9 mentions JSPs and Servlets as possible locations for error handlers and indirectly mentions static files when it refers to resources. The only place the spec defines how to work out which resource to use when a location could be referring to a static or a dynamic resource is SRV.11. This is no 'if the request matches a static resource that that always takes precedence' rule. The spec isn't always as clear cut as I would like but I can't find anywhere that even hints at static resources taking precedence. > You are suggesting that there can be a situation where a less than perfect > match > (a servlet in this case) is preferred over a perfect match (a static resource > in > this case). What is the logic behind that? This is exactly what can, and frequently does, happen as a result of applying the rules in SRV.11 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
