为何请求未被签名自定义绑定覆盖？我需实现支持签名头的自定义绑定

Hey there! Let's break down why your custom signed binding isn't being applied to your requests. Here are the most common culprits to check:

This is the most frequent issue—even if you build the perfect binding, it won't do anything unless you explicitly assign it to your service or client endpoint.

For example, on the server side, make sure you're wiring the binding to your service host's endpoint:

// Build the full custom binding
var securityElement = CreateSecurityBindingElement();
var encodingElement = new TextMessageEncodingBindingElement();
var transportElement = new HttpsTransportBindingElement();
var customBinding = new CustomBinding(securityElement, encodingElement, transportElement);

// Attach it to your service endpoint
var host = new ServiceHost(typeof(YourService));
host.AddServiceEndpoint(typeof(IYourServiceContract), customBinding, "https://your-service-url");

If you're using config files instead of code, double-check that the binding name in your <customBinding> section matches the binding attribute on your <endpoint> element, and that all three binding elements are correctly defined in order.

Your code snippet starts setting up the security element, but there might be missing pieces that prevent signature headers from working:

• Ensure the certificate you're using is valid, accessible (correct store location, proper permissions), and referenced correctly in both client and server.
• Explicitly enable header signature protection if it's not set by default:

  private BindingElement CreateSecurityBindingElement() {
      SecurityBindingElement security = SecurityBindingElement.CreateCertificateOverTransportBindingElement();
      security.MessageSecurityVersion = MessageSecurityVersion.WSSecurity11WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10;
      // Enable full header signature protection
      security.SetSignatureProtection(true);
      return security;
  }
  

• Verify your MessageSecurityVersion is fully specified (truncating it can break expected security behavior).

Check if there's a higher-priority binding configuration that's taking precedence:

• If you're mixing code-based and config-based bindings, WCF might be picking the config one first depending on initialization order.
• In ASP.NET-compatible WCF services, default bindings from <system.serviceModel> might be applied automatically if you don't explicitly override them.

Confirm that your test requests are hitting the endpoint that uses your custom binding, not a default endpoint (e.g., a basic HTTP endpoint you might have set up for testing).

Custom bindings require a strict order: Security → Message Encoding → Transport. You mentioned the right elements, but double-check that you're passing them to CustomBinding in this exact sequence—swapping order will break the binding's functionality entirely.

If this is a client-side issue, ensure your client's binding mirrors the server's custom binding exactly. Mismatched security settings (like different MessageSecurityVersion or certificate configurations) will cause WCF to fall back to default behavior or fail the request entirely.

Bonus: Enable WCF tracing to debug #

To get concrete visibility into which binding is being used, enable WCF tracing in your config file:

<system.diagnostics>
    <sources>
        <source name="System.ServiceModel" switchValue="Information, ActivityTracing" propagateActivity="true">
            <listeners>
                <add name="traceListener" type="System.Diagnostics.XmlWriterTraceListener" initializeData="wcf-trace.svclog" />
            </listeners>
        </source>
    </sources>
</system.diagnostics>

Use the SvcTraceViewer tool to open the generated log—it will show you exactly which binding is loaded and applied to each request.

内容的提问来源于stack exchange，提问作者Wouter S