Henrik, 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. Excellent! MB -- Mark Baker, CTO, Idokorro Mobile (formerly Planetfred) Ottawa, Ontario, CANADA. distobj@acm.org http://www.markbaker.ca http://www.idokorro.comReceived on Thursday, 30 May 2002 10:04:29 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:10 GMT