Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962)

So I guess the question is, is this behavior ok?  Should we just let upstream stuff cache per the cache-control header, etc?  Or is there some expectation from devs that if a service worker is present they will get a FetchEvent since the SW can change the resource irrespective of the headers?

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