6

I need to integrate my server with non-WCF client and suggested to change SOAP version in the headers. This can be done with <textMessageEncoding messageVersion="Soap11" /> element on a custom binding so i need to convert my current basicHttpBinding. How can i do that?

<basicHttpBinding>
    <binding>
        <security mode="TransportWithMessageCredential">
            <transport clientCredentialType="Windows"/>
            <message clientCredentialType="UserName" />
        </security>
    </binding>
</basicHttpBinding>
UserControl
  • 14,766
  • 20
  • 100
  • 187
  • A BasicHttpBinding already contains a TextMessageEncodingBindingElement with its MessageVersion property set to `Soap11`, so your reason for needing a custom binding seems wrong. – Chris Dickson Oct 06 '11 at 16:54

1 Answers1

7

The custom binding definition is:

<customBinding>
  <binding name="basicHttpEquivalent">
    <security authenticationMode="UserNameOverTransport" />
    <textMessageEncoding messageVersion="Soap11" />
    <httpsTransport />
  </binding>
</customBinding>

But this binding is exactly same as the basicHttpBinding you mentioned.

Ladislav Mrnka
  • 360,892
  • 59
  • 660
  • 670
  • 1
    would you happen to know where to find the custom binding equivalent for each of the standard bindings? I think I am going to require this to be able to use the enableUnsecureResponse attribute. Thanks, Rich – Richard Collette Oct 10 '11 at 15:45
  • 2
    @Richard: I'm using Reflector but you can try [BindingBox](http://webservices20.cloudapp.net/). – Ladislav Mrnka Oct 10 '11 at 15:51