aws实例类型 c5.4_用于ASP.NET Core 2.1中类型化HttpClient实例的HttpClientFactory

aws实例类型 c5.4

I'm continuing to upgrade my podcast site https://www.hanselminutes.com to .NET Core 2.1 running ASP.NET Core 2.1. I'm using Razor Pages having converted my old Web Matrix Site (like 8 years old) and it's gone very smoothly. I've got a ton of blog posts queued up as I'm learning a ton. I've added Unit Testing for the Razor Pages as well as more complete Integration Testing for checking things "from the outside" like URL redirects.

我将继续将播客站点https://www.hanselminutes.com升级到运行ASP.NET Core 2.1的.NET Core 2.1。 我使用的Razor Pages转换了旧的Web Matrix网站(例如8年之久)，并且运行非常顺利。 在学习大量知识的同时，我排队的博客帖子也很多。 我添加了Razor页面的单元测试，以及用于检查“外部”内容(例如URL重定向)的更完整的集成测试。

My podcast has recently switched away from a custom database over to using SimpleCast and their REST API for the back end. There's a number of ways to abstract that API away as well as the HttpClient that will ultimately make the call to the SimpleCast backend. I am a fan of the Refit library for typed REST Clients and there are ways to integrate these two things but for now I'm going to use the new HttpClientFactory introduced in ASP.NET Core 2.1 by itself.

我的播客最近已从自定义数据库切换到后端使用SimpleCast及其REST API 。 有多种方法可以提取该API以及最终将调用SimpleCast后端的HttpClient。 我是用于类型化REST客户端的Refit库的支持者，可以通过多种方式集成这两种内容，但是现在，我将使用ASP.NET Core 2.1中引入的新HttpClientFactory本身。

Next I'll look at implementing a Polly Handler for resilience policies to be used like Retry, WaitAndRetry, and CircuitBreaker, etc. (I blogged about Polly in 2015 - you should check it out) as it's just way too useful to not use.

接下来，我将研究实现针对弹性策略(例如Retry，WaitAndRetry和CircuitBreaker等)的Polly Handler (我在2015年写过有关Polly的博客-您应该检查一下)，因为它太有用了而无法使用。

HttpClient Factory lets you preconfigure named HttpClients with base addresses and default headers so you can just ask for them later by name.

HttpClient Factory允许您使用基地址和默认标头预先配置名为HttpClient的HttpClient，因此您以后可以按名称要求它们。

public void ConfigureServices(IServiceCollection services)
{
    services.AddHttpClient("SomeCustomAPI", client =>
    {
        client.BaseAddress = new Uri("https://someapiurl/");
        client.DefaultRequestHeaders.Add("Accept", "application/json");
        client.DefaultRequestHeaders.Add("User-Agent", "MyCustomUserAgent");
    });
    services.AddMvc();
}

Then later you ask for it and you've got less to worry about.

然后，稍后您要它，而您不必担心。

using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;

namespace MyApp.Controllers
{
    public class HomeController : Controller
    {
        private readonly IHttpClientFactory _httpClientFactory;

        public HomeController(IHttpClientFactory httpClientFactory)
        {
            _httpClientFactory = httpClientFactory;
        }

        public Task<IActionResult> Index()
        {
            var client = _httpClientFactory.CreateClient("SomeCustomAPI");
            return Ok(await client.GetStringAsync("/api"));
        }
    }
}

I prefer a TypedClient and I just add it by type in Startup.cs...just like above except:

我更喜欢TypedClient，我只是在Startup.cs中按类型添加它...就像上面一样，除了：

services.AddHttpClient<SimpleCastClient>();

Note that I could put the BaseAddress in multiple places depending on if I'm calling my own API, a 3rd party, or some dev/test/staging version. I could also pull it from config:

请注意，根据我要调用自己的API，第三方还是某些开发/测试/登台版本，我可以将BaseAddress放在多个位置。 我也可以从配置中拉出它：

services.AddHttpClient<SimpleCastClient>(client => client.BaseAddress = new Uri(Configuration["SimpleCastServiceUri"]));

Again, I'll look at ways to make this even simpler AND more robust (it has no retries, etc) with Polly soon.

