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 >>> [EMAIL PROTECTED] 6/19/03 4:41:46 PM >>> There was an extremely detailed UTF-8/ISO-8859-1 'how to' on this list recently (past week or so). I don't remember the details but it seemed to do it for the others. tim Jeff Tulley wrote: > Has anybody successfully authenticated to the /admin application, with a user who > has a password that has extended characters? (espaņol is what I've been trying - > espa(n tilde)ol if that doesn't come through the email). > > I thought this was a side-effect of my use of the JNDIRealm, but I cannot get it to > work for me using the MemoryRealm as well. > > The problem seems to be the specification of encoding="utf-8" in login.jsp. If you > do not set this content type, Tomcat seems to default to "ISO-8859-1". While I > realize that this will only work for those who can live with ISO-8859-1 (Latin 1?), > it seems that UTF-8 isn't working at all. > > Note to the first objections I forsee: I wrote out the tomcat-users file using a > UTF-8 compatible editor, and the password was for sure stored in my LDAP directory > in UTF-8 as well. I also tried all sorts of combinations of encodings while > authenticating, from hitting alt-164 and alt-0241 on Windows to copy and pasting the > full UTF-8 encoded multiple character value into the password field. > > Anybody get this to work? I want to see if I'm just doing it wrong before > suggesting the change of taking the utf-8 declaration out completely. > > Thanks, > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
