Bug 1021767
Summary: | JSP Character encoding is not set properly. | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | jooho lee <jlee> | ||||
Component: | Web | Assignee: | Rémy Maucherat <rmaucher> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Radim Hatlapatka <rhatlapa> | ||||
Severity: | high | Docs Contact: | Russell Dickenson <rdickens> | ||||
Priority: | unspecified | ||||||
Version: | 6.1.1 | CC: | mvelas | ||||
Target Milestone: | ER10 | ||||||
Target Release: | EAP 6.3.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-08-04 06:54:51 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
jooho lee
2013-10-22 03:45:20 UTC
This is only about a GET request that would have its URI badly decoded. This works. It seems you tried to set all possible configuration options and UTF-8 is mentioned just about everywhere, but actually USE_BODY_ENCODING_FOR_QUERY_STRING likely overrides everything (your GET has no charset to specify for its non existent body, and the HTTP default is not UTF-8). Encodings in URI is not a very good idea unless you like problems ... Hi Remy, Basically, for using international language, I suppose encoding is one of must to do to avoid character problems. As you mentioned, Http default is not UTF-8 so sometimes it makes some problems happen with global language such as Chinese, Korean and so on. Hence, normally this kind of option which override charset enforcely are used. However, even I tested with jsp which contains charset=utf-8 & encoding=utf8, problem was occurred. Although I set system properties "URI_ENCODING and USE_BODY_ENCODING_FOR_QUERY_STRING" to override the charset once agagin, it was also same result. Actually, I didn't test POST but I am not sure why you think Encoding in URI is not a very good way. As I mentioned above, it is usual to use encoding uri for international words. Moreover, I think this is definitely a bug that paramter come from previous page is forcebly decoded by ISO-8859-1 even though charset is defined as utf-8 on the top of file. Yes, you set everything you can, but that's counter productive. So drop USE_BODY_ENCODING_FOR_QUERY_STRING. Using the configuration proposed by Rémy (setting only the org.apache.catalina.connector.URI_ENCODING property to UTF-8), I obtained expected correctly encoded output: Results: #### Original Parameter Msg : 가나다###### Issue was verified against EAP 6.3.0.ER10. |