- From: Herve Ruellan <ruellan@crf.canon.fr>
- Date: Mon, 02 Sep 2002 14:17:50 +0200
- To: xml-dist-app@w3.org
Dear all, While reading Section 7.5.1 [1] and Section 7.5.2 [2] of part 2, it seems that Table 17 [3] is not fully in sync with what the SOAP receiver might generate. A SOAP receiver might generate a 400 HTTP Status code either in its Init state or in its Receiving state. In the first case, the HTTP response contains no SOAP fault and accordingly, the SOAP requestor should transition to the Fail state, while in the second case, the HTTP response may contain a SOAP fault and if this is the case, the SOAP requestor should transition to the Sending+Receiving state. The proposal is to change the 400 line in Table 17 to take into account both these cases: <proposal> 400 Bad Request If the media type does not correspond to a SOAP message, indicates a problem with the received HTTP request message. This operation SHOULD NOT be repeated with the same message content. The message exchange is regarded as having completed unsuccessfully. Instantiated Property Value context:FailureReason "fail:BadRequest" Next State: Fail If the media type corresponds to a SOAP message, indicates a problem with the received SOAP message. This operation SHOULD NOT be repeated with the same message content. The local binding instance continues to receive the incoming message. Instantiated Property Value context:FailureReason "fail:BadRequest" Next State: Sending+Receiving </proposal> Regards, Hervé. [1] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part2.html#http-reqsoapnode [2] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part2.html#http-bindrespnode [3] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part2.html#tabreqstatereqtrans
Received on Monday, 2 September 2002 08:17:45 UTC