SOAP 1.1 Request Optional Response HTTP Binding

Editors Copy $Date: 2006/03/10 19:10:10 $ @@ @@@@ @@@@

This version:
soap11-ror-httpbinding.html/
Latest version:
http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/soap11-ror-httpbinding
Editor:
David Orchard, BEA Systems

Copyright © @@@@  W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.

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.

Table of Contents

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

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.

3. References

3.1 Normative References

[SOAP 1.1]
W3C Note "Simple Object Access Protocol (SOAP) 1.1", Don Box, David Ehnebuske, Gopal Kakivaya, Andrew Layman, Noah Mendelsohn, Henrik Nielsen, Satish Thatte, Dave Winer, 8 May 2000. (See http://www.w3.org/TR/SOAP/.)
[RFC 2616]
IETF "RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1", R. Fielding, J. Gettys, J. C. Mogul, H. Frystyk, T. Berners-Lee, January 1997. (See http://www.ietf.org/rfc/rfc2616.txt.)
[RFC 2119]
IETF "RFC 2119: Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, March 1997. (See http://www.ietf.org/rfc/rfc2119.txt.)

3.2 Informative References

[SOAP 1.2 Part 0]
W3C Recommendation "SOAP Version 1.2 Part 0: Primer", Nilo Mitra, 24 June 2003 (See http://www.w3.org/TR/2003/REC-soap12-part0-20030624/.)
[SOAP 1.2 Part 1]
W3C Recommendation "SOAP Version 1.2 Part 1: Messaging Framework", Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau, Henrik Frystyk Nielsen, 24 June 2003 (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)
[SOAP 1.2 Part 2]
W3C Recommendation "SOAP Version 1.2 Part 2: Adjuncts Framework", Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau, Henrik Frystyk Nielsen, 24 June 2003 (See http://www.w3.org/TR/2003/REC-soap12-part2-20030624/.)
[SOAP MediaType]
IETF "RFC 3902: The 'application/soap+xml' media type", M. Baker, M. Nottingham, September, 2004. (See http://www.ietf.org/rfc/rfc3902.txt.)
[RFC 3986]
IETF "RFC 3986: Uniform Resource Identifiers (URI): Generic Syntax", T. Berners-Lee, R. Fielding, L. Masinter, January 2005. (See http://www.ietf.org/rfc/rfc3986.txt.)