WCF单向SOAP服务：MessageInspector拦截失效，无法返回自定义SOAP Fault

我正在开发一个基于.NET Framework的WCF服务，作为接收客户端消息的提供者，仅支持单向（one-way）通信，服务必须使用SOAP协议。该服务的需求之一是生成自定义HTTP响应，其响应体（body）需包含符合W3C标准的SOAP Fault。

我尝试通过MessageInspector类实现该需求，但未达到预期效果。参考官方文档配置相关方法后仍无效，客户端发送的消息直接进入MyService类的SendData()方法。

当前服务托管于.NET Framework控制台应用，以下是核心实现代码与项目结构：

项目结构 #

MyService
DTO
-- CompositeType.cs
Utils
-- SchemaValidationBehavior.cs
-- SchemaValidationBehaviorExtensionElement.cs
-- SchemaValidationMessageInspector.cs
-- ValidationFault.cs
App.config
IMyService
MyService

核心实现代码 #

服务契约接口（IMyService） #

[ServiceContract]
public interface IMyService
{
    [OperationContract(IsOneWay = true)]
    void SendData(CompositeType composite);
}

服务实现类（MyService） #

public class MyService : IMyService
{
    public void SendData(CompositeType composite)
    {
        System.Diagnostics.Debugger.Break();
        Console.WriteLine(composite.BoolValue.ToString() + " " + composite.StringValue);
    }
}

消息检查器（SchemaValidationMessageInspector） #

class SchemaValidationMessageInspector : IClientMessageInspector, IDispatchMessageInspector
{
    XmlSchemaSet schemaSet;
    bool validateRequest;
    bool validateReply;
    bool isClientSide;
    [ThreadStatic] // 指示静态字段的值对每个线程都是唯一的
    bool isRequest;

    public SchemaValidationMessageInspector()
    {
    }

    public SchemaValidationMessageInspector(XmlSchemaSet schemaSet, bool validateRequest, bool validateReply, bool isClientSide)
    {
        this.schemaSet = schemaSet;
        this.validateRequest = validateRequest;
        this.validateReply = validateReply;
        this.isClientSide = isClientSide;
    }

    // IClientMessageInspector Interfaces -- Client message inspector
    public void AfterReceiveReply(ref Message reply, object correlationState)
    {
        Console.WriteLine("I am inside AfterReceiveReply");
    }

    public object BeforeSendRequest(ref Message request, IClientChannel channel)
    {
        Console.WriteLine("I am inside BeforeSendRequest");
        return null;
    }

    // IDispatchMessageInspector Interfaces -- Service message inspector
    public object AfterReceiveRequest(ref Message request, IClientChannel channel, InstanceContext instanceContext)
    {
        Console.WriteLine("I am inside AfterReceiveRequest");
        return null;
    }

    public void BeforeSendReply(ref Message reply, object correlationState)
    {
        Console.WriteLine("I am inside BeforeSendReply");
    }
}

端点行为（SchemaValidationBehavior） #

class SchemaValidationBehavior : IEndpointBehavior
{
    XmlSchemaSet schemaSet;
    bool validateRequest;
    bool validateReply;

    public SchemaValidationBehavior(){}

    public SchemaValidationBehavior(XmlSchemaSet schemaSet, bool inspectRequest, bool inspectReply)
    {
        this.schemaSet = schemaSet;
        this.validateReply = inspectReply;
        this.validateRequest = inspectRequest;
    }

    #region IEndpointBehavior Members

    public void AddBindingParameters(ServiceEndpoint endpoint, BindingParameterCollection bindingParameters){}

    public void ApplyClientBehavior(ServiceEndpoint endpoint, ClientRuntime clientRuntime)
    {
        Console.WriteLine("I am inside ApplyClientBehavior");
    }

    public void ApplyDispatchBehavior(ServiceEndpoint endpoint, EndpointDispatcher endpointDispatcher)
    {
        Console.WriteLine("I am inside ApplyDispatchBehavior");
        SchemaValidationMessageInspector inspector = new SchemaValidationMessageInspector();
        endpointDispatcher.DispatchRuntime.MessageInspectors.Add(inspector);
    }

    public void Validate(ServiceEndpoint endpoint){}

    #endregion
}

行为扩展元素（SchemaValidationBehaviorExtensionElement） #

public class SchemaValidationBehaviorExtensionElement : BehaviorExtensionElement
{
    public SchemaValidationBehaviorExtensionElement(){}

    public override Type BehaviorType
    {
        get
        {
            return typeof(SchemaValidationBehavior);
        }
    }

    protected override object CreateBehavior()
    {
        Console.WriteLine("I am inside ApplyClientBehavior");
        return new SchemaValidationBehavior();
    }

    [ConfigurationProperty("validateRequest", DefaultValue = false, IsRequired = false)]
    public bool ValidateRequest
    {
        get { return (bool)base["validateRequest"]; }
        set { base["validateRequest"] = value; }
    }

    [ConfigurationProperty("validateReply", DefaultValue = false, IsRequired = false)]
    public bool ValidateReply
    {
        get { return (bool)base["validateReply"]; }
        set { base["validateReply"] = value; }
    }
}

配置文件（App.config） #

<configuration>
    <appSettings>
        <add key="aspnet:UseTaskFriendlySynchronizationContext" value="true" />
    </appSettings>
    <system.web>
        <compilation debug="true" />
    </system.web>
    
    <system.serviceModel>

