- From: youennf <notifications@github.com>
- Date: Fri, 01 Jun 2018 09:07:03 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 1 June 2018 16:07:27 UTC
The PR looks good to me. I wonder what is the fetch spec policy regarding external links like https://jakearchibald.github.io/accept-encoding-range-test/. It does not seem to work in Safari for instance and my locally installed Chrome bails out because of TransformStream not being present. Maybe a snapshot of the results could be hosted somewhere (whatwg owned maybe) and would link to that particular URL for fresher results. > This PR adds Accept-Encoding: identity for all requests with a Range header, regardless of source, and adds the header after the service worker (where Accept-Encoding is usually added). That makes sense to me. This is simple to implement, will simplify range requests authoring, including when intercepted by service workers. There seems to be no justification for making Accept-Encoding a special privileged header at the moment. -- 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/751#issuecomment-393927923
Received on Friday, 1 June 2018 16:07:27 UTC