WCF service using basicHttpBinding is still sending content type “text/xml”?

So do they need SOAP 1.1 or application/soap+xml; charset=utf-8 because SOAP 1.1 specification says that the request must have text/xml media type application/soap+xml is media type for SOAP 1.2. Forcing WCF to use SOAP 1.1 with application/soap+xml (= invalid SOAP) would require bigger changes then changing binding. You will need some custom message encoder or perhaps transport channel.

So do they need SOAP 1.1 or application/soap+xml; charset=utf-8 because SOAP 1.1 specification says that the request must have text/xml media type. Application/soap+xml is media type for SOAP 1.2. Forcing WCF to use SOAP 1.1 with application/soap+xml (= invalid SOAP) would require bigger changes then changing binding. You will need some custom message encoder or perhaps transport channel.

The only reason I'm thinking that I should be sending application/soap+xml is the text of the error message. I had been using wsHttpBinding, which AIUI would have been using SOAP 1.2. – Jeff Dege Nov 11 at 13:36 OK - I went back and checked. Using the wsHttpBinding, my service was sending application/soap+xml, and now using basicHttpBinding, it's sending text/xml.

So things should be fine. I'd not snooped the wsHttpBinding, but from the message I'd assumed that it had been sending text/xml and should have been sending application/soap+xml.It seems to have been the other way round. Thanks.

– Jeff Dege Nov 11 at 15:31 Be aware that wsHttpBinding uses SOAP 1.2 – Ladislav Mrnka Nov 11 at 15:52.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.