-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mircea,
On 4/21/2010 6:56 AM, Mircea LUTIC wrote:
> The filter does get called on my GET request.
Of course.
> In my understanding, a filter is the reccomended method of handling
> UTF-8 for both GET & POST (as well as other methods like HEAD, PUT
> etc.).
The filter cannot influence the way that GET parameters are decoded. The
only way to change that is to set URIEncoding="UTF-8" on your
<Connector> in server.xml.
Your best bet is to transfer all non-US-ASCII data in request /bodies/
by using HTTP POST.
If HTTP POST is not acceptable, please let us know why and perhaps we
can suggest some alternatives.
This looks a bit weird to me:
>
> window.location="test.jsp?Name=larevolu%C8%9Bie";//"test.jsp?Name="+escape(Utf8encode("larevoluție"))
What does the Utf8encode function do? What does the escape function do?
Have you tried snooping the HTTP conversation using a browser plug-in
and/or a line sniffer like Wireshark? What does the data doing over the
TCP/IP connection look like?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkvPHRkACgkQ9CaO5/Lv0PDVkgCgu3dZM9mFNYXDjOBATjvJ5MMP
sN4AniN4aNLVnqsiEL7EzkxzVm4wp83F
=MpSC
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
