SOAPAction header missing

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Brian Wetzel - 23 Aug 2004 22:55 GMT

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.PreProcessHttpMessage(SoapEnvel
ope message) at
Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(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.

Reply to this Message

Brian Wetzel - 24 Aug 2004 19:12 GMT

I figured out the problem. My firewall was removing the SOAPAction header.
Once I modified the configuration to allow the SOAPAction header everything
works fine.

> 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.PreProcessHttpMessage(SoapEnvel

> ope message) at

Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapSer

> verMessage message)
>
[quoted text clipped - 3 lines]
> If I run my client application from the web server, everything works fine.
> Does anyone know why the SOAPAction header would be getting lost.

Reply to this Message

SOAPAction header missing

Free Magazines