W3C home > Mailing lists > Public > xml-dist-app@w3.org > October 2001

Re: Issue #12 proposed resolution

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 3 Oct 2001 12:46:48 -0700
To: christopher ferris <chris.ferris@Sun.COM>
Cc: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
Message-ID: <20011003124642.A2556@mnot.net>

On Fri, Sep 28, 2001 at 10:11:33AM -0400, christopher ferris wrote:
> 6.3.2 HTTP 4xx Client Error
>       In general, a SOAP HTTP client SHOULD be prepared to handle
> 	any of the 4xx class of HTTP status codes. However, the
> 	following status codes have specific meaning within the
> 	context of this SOAP binding to HTTP.
>                 - A 400 Bad Request status SHALL be returned in the
>                   event that the
> 		    SOAP message contained within the body of an HTTP
>                   request message is not well formed XML or in the
>                   case where a
> 		    SOAP envelope was expected in the body of the
> 		    HTTP POST request and none was
>                   present.  
>                 - A 405 Method Not Allowed status MAY be returned
>                   in the event that the
> 		    method specified in the HTTP request is not POST.
> 		    As specified in RFC2616, the HTTP response MUST
> 		    include an Accept header that includes at least
> 		    POST.
>                 - A 415 Unsupported Media Type status code SHALL be
> 		    returned in the event that the encapsulation
> 		    mechanism used for the SOAP message in the HTTP
> 		    request is unsupported by the server.

The 5xx description specifies that an envelope should be included in
the body, whereas there is no such language here. Should we say
anything about the body content of these status codes?

Mark Nottingham
Received on Wednesday, 3 October 2001 15:46:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:16 UTC