SOAP (originally Simple Object Access Protocol) is a messaging protocol specification for exchanging structured information in the implementation of web services in computer networks Its purpose is to induce extensibility , neutrality and independence. The SOAP Fault element holds errors and status information for a SOAP message. So if you want to offer services to clients over the internet, while it will not be impossible with CORBA, you will have to overcome some firewall-related obstacles. Headers – Emitted when the SOAP Headers are not empty.
SOAP messages are formatted in XML and are typically sent using HTTP (hypertext transfer protocol). Well here is at last one concluding point: a GET request and its cache-control headers are indeed friendly with web caches. SOAP is a messaging protocol and in a nutshell is just another XML language.
REST does not contain an additional messaging layer and focuses on design rules for creating stateless services. ReturnFault: return an Invalid XML SOAP fault on a bad request, default: false. SOAP fault: In case a SOAP node fails to process a SOAP message, it adds the fault information to the SOAP fault element.
The Content-Type header for a SOAP request and response defines the MIME type for the message and the character encoding (optional) used for the XML body of the request or response. Note: All immediate child elements of the Header element must be namespace-qualified.
However, it is dependent on other protocols such as the HTTP and SMTP for the negotiation and transmission of messages. Note that in SOAP v1, customizing the API did not involve changing the WSDL. SOAP is XML=plain text so firewalls could inspect the content of HTTP body and block accordingly.