[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [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=47741#comment-47741 ] Sander Fieten commented on EBXMLMSG-57: --------------------------------------- In WS-I BP 2.0 which is declared normative in AS4 the following requirement is included: R1107 A RECEIVER MUST interpret a SOAP message as a Fault when the soap12:Body of the message has a single soap12:Fault child. This requirement implies a MSH should not use the HTTP status code at all but should check the SOAP body for Fault elements. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]