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

Fix packs for DataPower Gateway version 7.1
Fix packs for DataPower Gateway version 7.2
Fix packs for DataPower Gateway version 7.5
Fix packs for DataPower Gateway version 7.5.1
Fix packs for DataPower Gateway version 7.5.2

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

• Fix is available in 7.1.0.17, 7.2.0.14, 7.5.0.8, 7.5.1.7,
  7.5.2.7 and 7.6.0.0
  
  For a list of the latest fix packs available, please see:
  http://www-01.ibm.com/support/docview.wss?uid=swg21237631
  

Temporary fix

Comments

APAR Information

• 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