.NET Core 3.1 WCF如何实现带MTOM和客户端证书的程序化绑定

核心问题说明 #

你遇到的问题由两个配置缺失导致：

• .NET Core 原生WsHttpBinding未暴露MessageEncoding配置入口，无法直接设置MTOM编码，会出现服务端返回MTOM格式和客户端期望的文本SOAP格式不匹配的异常
• 你之前编写的CustomBinding方案缺少和原.NET Framework配置对齐的协议版本、传输安全规则、配额/超时参数，导致认证或序列化失败

前置依赖 #

先确认已安装所需NuGet包：

• System.ServiceModel.Http
• WcfCoreMtomEncoder

完整实现代码 #

using System.ServiceModel;
using System.ServiceModel.Channels;
using System.Security.Cryptography.X509Certificates;
using WcfCoreMtomEncoder;
using System.Text;

// 1. 配置消息编码：对齐原WsHttpBinding的SOAP12 + WS-Addressing10协议，开启MTOM
var textEncoding = new TextMessageEncodingBindingElement(MessageVersion.Soap12WSAddressing10, Encoding.UTF8);
var mtomEncoding = new MtomMessageEncoderBindingElement(textEncoding);
// 对齐原配置的ReaderQuotas参数
mtomEncoding.ReaderQuotas.MaxStringContentLength = 50000000;
mtomEncoding.ReaderQuotas.MaxArrayLength = 50000000;
mtomEncoding.ReaderQuotas.MaxBytesPerRead = 50000000;
mtomEncoding.ReaderQuotas.MaxNameTableCharCount = 50000000;

// 2. 配置HTTPS传输：对齐原安全配置和性能参数
var transport = new HttpsTransportBindingElement
{
    // 原WsHttpBinding默认使用Buffered模式，如无特殊流传输需求可保持该配置，否则改为Streamed
    TransferMode = TransferMode.Buffered,
    MaxBufferPoolSize = 50000000,
    MaxReceivedMessageSize = 100000000,
    // 对应原配置 transport clientCredentialType="Certificate"
    ClientCredentialType = HttpClientCredentialType.Certificate
};

// 3. 构造自定义绑定，设置超时
var binding = new CustomBinding(mtomEncoding, transport)
{
    SendTimeout = TimeSpan.FromMinutes(3)
};

// 4. 初始化客户端，配置客户端证书
var remoteAddress = new EndpointAddress("https://***.au10tixservicesstaging.com/Au10tixBos2/Au10tixFromFilesWorker.svc");
var client = new Au10tixFromFilesWorkerClient(binding, remoteAddress);
client.ChannelFactory.Credentials.ClientCertificate.SetCertificate(
    StoreLocation.CurrentUser,
    StoreName.My,
    X509FindType.FindByThumbprint,
    "你的证书指纹"
);

配置验证说明 #

所有参数均和你原.NET Framework配置完全对齐：

• 消息编码：MTOM + SOAP12 + WS-Addressing10，和原wsHttpBinding默认协议一致
• 安全规则：传输层证书认证，匹配原security mode="Transport"配置
• 性能配额：sendTimeout、maxBufferPoolSize、maxReceivedMessageSize以及readerQuotas下的所有参数均和原配置取值相同

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