Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1117629

Summary: URI parameter decoded by ISO-8859-1 even though there is metadata "pageEncoding=utf-8"
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: jooho lee <jlee>
Component: jbossasAssignee: Fernando Nasser <fnasser>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.3, 6.3.0CC: jason.greene, jsenshar, mmiura
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-15 06:01:08 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 Flags
Sample application none

Description jooho lee 2014-07-09 05:29:43 UTC 
Created attachment 916626 [details]
Sample application

Description of problem:

According to JSP spec[1], if pageEncoding or contentType attribute is set, URI parameter should be encoded/decoded by other Character-set. However, EAP does not follow it, which means URI parameters are always decoded by ISO-8859-1.

Version-Release number of selected component (if applicable):
jboss web 7.2.2.Final

How reproducible:

I attached KoreaChar.war file. Deploy this application and go to following url:
http://localhost:8080/KoreanChar/test_tag.jsp?msg=8m%C2%B2


Steps to Reproduce:
1.http://localhost:8080/KoreanChar/test_tag.jsp?msg=8m%C2%B2&test2=C%C3%A9dric

Actual results:
8m²

Expected results:
8m²

Additional info:

Weblogic 12c and wildfy 9 works properly.

Weblogic
 http://10.65.223.29:7001/KoreanChar/test_tag.jsp?msg=8m%C2%B2
 ==>8m² 

EAP 6.2.3 & 6.3.0.Beta
 http://localhost:8080/KoreanChar/test_tag.jsp?msg=8m%C2%B2
 ==>8m²

Wildfly9
 http://10.65.223.29:8080/KoreanChar/test_tag.jsp?msg=8m%C2%B2 
 ==>8m²
Comment 1 jooho lee 2014-07-09 05:35:32 UTC 
JSP 2.0 spec
[1]http://download.oracle.com/otndocs/jcp/jsp-2.0-fr-oth-JSpec/ ==> JSP.D.1Detection Algorithm
Comment 2 Jay SenSharma 2014-07-09 06:03:40 UTC 
The Workaround to this is to set the following system property while booting up JBoss:

-Dorg.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING=true

However i guess "true" should be the default option. But unfortunately it seems to be "false"