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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Theo Kramer commented on EBXMLMSG-57:
-------------------------------------

Yes - sync receipt meaning an ebMS Receipt signal sent as HTTP response.

Also according to SOAP 1.2 a SOAP fault may be included with an HTTP 400 response. So only 500 for returning a SOAP fault is not sufficient. This also has implications for standard Java libs that throw an exception on a BAD_REQUEST (400) and ignoring the associated SOAP fault.

Also see table 20 in section 7.5.1.2 and 7.5.2.2 of the SOAP 1.2 spec

> 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)