Re: [whatwg/fetch] Cache-mode and upstream Cache-Control (#722)

FWIW, I think this will be tricky for firefox to implement currently.  This stuff gets set deep in the networking stack:

https://searchfox.org/mozilla-central/rev/5dbfd833bbb114afe758db4d4bdbc5b13bcc33ef/netwerk/protocol/http/nsHttpChannel.cpp#1187-1200

AFAICT there is no higher level flag to bypass just the local cache.  This can probably be changed (if mozilla networking folks agree), but I think this is partly how we ended up here.

However, consider:

1. The browser wants to bypass upstream caches for some loads.  Like ctrl-r.
2. A service worker can intercept these loads and may proxy them via `evt.respondWith(fetch(evt.request))`.
3. This change makes `evt.request.cache` no longer reflect the intention of (1).

How do we maintain our goal of "service worker proxies requests don't lose functionality"?

-- 
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/722#issuecomment-413559634