- From: Marc Hadley <marc.hadley@sun.com>
- Date: Mon, 16 Sep 2002 17:46:19 -0400
- To: "Herve Ruellan" <ruellan@crf.canon.fr>
- Cc: xml-dist-app@w3.org
On Monday, Sep 2, 2002, at 08:17 US/Eastern, Herve Ruellan wrote: > > 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> > An alternative proposal is to change table 23 such that env:Sender is mapped to a HTTP 500 status code. This would then map cleanly with the existing table 17. This would have the added advantage of allowing us to remove table 23 since env:Sender is the only fault not currently mapped to a 500 status code. Regards, Marc. > 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 > > -- Marc Hadley <marc.hadley@sun.com> XML Technology Center, Sun Microsystems.
Received on Monday, 16 September 2002 17:46:51 UTC