如果未设置过期和/或无缓存标头，Google Chrome会缓存资源多长时间？

Question

We have been having a problem with Chrome caching a resource on our Glassfish server. The expires and no-cache headers are not being sent and the resource (an approximately 4 MB SWF file) is being cached by Chrome -- despite the presence of the Last-Modified header.

Sometimes Chrome will get a 304 code, and other times it simply does a 200 (from cache). I understand the 304 -- Chrome is likely checking the most recent Last-Modified date with the cached version to decide. But other times it does the 200 (from cache), which does not return any header information and appears that Chrome is simply assuming the file hasn't been modified instead of checking.

Google's own site states the following:

HTTP/S supports local caching of static resources by the browser. Some of the newest browsers (eg IE 7, Chrome) use a heuristic to decide how long to cache all resources that don't have explicit caching headers.

But this does not provide a definitive answer. Is this heuristic published anywhere? I realize there may not be a fixed answer (like 30 days), but some general guidelines would be useful. Furthermore, if Last-Modified is being set, I don't understand why Chrome isn't bothering to check that first.

Answer 1

DEFAULT_CACHE_TIME = 300

I found the above by searching at http://code.google.com/p/chromium/source/search?q=DEFAULT_CACHE_TIME&origq=DEFAULT_CACHE_TIME&btnG=Search+Trunk for "DEFAULT_CACHE_TIME".

There's a file called "chromeextensionsdocs.py" that contains the DEFAULT_CACHE_TIME.

I believe this is seconds based on the example given at http://code.google.com/appengine/docs/python/memcache/overview.html
In "chromeextensionsdocs.py", the DEFAULT_CACHE_TIME is sent as the last param in memcache.add

I'm not totally sure if this is the right value or not but seems likely that it is when putting the pieces together.

Answer 2

The time the browser considers a cached response fresh is usually relative to when it was last modified:

Since origin servers do not always provide explicit expiration times, a cache MAY assign a heuristic expiration time when an explicit time is not specified, employing algorithms that use other header field values (such as the Last-Modified time)... If the response has a Last-Modified header field (Section 2.2 of [RFC7232]), caches are encouraged to use a heuristic expiration value that is no more than some fraction of the interval since that time. A typical setting of this fraction might be 10%. [ https://tools.ietf.org/html/rfc7234#section-4.2.2]

The details of how Chrome (and other browsers) calculate that value, can be found in the source code ( An example from Chrome v49 ). It would appear that Chrome also calculates the value relative to the Last-Modified header.

( Credit to this post )