W3C home > Mailing lists > Public > xml-dist-app@w3.org > May 2002

Re: Proposal for dealing with other HTTP status codes

From: Mark Baker <distobj@acm.org>
Date: Thu, 30 May 2002 10:12:49 -0400
To: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Cc: xml-dist-app@w3.org
Message-ID: <20020530101249.C10964@www.markbaker.ca>


On Wed, May 29, 2002 at 12:33:07PM -0700, Henrik Frystyk Nielsen wrote:
> Table 11 refers to some but not all of the existing HTTP/1.1 status
> codes (see [0]). In addition to these status codes, HTTP provides an
> open-ended mechanism for supporting status codes defined by HTTP
> extensions (see [1] for a registration mechanism for new status codes).
> HTTP status codes are divided into status code classes as described in
> HTTP/1.1, section 6.1.1.

I assume you meant "RFC 2616, section 6.1.1".

> The SOAP HTTP binding follows the rules of any
> HTTP application which means that an implementation of the SOAP HTTP
> binding must understand the class of any status code, as indicated by
> the first digit, and treat any unrecognized response as being equivalent
> to the x00 status code of that class, with the exception that an
> unrecognized response must not be cached.


Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@acm.org
http://www.markbaker.ca        http://www.idokorro.com
Received on Thursday, 30 May 2002 10:04:29 UTC

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