Re: [whatwg/fetch] Allow range header to be set by APIs (#560)

Nice to see this happening, this might be especially useful in WebKit context where audio/video relies a lot on range requests.
Based on https://bugs.webkit.org/show_bug.cgi?id=184447, it seems that some servers might require 'Accept-Encoding : identity' to serve range responses from range requests.
I don't know how much this is a bug that servers should fix and how much this can impact deployment of this feature.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/560#issuecomment-392889485

Received on Tuesday, 29 May 2018 18:36:58 UTC