Editors Copy $Date: 2003/06/11 09:53:43 $ 01 March 2006

Abstract

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.

Status of this Document

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.

Appendix

1 Introduction

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.

1.1 Notational Conventions

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.

2 SOAP 1.1 request optional response HTTP Binding

This SOAP 1.1 request optional response HTTP binding, in conjunction with the SOAP 1.1 binding [SOAP 1.1], can be used for sending request messages with an optional SOAP response. This binding augments the SOAP 1.1 binding by allowing that the HTTP [RFC 2616] response MAY have a 202 status code and the response body MAY be empty. Note that the HTTP [RFC 2616] specification states "the 202 response is intentionally non-committal" and so any content in the response body, including a SOAP Envelope, MAY not be an expected SOAP response.