IBM Support

PI67942: JAVAX.SERVLET.HTTPSERVLETREQUEST.GETREQUESTURI() MIGHT RETURN A DECODED VALUE AFTER DISPATCHING

Fixes are available

PI67942: HttpServletRequest.getRequestURI() might return a decoded value after dispatching
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Invoking HttpServletRequest.getRequestURI() returns a decoded
    URI if it is invoked after dispatching the request when a
    decoded path was passed to
    javax.servlet.ServletRequest.getRequestDispatcher(String
    path).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server versions   *
    *                  8.5.5 and 9.0, and Websphere Application    *
    *                  Server Liberty users of Web Container.      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Invoking                                *
    *                      HttpServletRequest.getRequestURI()      *
    *                      after dispatching the request           *
    *                      incorrectly returns a decoded URI if a  *
    *                      decoded path was passed to              *
    *                      javax.servlet.ServletRequest.getRequest *
    *                      Dispatcher() or                         *
    *                      javax.servlet.AsyncContext.dispatch()   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If a decoded path is used when invoking
    ServletRequest.getRequestDispatcher() or one of the
    AsyncContext.dispatch() methods,
    HttpServletRequest.getRequestURI() returns a decoded URI
    instead of an encoded URI after the request has been
    dispatched.
    The following is an example of this problem:
    ServletA:
    ...
    request.getRequestDispatcher("/ServletB/a b").forward();
    ...
    ServletB:
    ...
    String uri = request.getRequestURI();
    ...
    The "uri" variable in ServletB will have the following value:
    /ServletB/a b
    The getRequestURI() method should return an URL encoded value.
    

Problem conclusion

  • The WebContainer has been modified to return a decoded URI
    when invoking HttpServletRequest.getRequestURI() after
    dispatching.
    
    A new context parameter needs to be set to true in the
    application's web.xml to enable this fix. If this fix is
    enabled, the developer must make sure that any invocations to
    ServletRequest.getRequestDispatcher() and
    AsyncContext.dispatch() are being done using decoded paths as
    a parameter:
    
    <context-param>
    
    <param-name>com.ibm.ws.webcontainer.ENCODE_DISPATCHED_REQUEST_UR
    I</param-name>
            <param-value>true</param-value>
    </context-param>
    
    After enabling the fix the "uri" variable in the example above
    will have the following value:
    
    /ServletB/a%20b
    
    If an encoded path is used when invoking
    ServletRequest.getRequestDispatcher() and
    AsyncContext.dispatch() when this fix is enabled the "uri"
    variable will have the following value:
    
    /ServletB/a%2520b
    
    This will be considered an application error and can be fixed
    by using decoded paths when invoking
    ServletRequest.getRequestDispatcher() and
    AsyncContext.dispatch().
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.11, 9.0.0.2 and 16.0.0.3. 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 number

    PI67942

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-23

  • Closed date

    2016-09-21

  • Last modified date

    2016-09-21

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

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

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 October 2021