Issue metadata
Sign in to add a comment
|
Empty Cache and Hard Reload and Disable cache not working
Reported by
teo.eter...@gmail.com,
Mar 22 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Example URL: Steps to reproduce the problem: 1. We updated our website on the server 2. We open the website with dev tools open 3. We click on empty cache and hard reload What is the expected behavior? we should see the new website What went wrong? we still see the old website, opening the website in incognito mode shows the new website Did this work before? Yes before .181 Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.13.3 Flash Version: Tested it on MacOS 3 different environments., for webdevs its quite a big issue
,
Mar 23 2018
https://youtu.be/Z4FsFjYy6eE Clear files and images in clear cache doesn't work either, only incognito mod helps
,
Mar 23 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 23 2018
@mmenke PS. as you can see in the title of the webpage is written Thomas :) and when i open the same site in incognito its written Ability
,
Mar 23 2018
PS. the files are saved thought Nginx. Request Method: GET Status Code: 200 Remote Address: xxx.xxx.xxx.xxx:443 Referrer Policy: no-referrer-when-downgrade RESPONSE HEADERS content-encoding: gzip content-type: application/javascript date: Fri, 23 Mar 2018 09:58:53 GMT etag: W/"5ab4c250-2b1ab" last-modified: Fri, 23 Mar 2018 09:01:04 GMT server: nginx/1.10.3 (Ubuntu) status: 200 strict-transport-security: max-age=63072000; includeSubdomains; REQUEST HEADERS :authority: xxxxxxxx.xxx :method: GET :path: /xxxxxxxx.module.25a4d184071f35d22774.chunk.js :scheme: https accept: */* accept-encoding: gzip, deflate, br accept-language: en-GB,en;q=0.9,hr-BA;q=0.8,hr;q=0.7,en-US;q=0.6,bs;q=0.5,de;q=0.4 cache-control: no-cache cookie: authToken=xxxxxxxxx pragma: no-cache referer: https://xxxxx.xxxxx/ user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
,
Mar 23 2018
Do you still run into the issue if you navigate a tab to the site, close all tabs with the site open, clear the cache by going to chrome://net-internals -> click on the little triangle in the upper right -> clear cache, and then open the website in a new tab? I'm trying to figure out if this is an issue with the on-disk cache not clearing correctly, or if it's an issue with either devtool's reload behavior, or the renderer process's in-memory cache. Different people are familiar with each area, unfortunately. Those instructions will check if the on-disk cache is the issue.
,
Apr 17 2018
ping reporter: can you please respond to comment #6? Thanks!
,
Apr 24 2018
#6 Yes same issue. Chrome still shows (from disk cache) for the index.html. I even tried now to add a cache header explicit for index.html "no-store" but chrome doesn't care and always serves it from disk cache. The only thing that helps is Settings -> Advanced -> Remove browsing data.
,
May 7 2018
I found the issue. Angular cli / webpack was searching the folder for appcache manifest files, and found a sample file and added it to index.html of the web application from the pdftronwebviewer which instructed it to (APP)cache index.html. So the issue is DevTools[disable cache] / Empty cache and hard reload is not clearing the App cache anymore since this version. Clearing it manually in the devtools application tabs seams to fix the problem
,
May 7 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 7 2018
Adding appcache label, per comment #9.
,
May 14 2018
,
Dec 4
Empty cache and hard reload is working as expected. App cache is deprecated tech, sw / cache storage substituted it. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mmenke@chromium.org
, Mar 22 2018