GoogleChrome / GoogleChrome/workbox
Avoid precaching newer contents for old revisions
- Dominant language
- JavaScript
- Stars
- 13k
- Forks
- 880
- Avg merge
- 2h 44m
- Merged PRs (30d)
- 8
Description
**Library Affected**:
workbox-sw
**Browser & Platform**:
Google Chrome 120.0.6099.129
**Issue or Feature Request Description**:
During deployment, clients can install a service worker and send requests to servers to precache assets.
At this point, the server responds with newer content, and the service worker should not store the content in CacheStorage as it is requesting content for an old revision.
Reproducible repository: https://github.com/iendeavor/workbox-issue-precaching
1. client visits website and starts to register service worker
2. service worker performs precaching for `{url: 'public/a.js', 'revision': 'version-1.js'}`
3. (deploy new content: content of `public/a.js` is changed now, new metadata is `{url: 'public/a.js', 'revision': 'version-2.js'}`)
5. server responds newer content
6. service worker save newer content for older revision
Contributor guide
Assessment
This issue has not been assessed yet.