tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 48550] Update examples and default server.xml to use UTF-8
Date Fri, 17 Dec 2010 18:23:56 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48550

--- Comment #3 from Attila Király <kiralyattila.hu@gmail.com> 2010-12-17 13:23:50 EST
---
As a user of Tomcat and a webapp developer I would really like to see the 1)
added to the default server.xml. I mostly develop apps using utf-8 encoding and
if the customer is using tomcat extra care is needed to either not use non
iso-8859-1 characters in query parameters or convincing them to modify the
tomcat configuration (from these options the former is always the easier).

Some test results:
- Glassfish 3.0.1 documentation contains a similar, optional (default value
"UTF-8") attribute called "uri-encoding" on the "http" element in the
"domain.xml" (mentioned here:
http://docs.sun.com/app/docs/doc/821-1753/girlq?l=en&a=view#indexterm-246 ).
Unfortunately it does not have any effect on query encoding (tried it with
different values but always ISO-8859-1 was used to decode query parameters).
This might be a bug in GF but the intention is there.
- On client side FF 3.6, Chrome 8, Opera 11 and IE9 Beta (and as I found on the
web older versions too) use the character encoding of the page to encode the
query parameters. So if the html is served with utf-8 encoding the query
parameters are encoded with utf-8.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message