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 2003/08/31 23:22:21 UTC
DO NOT REPLY [Bug 22855] New: -
responses.setContentType "corrupts" pageEncoding not overrides that
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=22855>.
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=22855
responses.setContentType "corrupts" pageEncoding not overrides that
Summary: responses.setContentType "corrupts" pageEncoding not
overrides that
Product: Tomcat 4
Version: 4.1.27
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: Shazard@mits.lv
JSP produces wrong response
Example of very first 2 lines of very first JSP user hits.
-----------
<%response.setContentType("text/html;charset=windows-1257");%>
Autentifikâcija veiksmîga<br>
-----------
Response is set correctly as browser switches to right one, but letters and
charaters are corrupted and changed to "?"
Does not happens if <@page> is used but this is not acceptible in case if
encoding changes dynamically (depending on user request and changing resource
bundles)
The only difference between those 2 approaches is that in <@page> case it
happens before obtaining out and pageContext