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?
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?
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
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.
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?
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?
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
Caching doesn't work when Authorization Header is present.
Very useful topic, well expained. But respose caching will work if the endpoint is protected by bearer token.
It will not work. you should not have authorization attribute
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.