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

Chrome's security team would prefer 206s to fail if a range wasn't requested. However, @ericlaw1979 says there are servers that do this, but the range covers the whole resource https://fiddler.ideas.aha.io/ideas/FID-I-191.

It'd be pretty easy to work around that case in the spec.

-- 
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-315072732

Received on Thursday, 13 July 2017 13:10:07 UTC