- From: Jungkee Song <notifications@github.com>
- Date: Tue, 13 Dec 2016 07:12:20 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Tuesday, 13 December 2016 15:12:56 UTC
Interesting. So, `cache-control:immutable` prevents a request with `"no-cache"` from sending a conditional revalidation in the first place. But it seems this can work only when a server provides this hint. In the GitHub hosting case, isn't setting this header impossible? That considered, providing opt-in to "no-cache" seems to satisfy both requirements. -- 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-266763783
Received on Tuesday, 13 December 2016 15:12:56 UTC