Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: 21 Jul 2004 16:19:20 -0000
Message-ID: <20040721161920.26273.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 28875]  -
    Multi-byte characters in default error page aren't printed out correctly.

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=28875>.
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=28875

Multi-byte characters in default error page aren't printed out correctly.


------- Additional Comments From moriyoshi@at.wakwak.com  2004-07-21 16:19 -------
I haven't been looking into this problem much and maybe I'm wrong somewhat.

Regarding the latest patch, I'm wondering if there is any reason to drop setLocale()
from that portion.

Invocation of either setCharacterEncoding() or setContentType() that precedes setLocale()
seems to prevent setLocale() from changing the character encoding for the request.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org