[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=41944#comment-41944 ] 

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

The Drummond interop testing partners agreed on 200 for sync receipt on a successful message and all pulls, 204 on no receipt on a successful message, and 500 on returning a soap fault.

In addition we need to decide on http response codes for when an AS4 message times out during receipt eg. an incomplete envelope is received eg. 400 Bad Request

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