Re: [w3c/ServiceWorker] Block 206s entering the cache (via put & addAll) (#937) from Jake Archibald on 2017-11-16 (public-webapps-github@w3.org from November 2017)

From: Jake Archibald <notifications@github.com>
Date: Thu, 16 Nov 2017 10:20:59 +0000 (UTC)
To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/ServiceWorker/issues/937/344879154@github.com>

I think 416 is fine for the same reasons 404 is fine. The danger of 206 is it's an 'ok' response that likely only represents part of what the developer expects.

Also, by not-allowing 206 we can potentially add range coalescing behaviour in future.

-- 
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/937#issuecomment-344879154

Received on Thursday, 16 November 2017 10:21:28 UTC