I'm not sure if I am going off into 'nadda-land' but doesn't the HTTP spec specify that the Content-Type header is used in both requests and responses? So shouldn't the URL be interpreted based on that charset specified by that?
eg Content-Type: text/html; charset=UTF-8 Are all valid values.. I think. (fyi I'm using the O'Reilly HTTP pocket reference and ftp://ftp.isi.edu/in-notes/rfc2616.txt to find this). - Chris. -----Original Message----- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 16 April 2002 14:52 To: Tomcat Developers List Subject: Re: TomCat web-server : problem with Japanese chars > The Web-server of TomCat does not appear to be able to resolve URLs that > contain non-ASCII characters (e.g. Japanese language) correctly for all > cases. We have a Win'2000 (Japanese OS) machine on which TomCat 4 is > installed. > > If some URL contains Japanese characters like : > http://localhost:8080/myapp/servlet/myservlet?name=<myname> > Here if myname is a Japanese string, it works fine because within the > servlet myservlet, we have set the encoding type to SHIFT_JIS before reading > the request parameters (a feature of Servlet 2.3 API) > > But for a URL like : > http://localhost:8080/myapp/<myname>.gif > this does not work if myname is a Japanese string and the server responds > with a 'resource not found' error. > > So is this a bug in TomCat or is there any solution we can implement for > this ? There is no established standard for URL char encoding, so it won't work in the real world. Tomcat (with Coyote) now defaults to UTF-8, which is the probable future standard. If the client encodes with some other charset (99% of the time, it will use the platform encoding instead), it won't work. Looking at the content-type to try to "be smart" is a possibility, but is also non standard. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- NOTICE: The information contained in this electronic mail transmission is intended by Convergys Corporation for the use of the named individual or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone (collect), so that the sender's address records can be corrected. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
