- From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
- Date: Mon, 19 Dec 2005 18:07:14 -0800
- To: Yves Lafon <ylafon@w3.org>
- CC: xmlp-comments@w3.org
Yves Lafon wrote:
>
> Anish,
> The working group decided to close the issue with the following resolution:
>
> In part2, Table 17:
> Add the following line
> {
> Status Code:
> 303
>
> Reason Phrase:
> See Other
>
> Significance/Action:
> The requested resource has moved and the HTTP request SHOULD be retried
> using the URI carried in the associated Location header field as the new
> value for the http://www.w3.org/2003/05/soap/mep/ImmediateDestination
> property. The value of
> http://www.w3.org/2003/05/soap/features/web-method/Method is changed to
> "GET", the value of http://www.w3.org/2003/05/soap/mep/OutboundMessage is
> set to null. [Note: Status code 303 MUST NOT be sent unless the request
> SOAP envelope has been processed according to the SOAP processing model
> and the SOAP response is to be made available by retrieval from the URI
> provided with the 303.]
>
> Next Step:
> Init
> }
>
> The "3xx" line should be replaced by the following:
> {
> Status Code:
> 301,302,307
>
> Reason phrase:
> "Redirect"
>
> Significance/Action:
>
> The requested resource has moved.
> In the case of unsafe HTTP method, like POST or PUT, explicit confirmation
> is required before proceeding as follow.
> In the case of a safe method, like GET, or if the redirection has been
> approved, the HTTP request SHOULD be retried using the URI carried in the
> associated Location header field as the new value for the
> http://www.w3.org/2003/05/soap/mep/ImmediateDestination property.
>
> NextState:
> "Init" or "Fail"
> }
>
> Please tell the group if you agree or not with this resolution.
Yes, I do agree with this resolution.
-Anish
--
Received on Tuesday, 20 December 2005 02:07:22 UTC