Re: [slightlyoff/ServiceWorker] should FetchEvent.request.cache reflect non-fetch browser cache controls? (#875)

Let's think about an example scenario. A navigation to a main resource (N) that includes a `fetch(url, { cache: "no-store" })` call to a subresource (R). Let's call the fetches N and R, respectively.

* Initial load of N triggers fetches to:
N - cache mode: "default"
R - cache mode: "no-store"
Intercepted by SW: yes - the cache mode values don't matter

* Refreshing the document triggers fetches to:
N - cache mode: "default" or "no-cache"? (currently "default"; no step overrides the value)
R - cache mode: "no-store" or "no-cache"? (currently "no-store"; no step overrides the value)
Intercepted by SW: yes - the cache mode values don't matter
When they're bypassed to the network stack: we may expect "no-cache" for both N and R

* Force refreshing the document triggers fetches to:
N - cache mode: "default" or "reload"? (currently "default"; no step overrides the value)
R - cache mode: "no-store" or "reload"? (currently "no-store"; no step overrides the value)
Intercepted by SW: no
When they get to the network stack: we may expect "reload" for both N and R

I guess @wanderview originally brought this question? - how to override the cache mode value (or not) and how to spec it?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/875#issuecomment-239379479