Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893)

@jungkees I don't understand why a github user cares about 304s here.  Github as a service allows arbitrary content to be hosted, so I'm not sure how they can have any expectation of a certain QPS to scripts.

Also, I would contend someone running a small site on github.io are exactly the sort of developers more likely to be surprised when their service workers don't update as expected because they get default caching they don't want.

I feel pretty strongly that no-cache should be the default.  This is based on helping numerous developers work through this issue.  I feel like its the root cause of at least half the problems people bring me.  Making it default cache is not going to help here.

-- 
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/893#issuecomment-266767291