![private cache access private cache access](https://storageswiss.files.wordpress.com/2017/04/accesskey-hidden.png)
![private cache access private cache access](https://www.my-private-network.co.uk/images/aws/del1-shadow.png)
Clients can set max-age=0 to also clear existing cache responses, as this forces the cache to revalidate with the server (no other directives have an effect when used with no-store). Note that this does not prevent a valid pre-existing cached response being returned. The response may not be stored in any cache. no-store This directive is not effective in preventing caches from storing your response. However, the stored response MUST always go through validation with the origin server first before using it, therefore, you cannot use no-cache in-conjunction with immutable.
![private cache access private cache access](https://hunter.readthedocs.io/en/latest/_images/ingenue-public-repo.png)
The response may be stored by any cache, even if the response is normally non-cacheable. The response may be stored only by a browser's cache, even if the response is normally non-cacheable. if a response/request should be validated with the origin server before caching.if a response/request can be cached (where it may be cached) and.Check the compatibility table for their support user-agents that don't recognize them should ignore them. Standard Cache-Control directives that the server can use in an HTTP response: Cache-Control: must-revalidateĮxtension Cache-Control directives are not part of the core HTTP caching standards document. Standard Cache-Control directives that the client can use in an HTTP request: Cache-Control: max-age= Some directives have an optional argument, which can be either a token or a quoted-string.Multiple directives are comma-separated.Case-insensitive, but lowercase is recommended.Caching directives follow the validation rules below: