尽管更改了 Web 配置和主机工厂，但仍不断收到 WCF 错误

Question

在我的开发者盒子上，我的 WCF 服务运行良好，没有任何问题，但是当我将其部署到共享服务器上时，当我尝试访问我的服务时，我收到以下错误消息

https://www.mydomain.com/Admin/myservice/service.svc:

服务“/admin/myservice/service.svc”无法激活，因为 编译期间出现异常。异常消息是：这个 集合已包含一个带有 http 方案的地址。可以有 该集合中的每个方案至多有一个地址。如果您的服务是 托管在 IIS 中，您可以通过设置来解决问题 'system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled' 为 true 或指定 'system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters'。 参数名称：项目；该集合已包含地址 与方案http。此方案中每个方案最多可以有一个地址 收藏。如果您的服务托管在 IIS 中，您可以修复 通过设置出现问题 'system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled' 为 true 或指定 'system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters'。 参数名称：item

这是相关的 web.config 配置：

<serviceHostingEnvironment aspNetCompatibilityEnabled="true">
    <baseAddressPrefixFilters>
        <add prefix="https://www.mydomain.com/"/>
    </baseAddressPrefixFilters>
</serviceHostingEnvironment> 

这是我的主机工厂代码：

public class MyServiceServiceHostFactory : ServiceHostFactory
{
    protected override ServiceHost CreateServiceHost(Type serviceType, Uri[] baseAddresses)
    {
        ServiceHost serviceHost = null;

        serviceHost = CreateMyServiceServiceHost(baseAddresses);

        return serviceHost;
    }

    private static ServiceHost CreateMyServiceServiceHost(Uri[] baseAddresses)
    {
        // initialize service host
        ServiceHost serviceHost = new ServiceHost(typeof(OrderServices), baseAddresses);

        // create and add service endpoint binding using message and user name
        WSHttpContextBinding wsHttpContextEndpointBinding = new WSHttpContextBinding(SecurityMode.TransportWithMessageCredential);
        wsHttpContextEndpointBinding.Security.Message.ClientCredentialType = MessageCredentialType.UserName;
        wsHttpContextEndpointBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.None;
        wsHttpContextEndpointBinding.AllowCookies = true;

        // add meta data service
        ServiceMetadataBehavior metadataBehavior = new ServiceMetadataBehavior();
        metadataBehavior.HttpGetEnabled = false;
        metadataBehavior.HttpsGetEnabled = true;
        metadataBehavior.MetadataExporter.PolicyVersion = PolicyVersion.Policy15;

        ServiceAuthorizationBehavior serviceAuthorizationBehavior =
        serviceHost.Description.Behaviors.Find<ServiceAuthorizationBehavior>();
        serviceAuthorizationBehavior.PrincipalPermissionMode = PrincipalPermissionMode.UseAspNetRoles;

        ServiceDebugBehavior serviceDebugBehavior =
        serviceHost.Description.Behaviors.Find<ServiceDebugBehavior>();
        serviceDebugBehavior.IncludeExceptionDetailInFaults = true;

        ServiceCredentials serviceCredentials = new ServiceCredentials();
        serviceCredentials.UserNameAuthentication.UserNamePasswordValidationMode = UserNamePasswordValidationMode.Custom;
        serviceCredentials.UserNameAuthentication.CustomUserNamePasswordValidator =
            new MyServiceUserNamePasswordValidator((MyServiceMembershipProvider) Membership.Providers["MyServiceMembershipProvider"]);

        serviceHost.Description.Behaviors.Add(metadataBehavior);
        serviceHost.Description.Behaviors.Add(serviceCredentials);

        serviceHost.AddServiceEndpoint(typeof(IOrderServices), wsHttpContextEndpointBinding, "");

        // Add MEX endpoint
        serviceHost.AddServiceEndpoint(ServiceMetadataBehavior.MexContractName, MetadataExchangeBindings.CreateMexHttpsBinding(), "mex");
        return serviceHost;
    }
}

为什么我会收到此错误？每个技术文档都说我正在按照文档正确地做事。这是否与 SSL 问题或主机名问题有关？这让我难住了。

Answer 1

如果您在 localhost 上工作并使用框架 4.0，请通过设置以下选项仅使用一个端点：

<serviceHostingEnvironment multipleSiteBindingsEnabled="False" />

使用此选项，它将运行。

Answer 2

我找到了一个解决方案，尽管目前还不够。如果您正在运行 .NET 4 并保证运行它，请添加以下配置：

<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />

这应该会清除错误。如果您没有运行 .NET 4，则必须像我一样创建一个工厂，但您应该创建一个服务主机并在列表中指定一个地址。您选择的地址并非无足轻重。错误的 URL 可能是不需要的 URL，或更糟糕的是错误的方案，从而导致其他服务错误。理想情况下，您应该根据 HttpContext 和您想要的方案构建您的 Url。

这是一个精简版本：

public class MyServiceHostFactory : System.ServiceModel.Activation.ServiceHostFactory
{
    protected override ServiceHost CreateServiceHost(Type serviceType, Uri[] baseAddresses)
    {                        
        ServiceHost host;

        // This solution is less than ideal because the Uri at baseAddresses[0] could be the wrong Url or
        // the  wrong scheme. 
        host = new ServiceHost(serviceType, baseAddresses[0]);

        // A better solution, is to use the incoming request Uri and pass it in like so:
        host = new ServiceHost(serviceType, *** construct the url from Http Context ***);

        return host;
    }
}