I am seeing the same behaviour as previously described. Text fields in my
form-login.jsp posting to j_security_check do not correctly follow encoding
type. I am using a ? character or (ALT-0153) in my password and it gets
garbled. I have set my web.xml to include the
I'm having the same issue. Even thought my login jsp sets the encoding to
utf-8, it seems that it is ignored. Therefore, any username with wide
characters can't login. The only way I got this working was by adding a
URIEncoding=utf-8 to the server.xml for Tomcat, and use a GET versus a
POST.
username has characters with codes U+0688, U+0434, U+0063.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3937391#3937391
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3937391
I looked at the document, the locale-encoding-mapping is for response, not for
request. So the web container still does not know the request encoding coming
from the client machine. One thing I do not understand: the default is
iso8859, but I think the default should be UTF-8.
Thanks!
View
j2ee_junkie wrote : javatwo,
|
| As I mentioned below, the filter is useless during FORM login. All that
login stuff happens in the container level. Filters are at the web-app/servlet
level.
|
| I am not speaking from experience, but what about the web-app.xml's
I am sorry for the error. I meant web.xml's web-app element. The schema
(found at http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd) has a
locale-encoding-mapping element that seems to be what your looking for.
However, I have never used this myself. Please keep me posted of it's use.
later,
javatwo,
As I mentioned below, the filter is useless during FORM login. All that login
stuff happens in the container level. Filters are at the web-app/servlet level.
I am not speaking from experience, but what about the web-app.xml's
locale-encoding-mapping-list configuration. In any case,
Thanks for reply, j2ee_junkie.
Right now I am using a filter to set request encoding to UTF-8 for all requests
in order to support chinese characters. It works great except Form login. The
username is created in UTF-8 and stored in database.
The related part in login-config.xml
javatwo,
I do not know if JBoss has any limitations of character encoding, but there are
a few things about your question that I may be able to help with.
Note: assuming you are using Tomcat...
First, if you created a filter with url-pattern = 'j_security_check', it will
never be executed.
