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=38826>. 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=38826 Summary: spec violation? Product: Tomcat 5 Version: 5.5.12 Platform: All OS/Version: Windows 2000 Status: NEW Severity: critical Priority: P1 Component: Servlet & JSP API AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Hi all! In Servlet spec, Filters section (SRV.6) I didnt found any mentions that error-handling process should bypass filters. My problem is: I have lot of heavy-working jsps in my app (yes I know bad design etc but at the moment there is no way to rewrite it). Sometimes, when one of jsps generated 200K of output the app-level error is encountered and is thrown to web container. It should return the error-page + status-code of 500 but such a big output in front of it leaded to "early" flush (status code 200 + part of html response was already sent to client). Such big amount of output data should be buffered to prevent "early" commit. I created a bufferer-filter for this purposes. But when I finally got an exception and execution is passed to error page I see that error-page don't use HttpServletResponseWrapper I defined in my filter. Instead of it error-page works with unwrapped object "org.apache.catalina.connector.ResponseFacade" and obviously bypass my filtering logic. -- 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]
