I have a web service that uses WSE deployed on a Windows 2003 server. When
I run my client from a remote computer, I get the following exception:
System.Web.Services.Protocols.SoapHeaderException: WSE012: The input was not
a valid SOAP message because the following header is missing: SOAPAction. at
Microsoft.Web.Services2.WebServicesExtension.PrePr ocessHttpMessage(SoapEnvel
ope message) at
Microsoft.Web.Services2.WebServicesExtension.Befor eDeserializeServer(SoapSer
verMessage message)
After enabling tracing in the web.config I can see that there is no
SOAPAction header in the request.
If I run my client application from the web server, everything works fine.
Does anyone know why the SOAPAction header would be getting lost.