-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
meeboo,
meeboo wrote:
> But that other poster was using Struts 1! Also, I am already using
> <meta http-equiv="Content-Type" content="text/html;
> charset=ISO-8859-1"></meta>
> Has anyone had luck using for example å ä ö in S2 ?
What is the character set actually being used by the request and the
response? Just because you have ISO-8859-1 in your <meta> tag doesn't
mean that the response is actually being sent and the request is
actually being interpreted as ISO-8859-1.
Here are some things to look at:
1. What does request.getCharacterEncoding return?
2. What does response.getCharacterEncoding return?
3. What does System.getProperty("file.encoding") return?
4. What does your HTTP or AJP listener have configured for
its default character set? (In Tomcat, the connectors
can use a default charset when the client does not provide
one in the request headers).
5. You never mentioned whether you were using GET or POST. There
is a difference in how the data is decoded.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGOkSH9CaO5/Lv0PARAhC9AJ4rwoZJfegWReU+S5cenabnKOhDhQCgp2yA
sKE5xIBugzsYFhEvKmjE+Qg=
=jLc4
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
