Update the prefetch SW example to use cache-busting parameters #209
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
R: @gauntface @wibblymat @PaulKinlan et al.
The current example showing off a service worker that prefetches URLs and then uses those responses in a cache-first strategy runs the risk of locking users in to a stale response indefinitely. To mitigate this risk, this change appends a cache-busting URL parameter to the
fetch()
request made in theinstall
handler. That way, we can be assured that the response to that initial request is fresh at the time theinstall
handler is run.(It's possible that the resource might change after the
install
handler is run, and coordinating those resource changes with the service worker cache versioning is a separate problem that's already alluded to in the comments.)