RE: [soapbuilders] SoapAction field in WSDL file
- There has been previous discussion in the SOAP community that the client
should respect the SOAPAction value specified by the server. I don't
think this is explicit anywhere in the spec, but it came up during SOAP
Therefore, the client should always include the "SOAPAction=X" header.
Note that for SOAP 1.1, the SOAPAction header is always required (for
firewall filtering reasons), just the value is optional. In SOAP 1.2 I
think there is going to be another mechanism for saying "this is a SOAP
message". Firewall admins will have the joy of having to maintain two
kinds of SOAP filters.
Note, Microsoft ASP.NET web services by default rely on the proper
SOAPAction value for routing, this behavior can be changed to route on
the request element in the message but it is less efficient.
Microsoft ASP.NET XML Web Services
From: Naresh Agarwal [mailto:nagarwal@...]
Sent: Friday, November 16, 2001 4:28 AM
Subject: [soapbuilders] SoapAction field in WSDL file
In the binding element of WSDL, there is SoapAction attribute in the
<definitions .... >
<binding .... >
<operation .... >
Now if a Soap Client *IN ANY SOAP IMPLEMENTATION* is written using
WSDL file , then *is it necessary* that Soap request would always
the *SoapAction=X* header.
Or the EXISTENCE of header *SoapAction=X* depends upon the Soap
Implementation used to write the Soap client.
Thanks & Regards,
This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues. Please stay on-topic.
To unsubscribe from this group, send an email to:
Your use of Yahoo! Groups is subject to