Preview of resource in cache is incorrect
Reported by
get...@gmail.com,
Aug 28
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: My service worker creates two caches, for versions of resources while logged in and one for the logged out versions. The caching works fine, and everything in the app works fine. These resources have the same URLs, just one was requested with a session credentials header and one not. When I inspect the caches under "Application" tab in devtools, I see both caches, and under each, I see all the resources listed with correct URLs. The "Headers" tab shows the proper expected response headers for each. But the "Preview" tab doesn't work correctly, specifically for my HTML files. It's as if, maybe for optimization, the rendered preview is stored against the URL rather than per individual cache item, so the preview ends up being "shared" between the two items, each respectively in a different cache. When I preview the resource under one cache, and then look at the preview of the same URL in the other cache, the previews are identical. At first, I assumed the resources themselves were wrong. But I've verified that they're the correct versions, since the response headers are correct (different for logged in vs logged out), and since the actual resources when served from the SW are as expected in each case. What is the expected behavior? I expect the "preview" tab to actually preview that resource specifically, not just a resource of that same URL but from a different cache. What went wrong? It seems it's sharing the previews between items of the same URL but in different caches. I can't be sure, but it seems like it uses the resource from whichever cache is "first" in the list of caches as the one to preview. Did this work before? No Chrome version: 68.0.3440.106 Channel: stable OS Version: OS X 10.11.6 Flash Version:
,
Aug 31
getify@ thanks for the issue. Request you to provide a sample file/URL where this issue can be reproduced which will help in further triaging. Thanks..
,
Sep 3
,
Nov 9
|
||||
►
Sign in to add a comment |
||||
Comment 1 by vamshi.kommuri@chromium.org
, Aug 29