6/21/2023 0 Comments View mozilla private cache![]() The Content-Encoding, Content-Range, Content-Type headers must not be modified by a proxy. no-transform No transformations or conversions should be made to the resource. Other no-store The cache should not store anything about the client request or server response. For more information, see also this blog post. In Firefox, immutable is only honored on transactions. Clients that aren't aware of this extension must ignore them as per the HTTP specification. If-None-Match or If-Modified-Since) to check for updates, even when the user explicitly refreshes the page. The resource, if unexpired, is unchanged on the server and therefore the client should not send a conditional revalidation for it (e.g. immutable Indicates that the response body will not change over time. proxy-revalidate Same as must-revalidate, but it only applies to shared caches (e.g., proxies) and is ignored by a private cache. Revalidation and reloading must-revalidate The cache must verify the status of the stale resources before using it and expired ones should not be used. min-fresh= Indicates that the client wants a response that will still be fresh for at least the specified number of seconds. Optionally, you can assign a value in seconds, indicating the time the response must not be expired by. max-stale Indicates that the client is willing to accept a response that has exceeded its expiration time. s-maxage= Overrides max-age or the Expires header, but it only applies to shared caches (e.g., proxies) and is ignored by a private cache. Contrary to Expires, this directive is relative to the time of the request. Expiration max-age= Specifies the maximum amount of time a resource will be considered fresh. The client only wishes to obtain a cached response, and should not contact the origin-server to see if a newer copy exists. only-if-cached Indicates to not retrieve new data. ![]() no-cache Forces caches to submit the request to the origin server for validation before releasing a cached copy. private Indicates that the response is intended for a single user and must not be stored by a shared cache. ![]() Cache-Control: immutableÄirectives Cacheability public Indicates that the response may be cached by any cache. Be sure to check the compatibility table for their support. 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. The directives are case-insensitive and have an optional argument, that can use both token and quoted-string syntax. Caching directives are unidirectional, meaning that a given directive in a request is not implying that the same directive is to be given in the response. The Cache-Control general-header field is used to specify directives for caching mechanisms in both, requests and responses. ![]()
0 Comments
Leave a Reply. |