This is no longer the case since cache partitioning was released: https://developers.google.com/web/updates/2020/10/http-cache-partitioning#how_will_cache_parti

This is no longer the case since cache partitioning was released: https://developers.google.com/web/updates/2020/10/http-cache-partitioning#how_will_cache_partitioning_affect_chromes_http_cache https://developers.google.com/web/updates/2020/10/http-cache... Cache keys are now tuples of (host, resource) so if you download and cache bootstrap.js on example.com, and then go to bootstrapsite.com which hosts the same JS file, you'll have to download it again because the cache keys are different: example.com -> bootstrap.js -> cached as (example.com, bootstrap.js) bootstrapsite.com -> bootstrap.js -> cached as (bootstrapsite.com, bootstrap.js) (example.com, bootstrap.js) ≠ (bootstrapsite.com, bootstrap.js)