This directive is not effective in preventing caches from storing your response. If you mean to not store the response in any cache, use no-store instead. 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. no-cache The response may be stored by any cache, even if the response is normally non-cacheable. private The response may be stored only by a browser's cache, even if the response is normally non-cacheable. Public The response may be stored by any cache, even if the response is normally non-cacheable. has public, max-age or s-maxage in Cache-Control or.Cache-Control does not have no-store, or if proxy, does not have private and.Cache-Control: immutableДЄ response is normally cached by the browser if: Check the compatibility table for their support user-agents that don't recognize them should ignore them. Cache-Control: must-revalidateД®xtension Cache-Control directives are not part of the core HTTP caching standards document. Standard Cache-Control directives that can be used by the server in an HTTP response. Standard Cache-Control directives that can be used by the client in an HTTP request. 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.Header typeД¬aching directives have the following rules to be valid: A given directive in a request does not mean the same directive should be in the response. The Cache-Control HTTP header holds directives (instructions) for caching in both requests and responses.

Private cache directive