In the document http://www.w3.org/TR/2007/REC-soap12-part0-20070427/ there is a conflict between the primer and the normative version. The primer states:
If an error occurs processing the request, the HTTP binding specification requires that a HTTP 500 "Internal Server Error" be used with an embedded SOAP message containing a SOAP fault indicating the server-side processing error.
The primer then shows Example 11 with an HTTP status code of 500 and a response body. This conflicts with the
http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#http-reqbindwaitstate normative document where it states in several places that only a status of 200 receives an HTTP body with a SOAP message. Section 7.5.1.3 Sending+Receiving and section 7.5.1.4 both state:
Only in the case that a status code 200 is received, the response message is assumed to contain a SOAP envelope serialized according to the rules for carrying SOAP messages in the media type given in the Content-Type header field.
Section 7.5.2.2 covering the responding SOAP node states:
HTTP Entity Body: Only if status line is 200, the SOAP message serialized according to the rules for carrying SOAP messages in the media type given by the Content-Type header field.
These documents appear to be in conflict, since the primer shows an HTTP status code of 500 returning a SOAP envelope. This is a pretty major discrepancy.
Sincerely,
John Landis
_________________________________________________________________
Get in touch in an instant. Get Windows Live Messenger now.
http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008