[ACCEPTED]-WCF and Soap 1.1-soap
The basicHttpBinding does use SOAP 1.1 - but in that case, you 6 would have a content type of application/soap+xml.
Since your 5 client is sending text/xml - any chance they're 4 expecting a REST interface? This would be 3 handled by the WCF webHttpBinding.
Read more about REST 2 in WCF on the MSDN WCF REST Developer Center and check out the Pluralsight 1 screencast series on WCF REST - highly recommended!
Generally when we get a message / error 3 in a web service which includes the text:
content type 'text/xml'
It 2 means that the web server returned an error 1 page instead of the expected xml response.
I had the exact same issue - the definition 5 was saying that it was soap 1.2 but expecting 4 1.1 as the content-type was different.
I 3 found that if i adjusted my server configuration 2 from:
...
<endpoint address="" .../>
<host>
<baseAddresses>
<add baseAddress="http://localhost:8001/services/fooService" />
</baseAddresses>
</host>
...
To:
...
<endpoint address="fooService" .../>
<host>
<baseAddresses>
<add baseAddress="http://localhost:8001/services" />
</baseAddresses>
</host>
...
The wsdl exposed it as Soap 1.1 1 this time.
More Related questions
We use cookies to improve the performance of the site. By staying on our site, you agree to the terms of use of cookies.