Html cache private cache5/7/2023 ![]() ![]() ![]() Since neither of those headers are present in this case, no revalidation needs to occur. When I investigated this heuristic of Last-modified / 10 for Why is this response being cached?, I found that all major browsers appear to use this same heuristic.Īccording to Cache-Control - HTTP | MDN, clients must only revalidate if one of the following headers is present: If this header is present, then the cache's freshness lifetime is equal to the value of the Date header minus the value of the Last-modified header divided by 10. If present, then we look for a Last-Modified header. The freshness lifetime is calculated based on several headers. Cache-Control: private, max-age0, no-cache These settings are referred to as response directives. HTTP/1.1 introduces a new class of headers, the Cache-Control response headers, which allow web publishers to define how pages should be handled by caches. Where responseTime is the time at which the response was received according to the browser. The expiration time is computed as follows: expirationTime = responseTime + freshnessLifetime - currentAge then the expiration calculation is essentially the algorithm described in RFC 2616 section 13.2. Error responses may be cached even in the. Mozilla has a HTTP Caching FAQ that says: The Extend Cache filter rewrites the URL references in the HTML page to include a hash of the resource content (if rewritecss is enabled then image URLs. This mode is not appropriate if the backend serves private, per-user content, such as dynamic HTML or API responses. ![]()
0 Comments
Leave a Reply. |