Re: [whatwg/fetch] Specify identity encoding for range requests. Fixes #747. (#751)

This is different to what browser appear to implement. Chrome and Safari appear to special-case media, and they add the `Accept-Encoding` header before the service worker (although Safari then filters it before the service worker).

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).

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

Received on Friday, 1 June 2018 10:00:52 UTC