Additional reasoning for sending Accept-Encoding: identity

[jakearchibald]

I hadn't really appreciated this with the initial PR, but preventing encoding solves a pretty big gotcha if developers tried to fetch ranges with fetch().

---

Preview | Diff

[annevk]

How does it avoid a failure? Because the server won't try to send back gzip content? Or because (most) user agents only support a lack of content encoding?

[jakearchibald]

I hadn't realised that if a resource is encoded, a range is taken from that encoded resource. So if the range is bytes=1-, and the content is encoded, fetch() will always reject when it tries to decode the content.

If the server returns unencoded data, this failure won't occur.

[annevk]

Thanks, I think I read the added note wrongly the first time since it's clear now.