IBM Support

PH17473: CASE SENSITIVITY ISSUES WHEN HEADERS ARE NOT BEING CACHED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Some headers may not be recognized if the header called with the
    getHeader() method has a different casing than the header
    received on the request.
    
    This issue is known to happen in
    environments with heavy load, when not all headers are being
    cached by the application server.
    
    The issue started occurring
    in WebSphere 9.0.0.11.
    

Local fix

  • Ensure that the header being requested in the getHeader() method
    has the same casing as the header received on the request.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of the HTTP channel in IBM        *
    *                  WebSphere Application Server and IBM        *
    *                  WebSphere Application Server Liberty        *
    ****************************************************************
    * PROBLEM DESCRIPTION: HTTP headers are meant to be case       *
    *                      insensitive, yet the HTTP Channel,      *
    *                      under certain conditions, might do a    *
    *                      case sensitive compare of header        *
    *                      names.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the HTTP Channel's header cache is full, the internal
    storage of headers is used and it might result in a case
    sensitive lookup of header names.
    

Problem conclusion

  • The HTTP Channel code has been fixed so that header values are
    considered as case insensitive.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.17, 9.0.5.2, and Liberty 19.0.0.12.  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

    PH17473

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-09-27

  • Closed date

    2019-10-22

  • Last modified date

    2019-10-22

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSCVS22","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Edition":""}]

Document Information

Modified date:
22 October 2019