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=32424>. 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=32424 ------- Additional Comments From [EMAIL PROTECTED] 2005-02-10 23:04 ------- Keith thanks for making the logic behind this clearer. I understand that this is desirable behaviour *when* the "default" servlet ends up handling the request but the redirect happens in "Rule 7" of the mapper where it is only *possible* that the "default" servlet will handle the request. In my web app a filter forwards the request on so that in the end the "default" servlet is never invoked which means the assumption made at "Rule 7" was invalid. In addition to this the spec is quite clear that a filter that is mapped to "/*" should be given the opportunity to filter all requests - in this special case Tomcat does not fulfil this requirement as it makes the *incorrect* assumption that the redirected request is logically the same as the original. eg. In my web app the request for "/images" is not the same as "/images/" (even though I don't have a servlet mapped to "/images") however Tomcat does not allow our forwarding filter to process the "/images" request and forward it on the the correct servlet as there happens to be a directory called "images" in out web app. I'm currently using Jetty and it allows filters to process the request *before* doing the 302. -- 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]
