Fix (APAR):  PQ93388

Status:  Fix

Release:  5.1.1.1,5.1.1,5.0.2.7

Operating System:  All

Supersedes Fixes:  

CMVC Defect:  PQ93388

Byte size of APAR:  76881

Date: 2004-09-23

Abstract:  WebSphere does not parse the encoded jsp parameter

Description/symptom of problem:  Since WAS5.0.2.5 and WAS5.1.1, customer send in a jsp parameter, WebSphere no longer parse this parameter for customer. Then if customer do a request.getParameter()call, same value will be returned. If customer send in a URLEncoded value, then he can do URLDecode later by himself. The reason for this change is some user want to use DBCS charactor in the JSP parameters without URLEncoded it, so does not want WebSphere parse it for them.
 However, some customer  application rely on WebSphere to parse its encoded parameters.To satisfy these two requirement, WebSphere implement a new way to parse customer jsp parameter. 
1. If the incoming JSP parameter is URLEncoded to the request encoding, WebSphere 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 charactor "%" and " ", then WebSphere decoder will return the same value. For example: 1,2,3 will be decoded as 1,2,3
3. If customer incoming JSP parameter is not URLEncoded, and contain charactor"%" or " ", for example "%100". Then customer can set webcontainer custom property "JSPParameterEncodedEnabled=true". Then WebSphere decoder will not decode it, a request.getParmeter() call will return "%100". This custome property default value is false.
PQ93388_511_fix.jar is for release 5.1.1 and 5.1.1.1. 
PQ93388_502_fix.jar is for release 5.0.2.7






Directions to apply fix:  

NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The Fix Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/support/index.html

1) Create temporary "fix" directory to store the jar file:
             UNIX: /tmp/WebSphere/fix
          Windows: c:\temp\WebSphere\fix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix.

5) Restart WebSphere

6) The temp directory may be removed.







Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS
     ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be
          removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.


1) Shutdown WebSphere

2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix.

3) Restart WebSphere







Directions to re-apply fix:  
1) Shutdown WebSphere

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere









Additional Information: