IBM Support

IT19215: MESSAGE MATCHING OBJECT DOES NOT PARSE HOST INFORMATION FROM X-CLIENT-IP HEADER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When using the message matching object to match on the value of
    a custom header, the match fails to properly parse information
    from designated header.
    Instead, the message matching object only checks for the
    physical IP address.
    Affected are customers who use the message count monitor to
    monitor custom headers. Also affected, are customer who monitor
    from the perspective of an engaged chained service to match on
    the client's IP.  Instead, the IP of the first service will be
    matched.
    

Local fix

Problem summary

  • If a monitor specifies pulling the IP of the source from the
    HTTP header and this header is set in the request, then that
    value is used to match against the subnet specified in the
    message matching; or, if instead matching on some other option,
    such as the method, then the IP is used as the 'source' for the
    request.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT19215

  • Reported component name

    DATAPOWER

  • Reported component ID

    DP1234567

  • Reported release

    720

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-10

  • Closed date

    2017-05-23

  • Last modified date

    2017-06-01

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

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

Modules/Macros

  • 0
    

Fix information

  • Fixed component name

    DATAPOWER

  • Fixed component ID

    DP1234567

Applicable component levels

  • R752 PSY

       UP



Document information

More support for: IBM DataPower Gateways
General

Software version: 7.2

Reference #: IT19215

Modified date: 01 June 2017