IBM Support

PM82220: Null value returned when a JAX-WS web service retrieves the HTTP header value by header name

Fixes are available

7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Once the server had been started and a request was sent with a
    header of say, "ABCD", if a subsequent request was sent with a
    header of "abcd" it is still received as "ABCD".  This will
    cause problems whenever checking for a case sensitive key in
    the http header map, and any part of the cached header name is
    in a different case.
    
    The problem is because the http headers are not case sensitive
    but the keys used in the JAX-WS map which contains the http
    data, are.  If WAS caches a value which is not in the same case
    as what is expected from the JAX-WS map, then you never get the
    correct value returned, even if the request has the header in
    the correct case.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server retrieving HTTP headers from a       *
    *                  JAX-WS web service request.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a JAX-WS web service retrieves     *
    *                      the HTTP header value by header name,   *
    *                      get null values returned.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A JAX-WS web service which needs to read some customized HTTP
    header value from the request. Most of the time this works
    fine, but occasionally when the application retrieves the
    headers, it gets null values returned, even though the headers
    are in the request.
    When getting the customized HTTP headers, the default behavior
    is searching and caching the header name in a case sensitive
    manner. Once the uppercase header name, like "ABCD" is cached,
    if the next request asks for header name "abcd," it will
    never get the header value due to the case sensitive search
    for the name.
    

Problem conclusion

  • According to the HTTP Protocols, modified the get method for
    searching and retrieving HTTP headers to be case in-sensitive.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.29, 8.0.0.7 and the fix pack after 8.5.0.2.
    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

    PM82220

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-06

  • Closed date

    2013-03-21

  • Last modified date

    2013-03-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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM82220

Modified date: 21 March 2013