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

Sander Fieten edited comment on EBXMLMSG-57 at 7/30/14 1:00 PM:
----------------------------------------------------------------

@Theo: With sync receipt you mean that a ebMS Receipt signal message is sent as the HTTP response? 

I am not sure whether we need to specify these HTTP codes in detail. As long as the returned codes are within the specifications ranges all implementations should accept and process messages. 


was (Author: sanderfieten):
@Theo: With sync receipt you mean that a ebMS Receipt signal message is sent as the HTTP response? 

I am not sure whether we need to {html}<b>specify</b>{html} these HTTP codes in detail. As long as the returned codes are within the specifications ranges all implementations should accept and process messages. 

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