From f401d3260a2c0b92c4989f975e0abc88569d10ae Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Tue, 14 Mar 2023 14:58:09 -0700 Subject: [PATCH] Remove outdated note about output caching (#28679) --- aspnetcore/performance/caching/response.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/performance/caching/response.md b/aspnetcore/performance/caching/response.md index 40f1d1e3a6..8f560037a0 100644 --- a/aspnetcore/performance/caching/response.md +++ b/aspnetcore/performance/caching/response.md @@ -53,7 +53,7 @@ Other cache headers that play a role in caching are shown in the following table Always honoring client `Cache-Control` request headers makes sense if you consider the goal of HTTP caching. Under the official specification, caching is meant to reduce the latency and network overhead of satisfying requests across a network of clients, proxies, and servers. It isn't necessarily a way to control the load on an origin server. -There's no developer control over this caching behavior when using the [Response Caching Middleware](xref:performance/caching/middleware) because the middleware adheres to the official caching specification. Support for *output caching* to better control server load is a design proposal for a future release of ASP.NET Core. For more information, see [Add support for Output Caching (dotnet/aspnetcore #27387)](https://github.com/dotnet/aspnetcore/issues/27387). +There's no developer control over this caching behavior when using the [Response Caching Middleware](xref:performance/caching/middleware) because the middleware adheres to the official caching specification. Support for *output caching* to better control server load was added in .NET 7. For more information, see [Output caching](xref:performance/caching/overview#output-caching). ## ResponseCache attribute