Learn how to implement HTTP caching in .NET using Meziantou.Framework.Http.Caching to reduce latency and network traffic with RFC 7234 and 8246 compliance.

Meziantou's resource offers insights, tutorials, and resources for software developers and IT professionals. Readers can learn about .NET development, web technologies, and software engineering best practices. With tutorials, code samples, and articles, Meziantou provides  guidance and expertise for building scalable and reliable software solutions.

Meziantou

HttpClient in .NET lacks built-in HTTP caching, requiring every request to hit the server. The Meziantou.Framework.Http.Caching NuGet package adds RFC 7234 and RFC 8246 compliant caching via a DelegatingHandler. The post covers installation, basic usage, ASP.NET Core dependency injection integration, client cache directives (no-cache, max-stale, only-if-cached), configurable options like response size limits and custom cache predicates, and thread safety including cache stampede prevention.

Implementing RFC-compliant HTTP caching for HttpClient in .NET

# Introducing Meziantou.Framework.Http.Caching

<p>The C# HttpClient might not have it, but ASP NET Core does. In ASP it’s called Response caching and is RFC 9111 compliant. RFC 9111 obsoletes RFC 7234</p>
<p>See: <a href="https://learn.microsoft.com/en-us/aspnet/core/performance/caching/response?view=aspnetcore-10.0" target="_blank" rel="noopener nofollow">https://learn.microsoft.com/en-us/aspnet/core/performance/caching/response?view=aspnetcore-10.0</a>
and <a href="https://www.rfc-editor.org/rfc/rfc9111" target="_blank" rel="noopener nofollow">https://www.rfc-editor.org/rfc/rfc9111</a></p>
