Response Caching in ASP.NET Core [.NET 6 Implementation of Response Caching Middleware]

Caching response helps improve the performance and response time of Web APIs where it is possible. But it takes some effort to build out a caching infrastructure and manage it.
The Response caching middleware which comes out of the box simplifies the implementation significantly. And also it does not require building custom implementation for caching, plus provides clients the option to choose whether to use a cached value or not.
My KZbin channel: / dotnetcorecentral
My Blog Website: dotnetcorecent...
My Github repo: github.com/cho...
Some of my popular videos:
Elasticsearch with .NET and introduction: • An Introduction to Ela...
Hangfire Scheduling an introduction: • Scheduling recurring j...
ASP.NET Core Authentication with JWT (JSON Web Token): • ASP.NET Core Authentic...
Running Background tasks using IHostedService and BackgroundService (In ASP.NET Core 3.1): • Running Background tas...
How to build an API Gateway in ASP.NET Core using Ocelot (Build API Gateway in a few minutes): • How to build an API Ga...

[@Chibabachacho]

It’s great to see that your channel is growing 😊. Just to clarify on the authorization part, do you mean to say if you have an Authorization attribute on top of your controller, you cannot use caching?

[@valeriik9135]

First, thanks for your work! could you clarify this point - if there's the Authorization header then 'cache-control:' must explicitly forbid caching using 'no-cache, no-store, must-revalidate' or the header 'cache-control' shouldn't be present at all?

[@DotNetCoreCentral]

Thanks so much for watching! Ideally, With Auth header, it will make sense to use 'no-cache, no-store, must-revalidate', to explicitly inform the server

[@gringo-south-america]

Caching doesn't work when Authorization Header is present.

[@ayan-qn9or]

Very useful topic, well expained. But respose caching will work if the endpoint is protected by bearer token.

[@srinidhi1990]

It will not work. you should not have authorization attribute

[@md.redwanhossain6288]

Very misleading tutorial. Response Cache does not store any data in the server. It is all about how the client will cache the response so that it does not need to send the request again. You are referring to Output caching when you said about server side cache.