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

A server that generates a 206 based upon query parameters is clearly broken and intentionally so; I'd suggest trying to prevent brokenness in that case is a lost cause.

OTOH, a 206 response clearly has an application-visible semantic, as NOT being the whole response. 

AFAIK there isn't any existing markup that allows a `<script>` to specify a range. That says to me that it should specify that a partial response shouldn't be processed.

Relevant spec seems to be here:
  https://html.spec.whatwg.org/#prepare-a-script

... around step 21, which does not appear to talk about success or completeness of the result of fetching.

@annevk?

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