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=22141>. 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=22141 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2005-03-21 01:38 ------- This has changed in the 2.4 spec, I suspect for this very reason. As Remy indicated, one option is to use 5.0.x or 5.5.x I don't see an easy way for Tomcat 4.1.x to handle this. Both the filter that calls getOutputStream() and the subsequent error page that calls getWriter() (using a JSP will always result in a call to getWriter()) are both part of the webapp. My instinct is, therefore, that the solution should also be part of the webapp. That being said, if you would like to propose a patch for 4.1.x then please do so - patches are always welcome. One approach that is open to you is to use a servlet for your custom error page and use getOutputStream(). I am setting the status on this back to INVALID on the basis that the spec, not tomcat, is the underlying issue. -- 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]
