HttpClientFactory

You can use the Polly Policy Registry with Minimal APIs and HttpClientFactory. Read on to see how.

In the previous post I showed how to pass a Polly Policy Wrap into an Minimal API endpoint with dependency injection. In this post I’ll show to use the Policy Wrap with the Http Client Factory, passing that into the endpoint.

This post shows how to use Polly with .NET 6 if you are taking advantage of top-level statements, minimal API endpoints, and the HttpClientFactory.

This post shows how to use Polly with .NET 6; injecting a HttpClientFactory with a Retry policy into a controller.

Full source code here. I have been using HttpClientFactory for a while and have generally preferred using named clients over typed clients. With a named client you get the HttpClient just before you are going to use it, and you have full access to the HttpResponse at the point you make the call to the remote service.

Full source code here. Want to learn more about Polly? Check out my Pluralsight course on it. When I give talks on Polly I show how to use it in a Web API application that calls another Web Api application.

Full source code here. Over the past week I have written a few articles about HttpClientFactory and dependency injection in .NET Core 2.1. There is one scenario I didn’t deal with - calling a HttpClient from inside the Main method in Program.

Full source code here. This is a alternative to the approach described in a previous post. On a slack channel there was some discussion around the use of a little known extension method on HttpClientBuilder, ConfigureHttpClient.

Full source code here. There are some subtle issues in the way I use DI in this post, see here for an alternative if you don’t want to follow this approach

Full source code here. Want to learn more about Polly? Check out my Pluralsight course on it. Polly allows you to cache a response for reuse by a subsequent request, it supports both local an distributed caches, full information can be found here https://github.