LI79523: A HTTP 204 RESPONSE CODE MAY NOT BE PROCESSED CORRECTLY WHEN USING AN INVOKE POLICY

5.0.6.2-APIConnect-Portal-20170301-1522
5.0.6.2-APIConnect-Portal-20170301-1522.ova
APIConnect_Management_5.0.6.2_20170227-1003_cfe593c0e1ea_1cf3ed4.ova
APIConnect_Management_5.0.6.2_20170227-1003_cfe593c0e1ea_1cf3ed4.vcrypt2
apiconnect-2.5.21
5.0.6.2-APIConnect-Portal-Essentials-20170301-1522
5.0.6.2-APIConnect-Portal-Essentials-20170301-1522.ova
APIConnect_Management_Essentials-5.0.6.2_20170227-1003_cfe593c0e1ea_1cf3ed4.ova
APIConnect_Management_Essentials-5.0.6.2_20170227-1003_cfe593c0e1ea_1cf3ed4.vcrypt2

APAR status

• Closed as program error.

Error description

• When the HTTP response code to an invoke policy is 204 (no
  content), the Datapower gateway may return a 500 (internal
  server error) if a Content-Type header is also included in the
  204 response.
  

Local fix

Problem summary

• The gateway incorrectly attempts to process the content when it
  receives an HTTP 204 (no content) response and a Content-Type
  header has been set in the response.
  

Problem conclusion

• This issue is resolved in IBM API Connect V5.0.6.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

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels

• R500 PSY

     UP