DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9434>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9434 Response Filters do not work with jsp:forward [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-05-27 21:43 ------- Could you please provide any hints in the specification supporting this theory? Either, this is a lack in the implementation of spec 2.3, or the specification does not point out restrictions in the orthogonality of filters vs. JSP tags. Any article I have read regarding filters supports the impression filters are are technology to use "on top" of servlets & JSP. Things work fine with Resin. I think the worst is declaring this lack internally as a "silent restriction" of Tomcat. Unless I have missed a clear hint in the specification, this has to be either mentioned in the release notes or fixed or pointed out in the specification. I aggree the specification might drop a note on wether filters should be bound to the destination URL or source URL on page forwards. However, dropping support for any use of filters with applications that use jsp:forward is weakening filters to a "might work if you are lucky" approach. I understand I am the guy postulating without giving. I've spent some hours trying to find a solution and failed. I'm not in the source. I'm using your great work without contribution. However, from a users perspective, this is simply arrogantly saying: "Yes, you found a bug. But we will neither tell nor fix it". -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
