WSE012 error because of a missing SOAPAction in the http header

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

doug - 04 Dec 2006 19:52 GMT

I'm running a wse3 web service with just default settings (i.e. I do NOT have
a policy file, and I have the bare minimum wse3 settings in my web.config:
basically just <soapServerProtocolFactory..> and I have trace enabled so I
can see in the inbound and outbound messages).

Everything works fine when I have my test client send an empty SOAPAction in
the http header.

I get a WSE012 error when I have my test client send no SOAPAction http
header.

Is there anyway to make WSE3 not require a SOAPAction http header? Seems
silly to require it, given it's security vulnerabilities. What am I missing
here?

Thanks
Doug

Reply to this Message

Pablo Cibraro [MVP] - 04 Dec 2006 20:35 GMT

Hi Doug,

WSE does not require the SOAPAction http header, it actually uses the
wsa:Action header provided in the addressing headers. Is your service
receing that addressing header ?.
I think the problem is in the ASP.NET host, ASP.NET requires the SOAPAction
header in order to invoke the right web service. For instance, if you host
your wse service in a host different from ASP.NET you won't have that
problem.
Maybe, you should change the base class of your web service to be
"SoapService" (A base class provided by WSE, it can be hosted in any
transport) instead of "WebService" (The base class provided by ASP.NET for
web services).

Regards,
Pablo Cibraro.

> I'm running a wse3 web service with just default settings (i.e. I do NOT
> have
[quoted text clipped - 16 lines]
> Thanks
> Doug

Reply to this Message

WSE012 error because of a missing SOAPAction in the http header

Free Magazines