IBM Support

PK26295: UNKNOWN HEADERS ARE NOT CORRECTLY PARSED IF WHITESPACE EXISTS BETWEEN THE NAME AND THE COLON DELIMITER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an unexpected header name is present in an incoming
    message and contains whitespace between the end of the name
    and the colon delimiter, then the name is not extracted from
    the stream correctly.
    
    For example, if the line "Unknown  : myvalue" arrived, it
    would be stored as "known" with the value "myvalue".
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the genericbnf parsing package      *
    *                 which includes the HTTP and SIP channels     *
    *                 of WebSphere Application Server version 6.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: If whitespace exists between the end    *
    *                      of an unknown or non-standard header    *
    *                      and the colon delimiter, then the       *
    *                      header name is not parsed correctly.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The extraction of the header name was based on the location of
    the colon and not the index of the last header name character.
    Thus whitespace would appear and leading characters of the
    actual name were dropped, one per whitespace character.
    
    Parsing of an incoming line such as "V  : value" will save a
    header name of " ".
    

Problem conclusion

  • The name extraction for the unknown headers now works from the
    correct positions and will strip off the trailing whitespace.
    Parsing an incoming line of "V  : value" will save the correct
    header name of "V".
    
    This is targeted for WebSphere Application Server fixpacks
    6.0.2.13 and 6.1.0.1.
    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

    PK26295

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-06-09

  • Closed date

    2006-06-16

  • Last modified date

    2006-06-16

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

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

Modules/Macros

  • HTTPCHAN
    

Fix information

  • Fixed component name

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
18 October 2021