PK47738: VERSION 6 IS MORE ADHERENT TO THE JSP SPECIFICATION THAN V5. <JSP:PARAM> SHOULD BE LEFT UNENCODED BY PAGE AUTHOR.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• The problem is seen because WebSphere 6.x is more adherent to
  the JSP specification. According the the specification
  <jsp:param> should be left unencoded by the page author.
  For backword compatability, JSP develepment team has decided
  to provide a custom property to turn off url encoding if the
  need be for the jsp tag <jsp:param>
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server versions    *
  *                 6.0.2 and 6.1 users whose applications try   *
  *                 to encode JavaServer Pages (jsp) parameters  *
  ****************************************************************
  * PROBLEM DESCRIPTION: According to the JSP specification,     *
  *                      page authors are not allowed to         *
  *                      encode jsp params in the <jsp:param>    *
  *                      tag. This restriction was however       *
  *                      allowed in version 5 while it was       *
  *                      tightened in version 6.Due to this      *
  *                      change, customers applications produce  *
  *                      erroneous output on version 6 while     *
  *                      it worked fine on version 5             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In order to maintain backward compatibility with version 5, in
  version 6 a new custom property called
  'disableURLEncodingForParamTag' has been introduced. By setting
  this property to true, the version 5 behaviour will be allowed
  in version 6 too.
  

Problem conclusion

• Code changes have already been integrated for this defect and
  will be officially available in the next fixpacks: 6.0.2.25
  and 6.1.0.13.
  Please refer to the recommended updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• JPS
  

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP