[OASIS Issue Tracker] (EBXMLMSG-57) Expected HTTP response codes

[ https://issues.oasis-open.org/browse/EBXMLMSG-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41941#comment-41941 ] 

Sander Fieten edited comment on EBXMLMSG-57 at 11/4/14 7:58 PM:
----------------------------------------------------------------

I agree that some clarification for HTTP status codes is useful although the SOAP specification and WS-I basic profile already define which codes should be used.

From section 3.5.3 of the WS-I BP 2.0:
" R1124 An INSTANCE MUST use a 2xx HTTP status code on a response message that indicates the successful outcome of a HTTP request.

R1111 An INSTANCE SHOULD use a "200 OK" HTTP status code on a response message that contains an envelope that is not a fault.

R1112 An INSTANCE SHOULD use either a "200 OK" or "202 Accepted" HTTP status code for a response message that does not contain a SOAP envelope but indicates the successful outcome of a HTTP request."

So even that HTTP 1.1 specifies status code 204 for "No Content" it should not be used for empty SOAP responses.


was (Author: sanderfieten):
I agree that some clarification for HTTP status codes is useful although the SOAP specification and WS-I basic profile already define which codes should be used.

From section 3.4.4 of the WS-I BP 1.1:
" R1124 An INSTANCE MUST use a 2xx HTTP status code on a response message that indicates the successful outcome of a HTTP request.

R1111 An INSTANCE SHOULD use a "200 OK" HTTP status code on a response message that contains an envelope that is not a fault.

R1112 An INSTANCE SHOULD use either a "200 OK" or "202 Accepted" HTTP status code for a response message that does not contain a SOAP envelope but indicates the successful outcome of a HTTP request."

So even that HTTP 1.1 specifies status code 204 for "No Content" it should not be used for empty SOAP responses.

And from section 3.4.7 on errors:
"R1126 An INSTANCE MUST return a "500 Internal Server Error" HTTP status code if the response envelope is a Fault."

> Expected HTTP response codes
> ----------------------------
>
>                 Key: EBXMLMSG-57
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-57
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: AS4 Profile, Core Spec
>            Reporter: Pim van der Eijk
>
> The HTTP response codes should be clarified for various situations,  SOAP response, SOAP fault or empty.
> In ENTSOG interop we found some products provide 204 as return code for empty response and others 200.   



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)