--- title: HttpClient in .NET 10 - IHttpClientFactory and Resilience description: Creating a new HttpClient per request leaves sockets in TIME_WAIT and can exhaust ports under load. A test sending 500 GET requests showed 500 dead sockets... canonical: https://daily.dev/posts/httpclient-in-net-10---ihttpclientfactory-and-resilience-6wdsb64li twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: HttpClient in .NET 10 - IHttpClientFactory and Resilience | daily.dev og:description: Creating a new HttpClient per request leaves sockets in TIME_WAIT and can exhaust ports under load. A test sending 500 GET requests showed 500 dead sockets... og:url: https://daily.dev/posts/httpclient-in-net-10---ihttpclientfactory-and-resilience-6wdsb64li og:image: https://api.daily.dev/og/posts/6wDSB64lI.png og:image:alt: HttpClient in .NET 10 - IHttpClientFactory and Resilience 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. # HttpClient in .NET 10 - IHttpClientFactory and Resilience **[Code with Mukesh](https://daily.dev/sources/codewithmukesh)** · [@iammukeshm](https://daily.dev/iammukeshm) · 16 min read · 0 upvotes · 0 comments ## Summary Creating a new HttpClient per request leaves sockets in TIME_WAIT and can exhaust ports under load. A test sending 500 GET requests showed 500 dead sockets with 'new HttpClient()' versus a single reused connection with IHttpClientFactory, which also ran faster (105ms vs 374ms). The post covers basic, named, typed and keyed clients (keyed added in .NET 9), DelegatingHandler ordering, and AddStandardResilienceHandler from Microsoft.Extensions.Http.Resilience, which adds a rate limiter, timeout, retry, circuit breaker and attempt timeout. A POST retry test showed the default resilience settings saved the same order three times, producing a 201 after 4.7 seconds; DisableForUnsafeHttpMethods() fixed this by saving the order once. Polly's Open Source Maintenance Fee starts charging $20/month per qualifying organization from November 16, 2026, and the source does not say whether it applies to Polly pulled in through another package. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Does AddStandardResilienceHandler retry POST requests by default in .NET 10? Yes, by default it retries all HTTP methods including POST, PUT, PATCH and DELETE. In a test where a downstream API saved an order and returned 503 twice, the default settings caused the order to be saved three times before returning a 201 Created after about 4.7 seconds. Calling DisableForUnsafeHttpMethods() turns off retries for POST, PUT, PATCH, DELETE and CONNECT, fixing the duplicate writes. _Anyone wiring up retries for write endpoints can check this kind of default behavior on daily.dev before shipping._ ### What are the default settings for AddStandardResilienceHandler in .NET 10? It chains five strategies: a rate limiter with 1,000 permits and a queue of 0, a 30-second total timeout, a retry with 3 attempts using exponential backoff with jitter from a 2-second base delay, a circuit breaker that opens at a 10% failure ratio with at least 100 requests in 30 seconds for 5 seconds, and a 10-second per-attempt timeout. It treats HTTP 5xx, 408 and 429 as transient. _Teams tuning HTTP resilience defaults can compare these numbers against their own SLAs using daily.dev._ ### Should I use a typed HttpClient or a keyed HttpClient in .NET 9 or later? Microsoft's keyed DI documentation now recommends keyed clients, registered with AddAsKeyed(), over typed clients, because typed clients are easy to misconfigure and easy to capture accidentally in a singleton. A keyed client is a named HttpClient registered as a scoped keyed service, so scope validation throws an error at startup if a singleton tries to use it, catching the mistake early. _Developers deciding between DI patterns for HTTP clients can track guidance shifts like this one on daily.dev._ ## Similar posts on daily.dev - [HttpClient Resilience in .NET 10: Timeout, Retry, and Circuit Breaker with Microsoft.Extensions.Http.Resilience](https://daily.dev/posts/httpclient-resilience-in-net-10-timeout-retry-and-circuit-breaker-with-microsoft-extensions-http-aszonhwdy) · We Are .NET · 5 upvotes · 0 comments - [Building Resilient APIs with the Retry Pattern](https://daily.dev/posts/building-resilient-apis-with-the-retry-pattern-nml75zabn) · Telerik · 0 upvotes · 0 comments --- Tags: [#.net](https://daily.dev/tags/.net) [View this post on daily.dev](https://daily.dev/posts/httpclient-in-net-10---ihttpclientfactory-and-resilience-6wdsb64li) ```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":"HttpClient in .NET 10 - IHttpClientFactory and Resilience","url":"https://daily.dev/posts/httpclient-in-net-10---ihttpclientfactory-and-resilience-6wdsb64li","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/httpclient-in-net-10---ihttpclientfactory-and-resilience-6wdsb64li"},"datePublished":"2026-10-31T09:36:34.011Z","dateModified":"2026-11-01T06:00:12.295Z","description":"Creating a new HttpClient per request leaves sockets in TIME_WAIT and can exhaust ports under load. A test sending 500 GET requests showed 500 dead sockets...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a9e917cb52c0c58ab458d6c260d444f9?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a9e917cb52c0c58ab458d6c260d444f9?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Code with Mukesh","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":"Person","name":"Mukesh Murugan","url":"https://daily.dev/iammukeshm","image":"https://lh3.googleusercontent.com/a-/AFdZucr2UBIpOeVTWohK8XKuXPOutNG6hgyQMz7CYj7LEA=s100","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":910}},"commentCount":0,"discussionUrl":"https://daily.dev/posts/httpclient-in-net-10---ihttpclientfactory-and-resilience-6wdsb64li","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":".net","timeRequired":"PT16M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Code with Mukesh","item":"https://daily.dev/sources/codewithmukesh"},{"@type":"ListItem","position":3,"name":"HttpClient in .NET 10 - IHttpClientFactory and Resilience"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/httpclient-in-net-10---ihttpclientfactory-and-resilience-6wdsb64li#faq","mainEntity":[{"@type":"Question","name":"Does AddStandardResilienceHandler retry POST requests by default in .NET 10?","acceptedAnswer":{"@type":"Answer","text":"Yes, by default it retries all HTTP methods including POST, PUT, PATCH and DELETE. In a test where a downstream API saved an order and returned 503 twice, the default settings caused the order to be saved three times before returning a 201 Created after about 4.7 seconds. Calling DisableForUnsafeHttpMethods() turns off retries for POST, PUT, PATCH, DELETE and CONNECT, fixing the duplicate writes. Anyone wiring up retries for write endpoints can check this kind of default behavior on daily.dev before shipping."}},{"@type":"Question","name":"What are the default settings for AddStandardResilienceHandler in .NET 10?","acceptedAnswer":{"@type":"Answer","text":"It chains five strategies: a rate limiter with 1,000 permits and a queue of 0, a 30-second total timeout, a retry with 3 attempts using exponential backoff with jitter from a 2-second base delay, a circuit breaker that opens at a 10% failure ratio with at least 100 requests in 30 seconds for 5 seconds, and a 10-second per-attempt timeout. It treats HTTP 5xx, 408 and 429 as transient. Teams tuning HTTP resilience defaults can compare these numbers against their own SLAs using daily.dev."}},{"@type":"Question","name":"Should I use a typed HttpClient or a keyed HttpClient in .NET 9 or later?","acceptedAnswer":{"@type":"Answer","text":"Microsoft's keyed DI documentation now recommends keyed clients, registered with AddAsKeyed(), over typed clients, because typed clients are easy to misconfigure and easy to capture accidentally in a singleton. A keyed client is a named HttpClient registered as a scoped keyed service, so scope validation throws an error at startup if a singleton tries to use it, catching the mistake early. Developers deciding between DI patterns for HTTP clients can track guidance shifts like this one on daily.dev."}}]} ```