IT19473: HTTP CLIENT IP LABEL DOES NOT WORK
Fixes are available
Closed as program error.
The HTTP Client IP Label does not work as described. It should allow you to enter the name of an HTTP Header (e.g X-Forwarded-For) to determine the IP address of the requesting client, which would then be used for monitoring and logging. Instead, the specified HTTP Header is not used for monitoring and logging. This will impact X-Client-IP header.
Affected are all customers using the http-client-ip-label setting present in most of DataPower services. This setting is by default set to "X-Client-IP". The functionality behind this feature lacked the part where the original client IP present in the "X-Client-IP" (or other custom) header should appear in the system logs as the current transaction client IP. This fix also introduces a new "network" target "info" priority message to mark the moment the logged client IP changes. For releases up to and including 7.5.2.x the message is: > Message 0 is specific to APAR IT19473: <current-client-ip> <new-client-ip> <http-header-name> Future releases will display the same message as more readable: > Client IP <current-client-ip> is now tracked as <new-client-ip> due to its presence in the "<http-header-name>" HTTP header.
Fix is available in 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11 and 18.104.22.168 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