Understanding HTTP Status Codes

This section describes HTTP status codes for non-SOAP and SOAP messages.

Status Codes for Non-SOAP Messages

The following list summarizes HTTP status codes for non-SOAP messages:

• For an asynchronous message, HTTP status codes 200 to 299 indicate a message status of Success.

• For a synchronous message, the HTTP status code 200 indicates a message status of Success.

• HTTP status code 404 indicates that the server has not found anything matching the Request-URI. In this case, an ExternalSystemContactException is generated on the integration gateway and the message status goes to Retry.

• HTTP status code 503 indicates that the server is currently unable to handle the request due to temporary server overload or maintenance. In this case, an ExternalSystemContactException is generated on the integration gateway and the message status goes to Retry.

• All other HTTP status codes generate an ExternalApplicationException. The status of these messages goes to Error.

Status Codes for SOAP Messages

This section summarizes HTTP status codes for SOAP messages.

If you are following SOAP 1.1 standards, the HTTP status code 500 indicates an Error.

If you are following SOAP 1.2 standards, the following HTTP status codes apply:

• HTTP status code 400 can mean any of the following:

  • InvalidMessageException

  • MessageMarshallingException

  • MessageUnmarshallingException

  • Malformed HTTP/XML

• HTTP status code 405 indicates that the method is not POST.

• HTTP status code 415 indicates the content type is not text/xml.

• HTTP status code 500 can mean any of the following:

  • ExternalSystemContactException

  • ExternalApplicationException

  • GeneralFrameworkException