HttpMessageHandler

As explained in ASP.NET Core in Action, 3e

HttpMessageHandler is the .NET base abstraction for processing HTTP requests and responses in an HttpClient handler chain.

HttpMessageHandler is the building block behind HttpClient’s outbound request pipeline. HttpClient coordinates the call, while the final HttpClientHandler opens the connection and sends the request. section 33.2.1

Handlers run in sequence: each can modify an outgoing request, then inspect the response as it returns. This makes the pipeline useful for cross-cutting concerns such as logging, metrics, authentication, and transient-error handling. section 33.2.1 section 33.0

Use IHttpClientFactory to manage the handler pipeline instead of repeatedly creating and disposing its underlying handler.

• Register the factory with builder.Services.AddHttpClient(). section 33.2.1
• Create an HttpClient through factory.CreateClient(), then configure its base address and call the remote API. section 33.2.1
• Let the factory manage handler lifetimes to avoid socket exhaustion while allowing DNS changes to be respected. section 33.5

A factory-created client

Register IHttpClientFactory, inject it into an endpoint, call factory.CreateClient(), set BaseAddress to https://example.com/rates/, and request latest. The response can then be checked with EnsureSuccessStatusCode() and read as text. section 33.2.1

Figure 33.4 Each HttpClient contains a pipeline of HttpMessageHandlers. The final handler is an HttpClientHandler, which makes the connection to the remote server and sends the HTTP request. This configuration is similar to the ASP.NET Core middleware pipeline, and it allows you to make cross-cutting adjustments to outgoing requests.

The figure shows HttpClientMessageHandlers arranged as an outbound pipeline, ending with HttpClientHandler, and compares the arrangement with ASP.NET Core middleware. section 33.2.1

How ASP.NET Core in Action, 3e covers it

How deep it goes

Explains pipeline flow, final connection handling, lifetime problems, and custom-handler use without detailing handler implementation internals.

Examples

Uses a factory-created client calling an example rates endpoint and discusses handlers for logging, metrics, authentication, and API keys.

What it assumes

Assumes familiarity with HttpClient and HTTP requests while establishing handler pipelines and lifetime management through examples.

What you can do after

Apply it via IHttpClientFactory to create managed clients and add reusable behavior to outgoing HTTP requests.

How it connects

Connects HttpClient, HttpClientHandler, IHttpClientFactory, middleware pipelines, and Polly-based transient-error handling.

liveBookmanning.com

Read ASP.NET Core in Action, 3e on liveBook Get the book at manning.com

Related concepts

• HTTP clientused by · An HTTP client is software or an API component that sends HTTP requests and receives and processes HTTP responses.
• DelegatingHandlerincludes · DelegatingHandler is a .NET HttpMessageHandler base class that forwards requests and responses to an inner handler while permitting additional processing.
• test doubleused by · A test double is a substitute for a real component or dependency that provides controlled or simplified behavior, or enables interaction observation, during testing.
• integration testused by · An integration test evaluates whether multiple software components, or a component and an external dependency, interact and behave correctly together.
• HttpClientHandlerincludes · HttpClientHandler is the .NET HttpMessageHandler that establishes network connections and sends HTTP requests for HttpClient.
• SendAsynchas part · SendAsync is an asynchronous API operation that sends a request or data and represents its completion and result asynchronously.

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.