Skip to content

Clarify HttpClient connection-pool disposal #55318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adegeo merged 4 commits into from
Aug 5, 2026
Merged

Clarify HttpClient connection-pool disposal #55318

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2b45a9e
Initial plan
Copilot Aug 5, 2026
2f1b8c3
Clarify HttpClient handler disposal
Copilot Aug 5, 2026
55f89e2
Scope handler disposal guidance
Copilot Aug 5, 2026
bd31859
Update docs/fundamentals/networking/http/httpclient-guidelines.md
adegeo Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/fundamentals/networking/http/httpclient-guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ The 15-minute interval was chosen arbitrarily for illustration purposes. You sho

## Pooled connections

The connection pool for an <xref:System.Net.Http.HttpClient> is linked to the underlying <xref:System.Net.Http.SocketsHttpHandler>. When the <xref:System.Net.Http.HttpClient> instance is disposed, it disposes all existing connections inside the pool. If you later send a request to the same server, a new connection must be recreated. As a result, there's a performance penalty for unnecessary connection creation. Moreover, TCP ports aren't released immediately after connection closure. (For more information on that, see TCP `TIME-WAIT` in [RFC 9293](https://www.rfc-editor.org/rfc/rfc9293.html#section-3.3.2).) If the rate of requests is high, the operating system limit of available ports might be exhausted. To avoid port exhaustion problems, we [recommend](#recommended-use) reusing <xref:System.Net.Http.HttpClient> instances for as many HTTP requests as possible.
The connection pool for an <xref:System.Net.Http.HttpClient> is linked to the underlying <xref:System.Net.Http.SocketsHttpHandler>. Disposing an <xref:System.Net.Http.HttpClient> disposes the pool only when the client owns and disposes the underlying handler. If a client uses a handler that it doesn't own, disposing the client doesn't affect the handler or its connections. <xref:System.Net.Http.IHttpClientFactory> creates clients with handlers that it manages, so it can reuse handlers and their connection pools. Sending another request to the same server using a different handler requires a new connection. As a result, there's a performance penalty for unnecessary connection creation. Moreover, TCP ports aren't released immediately after connection closure. (For more information on that, see TCP `TIME-WAIT` in [RFC 9293](https://www.rfc-editor.org/rfc/rfc9293.html#section-3.3.2).) If the rate of requests is high, the operating system limit of available ports might be exhausted. To avoid port exhaustion problems, [reuse](#recommended-use) <xref:System.Net.Http.HttpClient> instances for as many HTTP requests as possible.

## Recommended use

Expand Down
Loading