DO NOT REPLY [Bug 9856] - sendError(404) fails after getOutputStream() is called, if you have a custom 404 error-page

[bu...@apache.org]

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=9856>.
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=9856


niels_meersschaert@businessweek.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|enhancement                 |major




------- Additional Comments From niels_meersschaert@businessweek.com  2005-03-08 19:15 -------
This is a more significant issue than an enhancement.  I've run into an issue with a filter which modifies 
the response object.  It appears that error-page is handled after the filters.  If the filter modifies a 
response object (effectively calling getOutputStream()), the error-page will throw the exception 
described.  Since much of the benefit of the error-page directive is to setup a jsp page for displaying of 
error messages (including exceptions and error-codes like 404), this is a major bug.  I've been unable 
to determine any workaround other than either not using the filter, or not using error-page directives, 
which of course severley limits functionality.

-- 
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org