--- title: Create HTTP Requests with HttpClient in .NET | daily.dev description: Explains how to properly manage HttpClient instances in .NET to avoid common pitfalls like socket/port exhaustion. Covers the basics of HttpClient and... canonical: https://daily.dev/posts/create-http-requests-with-httpclient-in-net-utu7gfsrv twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Create HTTP Requests with HttpClient in .NET | daily.dev og:description: Explains how to properly manage HttpClient instances in .NET to avoid common pitfalls like socket/port exhaustion. Covers the basics of HttpClient and... og:url: https://daily.dev/posts/create-http-requests-with-httpclient-in-net-utu7gfsrv og:image: https://api.daily.dev/og/posts/Utu7GFSrV.png og:image:alt: Create HTTP Requests with HttpClient in .NET og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Create HTTP Requests with HttpClient in .NET **[NikolaTech](https://daily.dev/sources/nikolatech)** · 4 min read · 0 upvotes · 0 comments ## Summary Explains how to properly manage HttpClient instances in .NET to avoid common pitfalls like socket/port exhaustion. Covers the basics of HttpClient and HttpContent, then introduces IHttpClientFactory as the recommended solution for managing client lifecycles. Compares two patterns built on IHttpClientFactory: Named Clients (centralized configuration retrieved by name) and Typed Clients (encapsulating API logic in strongly-typed classes), with code examples for registration and usage via AddHttpClient, and a preference stated for typed clients due to easier mocking and centralized logic. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does creating a new HttpClient instance for every request cause port exhaustion in .NET? Each new HttpClient instance creates its own set of TCP connections, and if instances are created repeatedly rather than reused, the available sockets can become exhausted. HttpClient in .NET is designed to be reused across multiple requests rather than instantiated per call, which is why misuse leads to this issue. _Developers debugging socket exhaustion in .NET services can review HttpClient lifecycle patterns on daily.dev._ ### What is the difference between named clients and typed clients when using IHttpClientFactory in .NET? Named clients are registered with AddHttpClient and a string name, then retrieved via factory.CreateClient("name"), but request logic stays scattered across the codebase. Typed clients register a strongly-typed class with AddHttpClient, injecting HttpClient into its constructor so API interaction logic is centralized in one class, which also makes mocking easier for tests. _Teams deciding between named and typed HTTP clients in .NET can compare approaches on daily.dev._ ## Similar posts on daily.dev - [ASP.NET, Factory Patterns, and the Illusion of Control](https://daily.dev/posts/asp-net-factory-patterns-and-the-illusion-of-control-up6aoiahc) · We Are .NET · 3 upvotes · 0 comments - [Implementing RFC-compliant HTTP caching for HttpClient in .NET](https://daily.dev/posts/implementing-rfc-compliant-http-caching-for-httpclient-in-net-ckf4syuwc) · Meziantou · 5 upvotes · 1 comments --- Tags: [#.net](https://daily.dev/tags/.net), [#c#](https://daily.dev/tags/c#), [#dependency-injection](https://daily.dev/tags/dependency-injection) [View this post on daily.dev](https://daily.dev/posts/create-http-requests-with-httpclient-in-net-utu7gfsrv) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Create HTTP Requests with HttpClient in .NET","url":"https://daily.dev/posts/create-http-requests-with-httpclient-in-net-utu7gfsrv","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/create-http-requests-with-httpclient-in-net-utu7gfsrv"},"datePublished":"2026-10-04T13:06:55.115Z","dateModified":"2026-10-04T13:13:22.386Z","description":"Explains how to properly manage HttpClient instances in .NET to avoid common pitfalls like socket/port exhaustion. Covers the basics of HttpClient and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ceae51e5576b27685d019f999630a219?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ceae51e5576b27685d019f999630a219?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"NikolaTech","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"NikolaTech","logo":"https://media.daily.dev/image/upload/s--1h2fO6FL--/f_auto,q_auto/v1791119050/logos/nikolatech?_a=BAMAMicg0","url":"https://daily.dev/sources/nikolatech"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/create-http-requests-with-httpclient-in-net-utu7gfsrv","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":".net,c#,dependency-injection","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"NikolaTech","item":"https://daily.dev/sources/nikolatech"},{"@type":"ListItem","position":3,"name":"Create HTTP Requests with HttpClient in .NET"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/create-http-requests-with-httpclient-in-net-utu7gfsrv#faq","mainEntity":[{"@type":"Question","name":"Why does creating a new HttpClient instance for every request cause port exhaustion in .NET?","acceptedAnswer":{"@type":"Answer","text":"Each new HttpClient instance creates its own set of TCP connections, and if instances are created repeatedly rather than reused, the available sockets can become exhausted. HttpClient in .NET is designed to be reused across multiple requests rather than instantiated per call, which is why misuse leads to this issue. Developers debugging socket exhaustion in .NET services can review HttpClient lifecycle patterns on daily.dev."}},{"@type":"Question","name":"What is the difference between named clients and typed clients when using IHttpClientFactory in .NET?","acceptedAnswer":{"@type":"Answer","text":"Named clients are registered with AddHttpClient and a string name, then retrieved via factory.CreateClient(\"name\"), but request logic stays scattered across the codebase. Typed clients register a strongly-typed class with AddHttpClient, injecting HttpClient into its constructor so API interaction logic is centralized in one class, which also makes mocking easier for tests. Teams deciding between named and typed HTTP clients in .NET can compare approaches on daily.dev."}}]} ```