<!-- SERVICES -->
        <services>
            <service name="MyService.MyService" behaviorConfiguration="MyServiceBehavior">
                <endpoint address="" binding="basicHttpBinding" contract="MyService.IMyService" behaviorConfiguration="MyEndpointBehavior">
                    <identity>
                        <dns value="localhost" />
                    </identity>
                </endpoint>
                <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
                
                <host>
                    <baseAddresses>
                        <add baseAddress="http://localhost:9000/MyService/" />
                    </baseAddresses>
                </host>
            </service>
        </services>
<!-- SERVICES -->
        
<!-- BEHAVIORS -->      
        <behaviors>
            <endpointBehaviors>
                <behavior name="MyEndpointBehavior">
                    <schemaValidator validateRequest="true" validateReply="true"/>
                </behavior>
            </endpointBehaviors>

            <serviceBehaviors>
                <behavior name="MyServiceBehavior">
                    <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />
                    <serviceDebug includeExceptionDetailInFaults="true" />
                    <!-- Add the behavior extension here -->
                </behavior>
            </serviceBehaviors>
        </behaviors>
<!-- BEHAVIORS -->

<!-- EXTENSIONS -->
        <extensions>
            <behaviorExtensions>
                <add name="schemaValidator" type="MyService.Utils.SchemaValidationBehaviorExtensionElement, MyService" />
            </behaviorExtensions>
        </extensions>
<!-- EXTENSIONS -->
        
    </system.serviceModel>
</configuration>

控制台宿主代码 #

internal class Program
{
    static void Main(string[] args)
    {
        ServiceHost host = null;

        try
        {
            host = new ServiceHost(typeof(MyService.MyService));
            host.Open();
            Console.WriteLine($"Host for MyService started @ {DateTime.Now} {Environment.NewLine}Service hosted on http://localhost:9000");

            Console.ReadLine();
        }
        catch (Exception ex)
        {
            Console.WriteLine(ex.ToString());
            Console.ReadLine();
        }
        finally
        {
            host?.Close();
        }
    }
}

现有实现的问题 #

1. 单向操作特性限制：WCF单向操作默认是“fire and forget”模式，不会触发BeforeSendReply方法，服务处理完请求后不会主动返回响应，这是消息检查器未生效的核心原因。
2. 参数传递缺失：行为扩展元素未将配置的validateRequest/validateReply参数传递给行为类，行为类又未将参数传递给消息检查器，导致验证开关完全无效。
3. 请求拦截逻辑缺失：当前AfterReceiveRequest方法仅输出日志，没有实现请求验证和拦截逻辑，无法终止后续服务方法调用并返回Fault。

实现自定义SOAP Fault响应的步骤 #

步骤1：修复行为扩展元素的参数传递 #

更新SchemaValidationBehaviorExtensionElement的CreateBehavior方法，将配置参数传递给行为类：

protected override object CreateBehavior()
{
    Console.WriteLine("I am inside CreateBehavior");
    return new SchemaValidationBehavior(null, this.ValidateRequest, this.ValidateReply);
}

步骤2：修复端点行为的检查器初始化 #

更新SchemaValidationBehavior的ApplyDispatchBehavior方法，将验证参数传递给消息检查器：

public void ApplyDispatchBehavior(ServiceEndpoint endpoint, EndpointDispatcher endpointDispatcher)
{
    Console.WriteLine("I am inside ApplyDispatchBehavior");
    SchemaValidationMessageInspector inspector = new SchemaValidationMessageInspector(this.schemaSet, this.validateRequest, this.validateReply, false);
    endpointDispatcher.DispatchRuntime.MessageInspectors.Add(inspector);
}

步骤3：在消息检查器中拦截请求并返回SOAP Fault #

在AfterReceiveRequest方法中实现验证逻辑，验证失败时构造SOAP Fault并终止请求处理：

public object AfterReceiveRequest(ref Message request, IClientChannel channel, InstanceContext instanceContext)
{
    Console.WriteLine("I am inside AfterReceiveRequest");

    if (validateRequest)
    {
        // 替换为实际的请求验证逻辑（比如Schema校验）
        bool isValid = false;
        if (!isValid)
        {
            // 构造符合W3C标准的SOAP Fault
            FaultCode faultCode = FaultCode.CreateSenderFaultCode("InvalidRequest", "http://your-custom-namespace/faults");
            FaultReason faultReason = new FaultReason("请求数据不符合规范");
            MessageFault messageFault = MessageFault.CreateFault(faultCode, faultReason);
            
            // 创建包含Fault的响应消息
            request = Message.CreateMessage(request.Version, messageFault, "http://tempuri.org/IMyService/SendData");
            
            // 终止后续服务方法调用
            instanceContext.Abort();
            return null;
        }
    }
    
    return null;
}

步骤4：修改绑定配置确保返回响应 #

默认basicHttpBinding对单向操作不返回HTTP响应，需修改绑定配置：

<bindings>
    <basicHttpBinding>
        <binding name="CustomBasicHttpBinding">
            <security mode="None"/>
            <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
                maxBytesPerRead="4096" maxNameTableCharCount="16384" />
        </binding>
    </basicHttpBinding>
</bindings>

在服务端点中引用该绑定：

<endpoint address="" binding="basicHttpBinding" bindingConfiguration="CustomBasicHttpBinding" 
          contract="MyService.IMyService" behaviorConfiguration="MyEndpointBehavior">

关键说明 #

• 单向操作默认无响应，但通过手动构造响应消息并终止实例上下文，可以强制返回包含SOAP Fault的HTTP响应。
• SOAP Fault的构造必须符合W3C标准，指定正确的FaultCode（区分发送方/接收方错误）和FaultReason，确保客户端能正确解析。
• 验证逻辑需根据实际需求实现，比如加载XmlSchemaSet进行Schema校验，替换示例中的isValid判断逻辑。

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