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

I tried o reproduce the issue, but I am getting a different error:
"Length of the file not known. It must either be supplied in the config or given by the HTTP server."
And there is an warning before:
"Warning: The server responded with br encoding to a HEAD request. Ignoring since it may not do so for Range HTTP requests, but this will lead to incorrect results otherwise since the ranges will be based on the compressed data instead of the uncompressed data."

Firefox receives a 206 with a content-encoding. The header is coming from the server. I cannot confirm that that was causing the original issue because I cannot reproduce the error. 

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