Clear file cache through a separate fetch::no-cache call

[infinite-persistence]

Issue

ChunkLoadError.

There is anecdote¹ saying that Chromium will cache failed responses (e.g. timeout), so users could end up perpetually in a bad state until the cache is manually cleared, or the site moved on to a different chunk.

Approach

While there is no way to programmatically clear a user's cache, doing a separate fetch with no-cache indirectly replaces the cache with a fresh download.

Here an experiment to prove the concept:

1. In the first 2 reloads, we see the browser consistently/correctly using the one cached at 6.47pm.
2. Assume the cache was bad, so we send a separate fetch :: no-cache to clear it.
3. Reload. We see that the browser still used the cached version (correct behavior since filename didn't change or cache didn't expire), but it's a new one from 6:50pm.

2023-09-30.02-50-11--cache.mp4

Footnotes

1. https://github.com/whatwg/html/issues/6768 -- confirmed to be true; can be replicated ↩

[infinite-persistence]

--- close ---
Did not work under CF environment.
Next to try is the t=?<random> method mentioned in https://medium.com/@alonmiz1234/retry-dynamic-imports-with-react-lazy-c7755a7d557a