Is it possible to customize the message handler chain of the underlying HTTP client when using IDownstreamApi ?

[EnricoMassone]

I'm using the IDownstreamApi interface to call a downstream api from another API.

My use case is similar to the one showed here: the difference is that I'm not doing a call on behalf of the authenticated user, but instead on behalf of the application itself (client credentials flow for server to server communication).

Is it possible to customize the message handler chain of the underlying HTTP client when using this approach ? A typical example for this need is configuring resiliency strategies on the underlying HTTP client, to automatically retry over transient network errors.

When using the IDownstreamApi the actual configuration of the underlying HTTP client is hidden by the abstraction. Is it possible to access that in an idiomatic way using the library ? Is there a method or property designed to do that in the library ?

[EnricoMassone]

By checking the Issues section, it seems this question was already asked in the past (see #1740).

Based on my understanding, the proper solution to this problem is to call AddHttpClient("http-client-name") by using the very same name used to register the downstream api on the service collection (see here for a more detailed explanation).

Can you please confirm that this is the proper way to customize the underlying HttpClient when using IDownstreamApi ? I'm asking because, apart from the linked comment, I didn't find any mention to this pattern in the library documentation and examples.