Re: [whatwg/fetch] Allow range header to be set by APIs (#560) from Jake Archibald on 2017-06-30 (public-webapps-github@w3.org from June 2017)

From: Jake Archibald <notifications@github.com>
Date: Fri, 30 Jun 2017 06:55:49 +0000 (UTC)
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/pull/560/c312190670@github.com>

> The idea is that media APIs will set this flag?

And downloads, yeah.

I'm not quite sure how to spec that bit yet, I guess there'll be a section like "this API may issue range requests. To fetch a range, run the following steps…"

Those steps will detail how to handle ranges that don't match what was requested, and ensuring all parts come from the same source if any opaque response is involved. Also how to handle an HTTP 200 response.

For downloads I want to ensure that browsers restart the download if the length, etag or last-modified has changed. Firefox is the only browser doing a decent job here, the others happy merge the chunks together even though the content has changed.

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

Received on Friday, 30 June 2017 06:56:22 UTC