APAR status
Closed as program error.
Error description
Customer noted that the JSP parameters are not decoded properly
in WSAS 5.1.1, but are still URLEncoded when retrieved.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users *
****************************************************************
* PROBLEM DESCRIPTION: If users send in encoded query string, *
* Application Server does not parse it *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Application Server no longer parses the incoming query string
for customers since many customers do not want that, however,
this may break some customer's applications since they rely on
Application Server to parse it.
Problem conclusion
Since Application Server 5.1.1, if customers send in a jsp
parameter, Application Server no longer parses this parameter.
Then if customers do a request.getParameter()call, same value
will be returned. If the customer sends in a URLEncoded value,
then he can do URLDecode later by himself. The reason for this
change is some users want to use DBCS charactor in the JSP
parameters without URLEncoding it, so the do not want
Application Server to parse it for them.
However, some customer applications rely on Application Server
to parse their encoded parameters. To satisfy these two
requirements, Application Server has implemented a new way to
parse customer jsp parameters.
1. If the incoming JSP parameter is URLEncoded to the request
encoding, the Application Server decoder will decode it
accordingly.
For example: 1%2c2%2c3 will be decoded as 1,2,3
2. If the incoming JSP parameter is not URLEncoded, and does
not contain characters "%" and " ", then the Application Server
decoder will return the same value. For example: 1,2,3 will be
decoded as 1,2,3
3. If the incoming JSP parameter is not URLEncoded, and contains
characters "%" or " ", for example "%100". Then the customer
can set the webcontainer custom property
"JSPParameterEncodedEnabled=true". Then the Application Server
decoder will not decode it, a request.getParmeter() call will
return "%100". This custom property default value is false
Temporary fix Comments
APAR information |
APAR number |
PQ93388 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
10W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-08-26 |
Closed date |
2004-09-23 |
Last modified date |
2004-09-23 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|