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/05/27 09:09:34 UTC
DO NOT REPLY [Bug 10385] -
SSI-Servlet produces invalid character encoding information
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=10385>.
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=10385
SSI-Servlet produces invalid character encoding information
temp@pa22.katowice.sdi.tpnet.pl changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |http://pa22.katowice.sdi.tpn
| |et.pl:8101/fortune/example.s
| |html
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
Version|4.0.3 Final |4.1.24
------- Additional Comments From temp@pa22.katowice.sdi.tpnet.pl 2003-05-27 07:09 -------
I tried to use polish character encoding on page
http://pa22.katowice.sdi.tpnet.pl:23/fortune/example.shtml
and the result is - the characters in "Strona g��wna" are displayed wrong - it
looks they are converted to unicode.
The header is set properly
<meta http-equiv="content-type" content="text/html; charset=iso-8859-2"> and
the characters are also ok - you can see source of the file in
http://pa22.katowice.sdi.tpnet.pl:8101/fortune/example.shtml.src
The line with res.setContentType("text/html;charset=UTF-8"); is still present
in the code, propably this is the reason, but simple replacing it with my
desired encoding doesnt solve the problem completely.
What should I do to make it work at least temporary?
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org