IT34848: REQUEST.HEADERS.X-CLIENT-IP NEEDS TO BE POPULATED IN DATAPOWER API GATEWAY

Fix packs for DataPower Gateway version 2018.4.1

APAR status

• Closed as program error.

Error description

• After migrating v5 APIs to APIGW, one will see that
  the request.headers (such as request.headers.x-client-ip ) are
  not available on APIGW and returns  'undefined' as instead of
  the expect value.
  In v5:
  request.headers.x-client-ip is populated
  In APIGW:
  request.headers.x-client-ip is NOT populated
  message.headers.x-client-ip is populated
  

Local fix

• Manually change your gateways scripts to use
  "message.headers.x-client-ip" instead of
  "request.headers.x-client-ip ".
  

Problem summary

• The APIC user may not use the header request.headers.x-client-ip
   in API Gateway as populated in V5.
  

Problem conclusion

• Fixed in 2018.4.1.15, 10.0.1.2
  

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:

Fix information

• Fixed component name

  DATAPOWER

• Fixed component ID

  DP1234567

Applicable component levels

• R770 PSY

     UP

• RA0X PSY

     UP