绑定不在“双模式”下工作(webhttpbinding和basichttpbinding)

正如异常所说,第二个端点有(1)webhttpbehavior和(2)basichttpbinding,它们是不兼容的。我认为您可能只想从第二个端点删除WebhttpBehavior。

答案是:

(布赖恩说得很清楚,但这就是造成这种情况的原因)

Visual Studio在客户端为我创建了一个“custombinding”元素,但没有什么帮助。为了让它正常工作,我将客户端app.config改为:

    <system.serviceModel>
    <bindings>
        <basicHttpBinding>
            <binding name="WebHttpBinding_ISecurityBroker" allowCookies="true" />
        </basicHttpBinding>     
    </bindings>
    <client>         
        <endpoint binding="basicHttpBinding" bindingConfiguration="WebHttpBinding_ISecurityBroker"
            contract="Client.API.WCF.ISecurityBroker" name="WebHttpBinding_ISecurityBroker" />
    </client>
</system.serviceModel>

我的服务器端web.config是:

<system.serviceModel>
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
    <behaviors>
        <endpointBehaviors>

            <behavior name="webHttpEnablingBehaviour">

                <webHttp />
            </behavior>
        </endpointBehaviors>
        <serviceBehaviors>

            <behavior name="webHttpEnablingBehaviour">
                <serviceMetadata httpGetEnabled="true" />
            </behavior>

        </serviceBehaviors>
    </behaviors>
    <services>
        <service
          name="IWW.MIGTurbo2.WCF.Security.SecurityBroker" behaviorConfiguration="webHttpEnablingBehaviour">
            <endpoint contract="IMetadataExchange" binding="mexHttpBinding" address="mex" />

            <endpoint address="" 
                binding="webHttpBinding"
                bindingConfiguration="default"
                contract="IWW.MIGTurbo2.WCF.Security.ISecurityBroker"
                behaviorConfiguration="webHttpEnablingBehaviour">
            </endpoint>
            <endpoint address="other"
                binding="basicHttpBinding"
                bindingConfiguration="default"
                contract="IWW.MIGTurbo2.WCF.Security.ISecurityBroker">
            </endpoint>
        </service>

    </services>
    <client />
    <bindings>
        <webHttpBinding>
            <binding name="default" ></binding>
        </webHttpBinding>
        <basicHttpBinding> 
            <binding name="default" allowCookies="true"></binding>
        </basicHttpBinding>
    </bindings>
</system.serviceModel>

我有以下代码可以在我的客户机应用程序(WinForms)中连接:

using (SecurityBrokerClient securityBrokerClient = new SecurityBrokerClient())
        {
            string securityBrokerUrl=url+"api/wcf/SecurityBroker.svc";
            securityBrokerUrl += "/other";
            securityBrokerClient.Endpoint.Address = new System.ServiceModel.EndpointAddress(securityBrokerUrl);
            securityBrokerClient.Open();
            securityBrokerClient.Login(username, password, "MIGTurbo2Admin");
        }

我在配置文件中看到的第一个也是最重要的问题是端点配置。

<endpoint address="" binding="webHttpBinding"  bindingConfiguration="default"
          contract="IWW.MIGTurbo2.WCF.Security.ISecurityBroker"
          behaviorConfiguration="webHttpEnablingBehaviour">
 </endpoint>

            <!-- This is for WinForms clients, but isn't working -->

 <endpoint address="" binding="basicHttpBinding" bindingConfiguration="default"
            contract="IWW.MIGTurbo2.WCF.Security.ISecurityBroker"
             behaviorConfiguration="webHttpEnablingBehaviour">
 </endpoint>

这里我们没有在标记中指定任何地址和listenuri。因此,我们将拥有这些的默认值,并且对于2个端点,我们将拥有相同的地址和相同的listenuri(即默认值)。

所以问题来了。 1。不能使用具有相同listenuri和相同地址的不同类型的绑定。但是在您的情况下,当您为地址指定空值时,两个端点将具有相同的值。

决议: 1。为两个端点指定不同的地址,而不是将其保留为空。

<endpoint address="Rest" binding="webHttpBinding"  bindingConfiguration="default"
          contract="IWW.MIGTurbo2.WCF.Security.ISecurityBroker"
          behaviorConfiguration="webHttpEnablingBehaviour">
 </endpoint>

            <!-- This is for WinForms clients, but isn't working -->

 <endpoint address="WebForm" binding="basicHttpBinding" bindingConfiguration="default"
            contract="IWW.MIGTurbo2.WCF.Security.ISecurityBroker"
             behaviorConfiguration="webHttpEnablingBehaviour">
 </endpoint>

因此,即使我们使用不同的绑定和相同的listenuri(如果我们不指定listenuri,它将是默认的),因为地址(相对地址)值不同,它也可以正常工作。