IT15108: B2B GATEWAY RETURNS HTTP 500 INSTEAD OF HTTP 200 WHEN INBOUND MESSAGE IS SIGNED INCORRECTLY
Fixes are available
Closed as program error.
When inbound message is signed incorrectly, B2B Gateway return HTTP 500 error for verification failure. However, according to RFC, it should indicate success at the HTTP level even when the disposition of the data was an error condition at the authentication, decryption or other higher level.
Incorrect HTTP 500 return for incorrectly signed inbound message.
Fix is available in 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