You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/05/06 21:54:23 UTC
DO NOT REPLY [Bug 8831] -
ErrorReportValve.java corrupts data in subtle way
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=8831>.
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=8831
ErrorReportValve.java corrupts data in subtle way
remm@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From remm@apache.org 2002-05-06 19:54 -------
Yes, I agree. This is how the code behaves now in 4.0.4 and 4.1.x.
The current logic is:
Writer writer = response.getReporter();
if (writer != null) {
try {
hres.setContentType("text/html");
} catch (Throwable t) {
if (debug >= 1)
log("status.setContentType", t);
}
// If writer is null, it's an indication that the response has
// been hard committed already, which should never happen
writer.write(sb.toString());
writer.flush();
}
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>