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 2004/07/26 23:51:22 UTC
DO NOT REPLY [Bug 30332] New: -
Field charsetSet reset problem in class org.apache.coyote.Response
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=30332>.
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=30332
Field charsetSet reset problem in class org.apache.coyote.Response
Summary: Field charsetSet reset problem in class
org.apache.coyote.Response
Product: Tomcat 4
Version: 4.1.30
Platform: All
OS/Version: All
Status: NEW
Severity: Critical
Priority: Other
Component: Connector:Coyote HTTP/1.1
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: peilinz@hotmail.com
We are still having problems with response content-type to have ";charset=UTF-8"
automatically attached even though we explicitly called
HttpServletResponse.setContentType("application/pdf") and never called
setCharacterEncoding() in the same request. As a matter of fact, after putting
some debugging code in org.apache.coyote.Response.setCharacterEncoding(), I
found out it was never called in the request that we use to send the PDF file.
The debugging also showed that the member variable "charsetSet" was true before
setContentType() was called. Therefore, I suspect the recycle()/reset() method
in this class wasn't called when it needs to be called. On the other hand, does
it make sense to add "charsetSet = false;" at the beginning of the
setContentType() method?
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org