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

RE: Issue #12: HTTP Status Codes 500 v 200

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Sat, 9 Jun 2001 10:25:43 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D034419F7@red-msg-07.redmond.corp.microsoft.com>
To: <dkgunter@lbl.gov>, <xml-dist-app@w3.org>

> From what I understand, SOAP is _not_ an extension of HTTP, instead 
>it is a protocol with an HTTP binding. I really hope that other 
>bindings remain possible.

We are only discussing the HTTP binding - SOAP itself can be used with
other protocols. This is clearly what SOAP/1.1 also states.

>Pushing SOAP status information up into HTTP seems to me like a hack 
>that's going to cause no end of headaches for other bindings (what 
>happens when an intermediary needs to translate from HTTP<->UDP? does 
>it have to parse all the messages going back HTTP-side so it can stick 
>in the right error code? ugh..). Also, it complicates the spec.

There is no pushing things around. We are specifically talking about
HTTP and SOAP together. The HTTP binding is silent about what happens
when using other bindings and the use of HTTP status codes is completely
orthogonal to this.

Henrik Frystyk Nielsen
mailto:henrikn@microsoft.com
Received on Saturday, 9 June 2001 13:26:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:01 GMT