Re: [whatwg/fetch] Interop issue with range requests when the server sends more bytes than it says (#1295)

Interesting. And in Chrome they don't send content-encoding:

![image](https://user-images.githubusercontent.com/617481/129596136-2cfefdcb-cf60-43c1-a727-3752013d7368.png)

(although they do send it on the initial 200)

Either Firefox's inspector is carrying over headers from the initial 200 to the 206 (seems unlikely), or this is a website bug where they're changing their behavior based on the browser in question.

-- 
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/1295#issuecomment-899642234