Re: [whatwg/fetch] Some servers seem to expect 'Accept-Encoding : identity' to serve Range requests (#747)

What browsers seem to send along with ranged requests:

* Chrome: `Accept-Encoding: identity;q=1, *;q=0`.
* Safari: `Accept-Encoding: identity`.
* Firefox: No `Accept-Encoding` header.
* Edge: `Accept-Encoding: gzip, deflate, br`.

In terms of "I don't want any encoding", Chrome's value seems redundant compared to Safari's. Firefox's lack of header seems risky. Edge's is the least unusual vs other requests. I haven't tested whether Edge & Firefox actually accept encoded data.

It seems really unusual that a server would require `identity`, since an uncompressed response is always allowed, unless explicitly disallowed by `Accept-Encoding`. If it is something that servers require, then we should see Edge (and maybe Firefox too), failing to get partial responses from these servers.

@youennf is this something you've seen a lot of servers require, or is it just the case in https://bugs.webkit.org/show_bug.cgi?id=184447?

-- 
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/issues/747#issuecomment-393107638