如何为特定HttpClient关联对应配置的TokenDelegatingHandler（不创建子类）？

现有以下C#接口与类（实现部分已省略以简化内容）：

public interface ITokenAuthenticationService { ... }

public class TokenAuthenticationService(
    IOptions<TokenOptions> options,
    HttpClient httpClient,
    TimeProvider? timeProvider = null
) : ITokenAuthenticationService
{ ... }

public class TokenDelegatingHandler(
    ITokenAuthenticationService tokenAuthenticationService
) : DelegatingHandler
{ ... }

public class MyService1(HttpClient client)
{ ... }

当前程序的服务注册配置如下：

var sp = new ServiceCollection()
    .Configure<TokenOptions>(configuration.GetRequiredSection("Service1"))
    .AddTransient<TokenDelegatingHandler>()
    .AddHttpClient<ITokenAuthenticationService, TokenAuthenticationService>()
    .ConfigureHttpClient(c => c.BaseAddress = new Uri("http://auth.service1.com")).Services

    // Service 1 配置
    .AddHttpClient<MyService1>()
        .ConfigureHttpClient(c => c.BaseAddress = new Uri("http://service1.com"))
        .AddHttpMessageHandler<TokenDelegatingHandler>().Services
        .BuildServiceProvider();
        
var bar = sp.GetRequiredService<MyService1>();
var result = await bar.DoSomethingAsync("baz");

TokenAuthenticationService必须依赖正确的TokenOptions配置才能正常工作。现在需要实现：让第二个服务MyService2使用带有独立配置的TokenDelegatingHandler，且不需要继承该Handler创建子类，同时关联到对应的专属HttpClient。

解决方案 #

要实现这个需求，核心是利用命名选项和命名HttpClient来隔离不同服务的配置与认证实例，既复用现有TokenDelegatingHandler，又避免依赖冲突。

1. 为每个服务注册独立的命名配置 #

不再注册全局的TokenOptions，而是为每个服务分别注册命名配置，这样不同的认证服务实例可以获取各自的配置：

// 注册Service1的专属命名配置
.Configure<TokenOptions>("Service1", configuration.GetRequiredSection("Service1"))
// 注册Service2的专属命名配置
.Configure<TokenOptions>("Service2", configuration.GetRequiredSection("Service2"))

2. 修改TokenAuthenticationService以支持命名配置 #

修改构造函数，通过IOptionsSnapshot<TokenOptions>获取指定名称的配置：

public class TokenAuthenticationService(
    IOptionsSnapshot<TokenOptions> optionsSnapshot,
    HttpClient httpClient,
    string configName, // 新增参数，指定要使用的配置名称
    TimeProvider? timeProvider = null
) : ITokenAuthenticationService
{
    // 根据名称获取对应配置
    TokenOptions options = optionsSnapshot.Get(configName);
    // ... 后续业务逻辑使用该配置
}

3. 为每个服务注册专属的TokenAuthenticationService实例 #

通过命名HttpClient和AddTypedClient，为每个服务创建绑定对应配置和认证地址的ITokenAuthenticationService实例：

// 注册Service1的专属认证服务
.AddHttpClient<ITokenAuthenticationService, TokenAuthenticationService>("Service1Auth")
.ConfigureHttpClient(c => c.BaseAddress = new Uri("http://auth.service1.com"))
.AddTypedClient((serviceProvider, httpClient) => 
    ActivatorUtilities.CreateInstance<TokenAuthenticationService>(
        serviceProvider, 
        httpClient, 
        "Service1" // 指定使用Service1的命名配置
    ))

// 注册Service2的专属认证服务
.AddHttpClient<ITokenAuthenticationService, TokenAuthenticationService>("Service2Auth")
.ConfigureHttpClient(c => c.BaseAddress = new Uri("http://auth.service2.com"))
.AddTypedClient((serviceProvider, httpClient) => 
    ActivatorUtilities.CreateInstance<TokenAuthenticationService>(
        serviceProvider, 
        httpClient, 
        "Service2" // 指定使用Service2的命名配置
    ))

