Re: [whatwg/fetch] Should the cache control default mode match how the page is loaded? (#289)

The issue is that, with the current default value, other than clearing the whole cache, user can never force updating resources fetched via `fetch()`.

Also without a full implementation of cache mode (no browser is currently shipping cache mode support as far as I know), authors do not have many choices as well. They might need to either configure the server to explicitly disable caching via sending some header in responses, or append some kind of revision string to the url.

The combination of these issues leads to a poor development experience to me.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/289#issuecomment-214179624