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

I think that's a different issue.  If Chrome sees a content-length for a resource with a chunked transfer encoding, I believe it ignores the content-length.

That comment was about the fact that if we see content-length that matches uncompressed content-length, we'll consider that a success, if decompression results in a file that exactly matches the content-length size.

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