Copyright © W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use, and software licensing rules apply.
SOAP Version 1.1 provides an HTTP binding for exchanging a request and a response. This binding provides a "request optional response" refinement that enables an HTTP response with status code 202 to have a SOAP envelope or to be empty.
This document is an editors' copy that has no official standing.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.
1 Introduction
1.1 Notational Conventions
2 SOAP 1.1 request optional response HTTP Binding
3 References
3.1 Normative References
3.2 Informative References
A Change Log (Non-Normative)
The SOAP 1.1 request optional response Binding (this document) defines modification to the SOAP 1.1 HTTP Binding [SOAP 1.1] that enables an HTTP response with status code 202 to have a SOAP envelope or to be empty.
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC 2119].
With the exception of examples and sections explicitly marked as "Non-Normative", all parts of this specification are normative.
This SOAP 1.1 request optional response HTTP binding can be used for sending request messages with an optional response. For such messages, the HTTP [RFC 2616] response MUST be a 202 status code and the response body MAY be empty.