tags:

views:

351

answers:

1

My C# sample client ASP.NET program successfully runs a call in my Axis2 server but the client does not seem to like the response.

I get:

Client found response content type of 'multipart/related; boundary=MIMEBoundaryurn_uuid_38D413ACFC9D56F28E1258666845186; type="application/xop+xml"; start="<0.urn:uuid:[email protected]>"; start-info="text/xml"', but expected 'text/xml'.

According to the MSDN forums I supposedly must enable MTOM but they only explain this for the now-obsolete WSE 3 package.

In the WCF space, for an ASP.NET program in C#, how to I enable MTOM or otherwise fix this response content-type mismatch? Actually, I'll need MTOM next.

A: 

This in normally that the client expects an xml response, but gets an error message from the server that it cannot parse.

Either log the reponse or use a network sniffer (fiddler) to check what you are getting back.

Shiraz Bhaiji
The reply is rejected by the client. From some other postings elsewhere I see I need to enable MTOM. Page 223 of "Learning WCF" shows a "<basicHttpBinding>" to do this, but the "Add Service Reference" doesn't make an app.conf file like it sometimes does and I don't know for sure where to go.
tpc1095