再次，我将研究如何尽快使Polly变得更简单，更强大(没有重试等)。

public class SimpleCastClient
{
    private HttpClient _client;
    private ILogger<SimpleCastClient> _logger;
    private readonly string _apiKey;

    public SimpleCastClient(HttpClient client, ILogger<SimpleCastClient> logger, IConfiguration config)
    {
        _client = client;
        _client.BaseAddress = new Uri($"https://api.simplecast.com"); //Could also be set in Startup.cs
        _logger = logger;
        _apiKey = config["SimpleCastAPIKey"]; 
    }

    public async Task<List<Show>> GetShows()
    {
        try
        {
            var episodesUrl = new Uri($"/v1/podcasts/shownum/episodes.json?api_key={_apiKey}", UriKind.Relative);
            _logger.LogWarning($"HttpClient: Loading {episodesUrl}");
            var res = await _client.GetAsync(episodesUrl);
            res.EnsureSuccessStatusCode();
            return await res.Content.ReadAsAsync<List<Show>>();
        }
        catch (HttpRequestException ex)
        {
            _logger.LogError($"An error occurred connecting to SimpleCast API {ex.ToString()}");
            throw;
        }
    }
}

Once I have the client I can use it from another layer, or just inject it with [FromServices] whenever I have a method that needs one:

一旦有了客户端，就可以从另一层使用它，或者只要有需要的方法，就可以用[FromServices]注入它：

public class IndexModel : PageModel
{
    public async Task OnGetAsync([FromServices]SimpleCastClient client)
    {
        var shows = await client.GetShows();
    }
}

Or in the constructor:

或在构造函数中：

public class IndexModel : PageModel
{
    private SimpleCastClient _client;

    public IndexModel(SimpleCastClient Client)
    {
        _client = Client;
    }
    public async Task OnGetAsync()
    {
        var shows = await _client.GetShows();
    }
}

Another nice side effect is that HttpClients that are created from the HttpClientFactory give me free logging:

另一个不错的副作用是，从HttpClientFactory创建的HttpClient提供了免费的日志记录：

info: System.Net.Http.ShowsClient.LogicalHandler[100]
      Start processing HTTP request GET https://api.simplecast.com/v1/podcasts/shownum/episodes.json?api_key=
System.Net.Http.ShowsClient.LogicalHandler:Information: Start processing HTTP request GET https://api.simplecast.com/v1/podcasts/shownum/episodes.json?api_key=
info: System.Net.Http.ShowsClient.ClientHandler[100]
      Sending HTTP request GET https://api.simplecast.com/v1/podcasts/shownum/episodes.json?api_key=
System.Net.Http.ShowsClient.ClientHandler:Information: Sending HTTP request GET https://api.simplecast.com/v1/podcasts/shownum/episodes.json?api_key=
info: System.Net.Http.ShowsClient.ClientHandler[101]
      Received HTTP response after 882.8487ms - OK
System.Net.Http.ShowsClient.ClientHandler:Information: Received HTTP response after 882.8487ms - OK
info: System.Net.Http.ShowsClient.LogicalHandler[101]
      End processing HTTP request after 895.3685ms - OK
System.Net.Http.ShowsClient.LogicalHandler:Information: End processing HTTP request after 895.3685ms - OK

It was super easy to move my existing code over to this model, and I'll keep simplifying AND adding other features as I learn more.

将现有代码移至该模型非常容易，随着我了解更多，我将继续简化并添加其他功能。

Sponsor: Check out JetBrains Rider: a cross-platform .NET IDE. Edit, refactor, test and debug ASP.NET, .NET Framework, .NET Core, Xamarin or Unity applications. Learn more and download a 30-day trial!

赞助商：查看JetBrains Rider：一个跨平台的.NET IDE 。 编辑，重构，测试和调试ASP.NET，.NET Framework，.NET Core，Xamarin或Unity应用程序。 了解更多信息并下载30天试用版！

翻译自: https://www.hanselman.com/blog/httpclientfactory-for-typed-httpclient-instances-in-aspnet-core-21

aws实例类型 c5.4