Autofac - SingleInstance HttpClient

Question

Have read in various places that HttpClient should be reused rather than a new instance every time.

https://aspnetmonsters.com/2016/08/2016-08-27-httpclientwrong/

I am using Autofac on a project.

Would this be a good way of making a single instance of HttpClient available to inject into services?

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

Seems to work :)

So what is your question? (*it appears you answered it yourself on the last 2 lines*) — Igor, May 17 '18 at 14:52
Awesome. I guess I was just taken by surprise when it worked so easily :) — wingyip, May 17 '18 at 14:58

score 35 · Accepted Answer · answered May 17 '18 at 14:57

That's perfectly fine if you want one per whole application lifecycle however you might want to configure it different per API endpoint.

builder.Register(ctx => new HttpClient() {BaseAddress = new Uri("https://api.ipify.org")})
    .Named<HttpClient>("ipify")
    .SingleInstance();

builder.Register(ctx => new HttpClient() { BaseAddress = new Uri("https://api.postcodes.io") })
    .Named<HttpClient>("postcodes.io")
    .SingleInstance();

Then say we have a PostcodeQueryHandler

public class PostcodeQueryHandler
{
    public PostcodeQueryHandler(HttpClient httpClient) { }
}

We'd set up the bindings like

builder.Register(ctx => new PostcodeQueryHandler(ctx.ResolveNamed<HttpClient>("postcodes.io")))
        .InstancePerDependency();

I just want to add that `InstancePerDependency()` is the default behavior and you may skip it if you want. [InstancePerDependency Method](https://autofac.org/apidoc/html/B7A3F094.htm) — Ivo Gluhchev, Dec 05 '18 at 08:49
@Kevin Smith thanks for the alternative! It's nice to have both of these solutions here in one place. — ganjeii, Aug 30 '19 at 23:43

Autofac - SingleInstance HttpClient

1 Answers1

Linked