IT19215: MESSAGE MATCHING OBJECT DOES NOT PARSE HOST INFORMATION FROM X-CLIENT-IP HEADER
Fixes are available
Closed as program error.
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.
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.
Fix is available in 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168 and 22.214.171.124 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels