- From: Ben Kelly <notifications@github.com>
- Date: Thu, 28 Sep 2017 17:38:17 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 28 September 2017 17:38:38 UTC
It seems that in firefox we avoid using partial response and range requests if: 1. The server cannot support range requests 2. The underlying resource has changed since the previous part of the resource was received See: https://searchfox.org/mozilla-central/source/netwerk/base/nsIResumableChannel.idl#13 If we allow range requests through FetchEvent.request, how can we ever know if the underlying resource has changed? Normally we depend on the http cache to detect if a change has taken place, but we don't have that here. The service worker could return completely different data each time. Does chrome have similar "detect if something changed" behavior for range requests? -- 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/1201
Received on Thursday, 28 September 2017 17:38:38 UTC