1.7 Versioning and Capability Negotiation

This specification covers versioning issues in the following areas:

  • Supported transports: This protocol can use SOAP, TCP, HTTP, or HTTPS as a transport. Details are provided in Transport (section 2.1).

  • Protocol versions: Only one version of this protocol is currently defined.

  • Security and authentication methods: This protocol relies on the security provided by the following:

  • Capability negotiation: An implementation of this protocol with SOAP over HTTP can interoperate with other implementations of SOAP over HTTP that implement [SOAP1.1]. This protocol provides a mechanism to distinguish an implementation of this protocol from other implementations of SOAP over HTTP. A client role of this protocol indicates this by using the User-Agent header as specified in Versioning and Capability Negotiation (section 2.1.3.1.1.1). The server role uses this information when sending a SOAP fault as specified in ServerFault (section 2.2.2.17).