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

Fault HTTP status 500

From: Pete Hendry <peter.hendry@capeclear.com>
Date: Mon, 08 Oct 2001 19:15:49 +0100
Message-ID: <3BC1ED55.F67E6358@capeclear.com>
To: xml-dist-app@w3.org

I'd like clarification on the reason for using an HTTP error status to indicate a soap fault. I'd also like the reason
behind using 500 which is the 'Internal Server Error' code.

In my opinion, if the message reached the SOAP processor, then HTTP has done its job and then it is on to the
application to generate errors in its own way. SOAP has its own error mechanism (fault) which is separate from HTTP.
HTTP is simply the SOAP carrier. Why do we therefore have to use an HTTP error code to indicate a fault within the SOAP
application?

I would prefer that HTTP error codes be used by the web server and the SOAP processor return a fault with HTTP status
200 (i.e. not an HTTP error). I see no reason that the code handing off to the SOAP processor should be concerned with
the fact that the returned message contains a Fault. That is beyond its responsibility.

Thanks for any clarification on this.

Pete
Received on Monday, 8 October 2001 14:16:26 GMT

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