在Autofac中注册SingleInstance的HttpClient是否为合理注入方式？

Great question! Let's break this down clearly:

First off, your approach is totally reasonable and aligns with established best practices for HttpClient usage.

As you noted, creating a new HttpClient instance every time you need to make a request is a bad practice—it leads to unnecessary socket resource exhaustion, since each new HttpClient spins up its own underlying handler and connection pool that doesn't get cleaned up immediately. By registering it as a singleton with Autofac using:

builder.Register(c => new HttpClient()).As<HttpClient>().SingleInstance();

you're ensuring a single instance is reused across your application, which avoids those resource leaks—and your "running normally" experience confirms this is working as intended.

A Quick Caveat to Keep in Mind #

While a singleton HttpClient is excellent for resource management, it has one gotcha: it caches DNS resolutions permanently by default. That means if the IP address behind the domain you're calling changes (common in cloud environments with load balancers or auto-scaled services), your HttpClient won't pick up the new IP until the application restarts.

If this is a concern for your use case, you can tweak the behavior by providing a custom HttpClientHandler when creating the instance:

builder.Register(c => 
{
    var handler = new HttpClientHandler
    {
        // Set a custom DNS refresh interval (e.g., 5 minutes)
        DnsRefreshTimeout = TimeSpan.FromMinutes(5)
    };
    return new HttpClient(handler);
}).As<HttpClient>().SingleInstance();

Alternatively, if you want more granular control over client lifetimes (like named clients or automatic handler rotation), you could integrate Autofac with IHttpClientFactory (built into ASP.NET Core), but that's an extra step—your current setup is perfectly valid for most scenarios.

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