chrome won't update index.html if there are manifest in client and some http headers in server
Reported by
kuangq...@gmail.com,
May 9 2016
|
||||||
Issue description
Chrome Version : 52.0.2728.0 canary (win x86)
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:OK,5.1.7
What steps will reproduce the problem?
(1) use nginx to be a server
(2) it response both etag and last-modified as http header ( it won't reproduce if either is removed)
(3) ver1 (index.html):
<!doctype html>
<html lang="zh-CN" manifest="./dist/app.manifest">
<head>...</head>
<body>...
<script src="dist/init.ver1.js"></script>
</body>
</html>
(4)visit it by "http://localhost:8080/index.html"
(5)update the index.html to ver2(the source file is generated by webpack )
<!doctype html>
<html lang="zh-CN" manifest="./dist/app.manifest">
<head>...</head>
<body>...
<script src="dist/init.ver2.js"></script>
</body>
</html>
(6)refresh(press F5)
What is the expected result?
ver2 of index.html open rightly
What happens instead?
init.ver2.js download rightly .but the html still want to get init.ver1.js.so the html report and script load error
Please provide any additional information below. Attach a screenshot if
possible.
,
May 10 2016
,
May 31 2016
Got another appcache bug for ya Michael.
,
Jan 10 2018
Hi, I have a very similar issue as described above except the application is a pinned webpage on Android device. No additional HTTP header was sent by the server. Tested on: Chrome v 63 running on Android device. 1. Server: Tomcat 2. On Android device, index.html is pinned to home screen 3. index.html includes ver1.js 4. index.html is specified in appcache 5. index.html is updated, file name is the same, and now include ver2.js 6. appcache content is updated but the file name remains the same 7. Refresh is triggered by javascript location.reload(true) Expected: Chrome downloads ver2.js and loads updated index.html What happens instead Chrome downloads ver2.js but loads the old index.html which refers to ver1.js
,
Jan 10 2018
,
Jan 11
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 13
We intend to deprecate AppCache. Only critical bugs will be fixed. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kavvaru@chromium.org
, May 10 2016Labels: Te-NeedsFurtherTriage