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

This is largely the point of using a service worker, no?  The user hits the refresh button triggering no-cache fetches.  The SW then responds with data from the Cache API without consulting the server.  Or synthesizes a response, etc.  The user's request to check with the server is often ignored by design.

If the user does a hard refresh (shift-ctrl-r) then SW is bypassed.  The user's intent cannot be changed at this point.

This is a SW intercept design choice, though.  The exposed request.cache value is a minor point when you can return completely different responses.

I see no reason to make browser cache overrides magical and hidden.

---
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-236757927