Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The client side of this protocol is simply a pass-through. That is, no additional timers or other state is required on the client side of this protocol. Calls made by the higher-layer protocol or application are passed directly to the transport, and the results returned by the transport are passed directly back to the higher-layer protocol or application.
Except where specified, protocol clients SHOULD interpret HTTP status codes returned by the protocol server as specified in [RFC2616], section 10, "Status Code Definitions".
This protocol allows protocol servers to notify protocol clients of application-level faults using SOAP faults. This protocol allows protocol servers to provide additional details for SOAP faults by including either a detail element as specified in [SOAP1.1], section 4.4, or a detail element as specified in [SOAP1.2-1/2007], section 5.4.5, that conforms to the XML schema definition (XSD) of the SOAP fault. Except where specified, these SOAP faults are not significant for interoperability, and protocol clients can interpret them in an implementation-specific manner.
This protocol allows protocol servers to perform implementation-specific authorization checks and notify protocol clients of authorization faults as specified previously in this section.