This might help. http://www.w3.org/TR/REC-html40/interact/forms.html#adef-accept-charset
I really don't know.
-Tim
Jeff Tulley wrote:
Thanks I just found it in the archives. I had been at JavaOne last week and so did a mass-delete of this list when I returned, and I also did not pick that up in the archives for some reason until you pointed it out.
So, there is still a problem with Tomcat when a login page specifies <%@ page contentType="text/html; charset=UTF-8" %> (which the login.jsp of the /admin application indeed does). According to this FAQ, the inclusion of such a declaration is CORRECT. So, is Tomcat just missing the conversion part?
If so, I hope that it can be changed. It seems like such a change would be a huge potential backwards compatibility issue and is therefore risky.
I still challenge whether with the existing tomcat-provided login.jsp and authentication mechanism, whether you can log in with a user that has extended characters. If anybody has successfully done that please let me know. (I'm only successful if contentType=ISO-8859-1).
Also, that FAQ mentions passing in a "-Dfile.encoding=UTF-8", which Tomcat does not currently do. This is another backwards compatibility issue for getting this to be the default Tomcat behavior.
Jeff Tulley ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
