Re: [SOAP] SOAPAction soap 1.1

> I believe the SOAPAction was just a specfic thing for the http transport and it > is ment to be used be used by routers so they could route soap calls > differently. I believe this got droped with soap 1.2 Well I don't know about dropped... At w3 the soap primer says ---8<--- a.. In the SOAP 1.2 HTTP binding, the SOAPAction HTTP header defined in SOAP 1.1 has been removed, and a new HTTP status code 427 has been sought from IANA for indicating (at the discretion of the HTTP origin server) that it is required by the server application. The contents of the former SOAPAction HTTP header are now expressed as a value of an "action" attribute of the "application/soap+xml" media type that is signaled in the HTTP binding. b.. In the SOAP 1.2 HTTP binding, the Content-type header should be "application/soap+xml" instead of "text/xml" as in SOAP 1.1. The IETF registration for this new media type is pending [13]. c.. SOAP 1.2 provides a finer grained description of use of the various 2xx, 3xx, 4xx HTTP status codes. d.. Support of the HTTP extensions framework has been removed from SOAP 1.2. e.. SOAP 1.2 provides an additional message exchange pattern which may be used as a part of the HTTP binding that allows the use of HTTP GET for "safe" information retrievals. ---8<--- What I meant was how it is used in 1.1 today SOAPAction: yournamespace#procedure or SOAPAction: yournamespace or SOAPAction: function