4. 为每个服务的HttpClient绑定专属的TokenDelegatingHandler #

不再注册全局的TokenDelegatingHandler，而是在配置服务HttpClient时，动态创建绑定对应认证服务的Handler实例：

// 配置MyService1的HttpClient，绑定Service1的认证服务
.AddHttpClient<MyService1>()
.ConfigureHttpClient(c => c.BaseAddress = new Uri("http://service1.com"))
.AddHttpMessageHandler(serviceProvider => 
{
    // 获取Service1对应的专属认证服务实例
    var authService = serviceProvider.GetRequiredService<IHttpClientFactory>()
        .CreateClient("Service1Auth")
        .GetTypedClient<ITokenAuthenticationService>();
    return new TokenDelegatingHandler(authService);
})

// 配置MyService2的HttpClient，绑定Service2的认证服务
.AddHttpClient<MyService2>()
.ConfigureHttpClient(c => c.BaseAddress = new Uri("http://service2.com"))
.AddHttpMessageHandler(serviceProvider => 
{
    // 获取Service2对应的专属认证服务实例
    var authService = serviceProvider.GetRequiredService<IHttpClientFactory>()
        .CreateClient("Service2Auth")
        .GetTypedClient<ITokenAuthenticationService>();
    return new TokenDelegatingHandler(authService);
})

完整配置代码示例 #

var sp = new ServiceCollection()
    // 注册命名配置
    .Configure<TokenOptions>("Service1", configuration.GetRequiredSection("Service1"))
    .Configure<TokenOptions>("Service2", configuration.GetRequiredSection("Service2"))

    // 注册Service1专属认证服务
    .AddHttpClient<ITokenAuthenticationService, TokenAuthenticationService>("Service1Auth")
    .ConfigureHttpClient(c => c.BaseAddress = new Uri("http://auth.service1.com"))
    .AddTypedClient((sp, httpClient) => 
        ActivatorUtilities.CreateInstance<TokenAuthenticationService>(sp, httpClient, "Service1"))

    // 注册Service2专属认证服务
    .AddHttpClient<ITokenAuthenticationService, TokenAuthenticationService>("Service2Auth")
    .ConfigureHttpClient(c => c.BaseAddress = new Uri("http://auth.service2.com"))
    .AddTypedClient((sp, httpClient) => 
        ActivatorUtilities.CreateInstance<TokenAuthenticationService>(sp, httpClient, "Service2"))

    // 配置MyService1
    .AddHttpClient<MyService1>()
    .ConfigureHttpClient(c => c.BaseAddress = new Uri("http://service1.com"))
    .AddHttpMessageHandler(sp => 
    {
        var authService = sp.GetRequiredService<IHttpClientFactory>()
            .CreateClient("Service1Auth")
            .GetTypedClient<ITokenAuthenticationService>();
        return new TokenDelegatingHandler(authService);
    })

    // 配置MyService2
    .AddHttpClient<MyService2>()
    .ConfigureHttpClient(c => c.BaseAddress = new Uri("http://service2.com"))
    .AddHttpMessageHandler(sp => 
    {
        var authService = sp.GetRequiredService<IHttpClientFactory>()
            .CreateClient("Service2Auth")
            .GetTypedClient<ITokenAuthenticationService>();
        return new TokenDelegatingHandler(authService);
    })

    .BuildServiceProvider();

// 使用示例
var service1 = sp.GetRequiredService<MyService1>();
var result1 = await service1.DoSomethingAsync("baz");

var service2 = sp.GetRequiredService<MyService2>();
var result2 = await service2.DoSomethingAsync("foo");

关键说明 #

• 命名选项：通过带名称的Configure方法注册多组配置，结合IOptionsSnapshot可以按名称精准获取对应配置，避免全局配置冲突。
• 命名HttpClient：为每个服务的认证服务创建独立命名的HttpClient，确保各自的BaseAddress、请求策略等配置完全隔离。
• 动态创建Handler：在配置业务服务的HttpClient时，手动创建绑定专属认证服务的TokenDelegatingHandler，无需继承子类即可实现不同服务的认证隔离。

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