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=22141>. 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=22141 response wrapper not being used in filtering an error-page [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Component|Connector:Coyote HTTP/1.1 |Catalina Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-08-05 17:06 ------- Error page processing works like this: - Request gets processed - Then once the processing is done, the response is forwarded to the error page (the JSP) Your filter can't intercept forwards, so it is not invoked. As for the ISE, I think it means just what it means (getOutputStream was already used previously, so Jasper doesn't work; I assume that if you had your filter invoked, it would work). In Tomcat 5, you can map a filter to the request dispatcher forward and include, which would allow you to make it work. I do think, however, that compression belongs to the lower level (the HTTP connector). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
