You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by ma...@apache.org on 2002/07/02 15:52:40 UTC
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/core BufferedServletOutputStream.java
marcsaeg 2002/07/02 06:52:40
Modified: src/share/org/apache/tomcat/core Tag: tomcat_32
BufferedServletOutputStream.java
Log:
If an invalid character is sent through BufferedServletOutputStream it will
cause an infinite loop on the error page because the same invalid character
will put into the error page which will then be sent through the BSOS which
will cause another exception to the error page which will start the whole
over again.
NOTE: I know that TC3.2.x has been obsoleted, but I came across this one
change that I made locally after the 3.2.4 release and figured I'd get into
CVS before it got lost on my local machine.
Revision Changes Path
No revision
No revision
1.14.2.4 +5 -5 jakarta-tomcat/src/share/org/apache/tomcat/core/Attic/BufferedServletOutputStream.java
Index: BufferedServletOutputStream.java
===================================================================
RCS file: /home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/core/Attic/BufferedServletOutputStream.java,v
retrieving revision 1.14.2.3
retrieving revision 1.14.2.4
diff -u -r1.14.2.3 -r1.14.2.4
--- BufferedServletOutputStream.java 22 Jun 2001 19:57:06 -0000 1.14.2.3
+++ BufferedServletOutputStream.java 2 Jul 2002 13:52:39 -0000 1.14.2.4
@@ -215,9 +215,9 @@
// streams properly encode their output.
//
if ((c & 0xff00) != 0) { // high order byte must be zero
- String errMsg = sm.getString(
+ String errMsg = sm.getString(
"servletOutputStreamImpl.fmt.not_iso8859_1",
- new Object[] {new Character(c)});
+ new Object[] {Integer.toHexString((int)c)});
throw new IOException(errMsg);
}
write(c);
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>