WCF SOAP 1.2 service expecting SOAP 1.1 content type

Question

I\'m building a WCF web service that requires interop with non-WCF clients (in fact, there will be no WCF clients).

I\'ve already written a WSDL using SOAP 1.2 (as p

Answer 1

The only thing I can think with it is that because you've not specified a binding in a lot of detail, and its using HTTP (as per this: "Listen at 'http://mycomputer/MyWs.svc'") then is it using the default (i.e. basicHttpBinding) for this, which is creating the mismatch?

Answer 2

I had the same issue when I had multiple bindings on my service. When I removed all bindings and only left one unnamed binding in place, the error message disappeared.

Answer 3

Please check this link How to: Configure WCF Service to Interoperate with ASP.NET Web Service Clients .

To configure a Windows Communication Foundation (WCF) service endpoint to be interoperable with ASP.NET Web service clients, use the System.ServiceModel.BasicHttpBinding type as the binding type for your service endpoint.

Also, defining two endpoints you can use HTTP and HTTPS versions of the same service