WSE003: The input was not a valid SOAP message

G

Gerrit

Hello!

I'm having some probelems with a Web Service.

Situation:
I'm using WSE 2.0 in the Web.config I have added

<httpHandlers>
<add type="Philips.ICIConnector.IciDispatcher.RoutingHandler,
IciDispatcher" path="*.ashx" verb="*" />
</httpHandlers>

So, all requests to ashx files end up in my RoutingHandler and there I
can analyze and do whatever is necessary.
Well, this part works as expected.



So here is the problem:

The system I'm intergating with and that uses my Web Service requires
that the following link does not return an error:

http://myserver/Dispatacher.ashx

When clicking that link I get the following error:

WSE003: The input was not a valid SOAP message

No surprise because in this case there is no SOAP message.



Question:

How can I fool the system to return in this situation no error message?
I thought about using SoapExtensions and BeforeDeserialize, but this
already implies that there is a valid SOAP message which I don't have
in this situation.
Is there anything I can do in IIS to catch such requests?
What am I doing wrong?

Any help appreciated.

Gerrit
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,995
Messages
2,570,236
Members
46,821
Latest member
AleidaSchi

Latest Threads

Top