- From: Matt Menke <notifications@github.com>
- Date: Sat, 14 Aug 2021 13:33:29 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 14 August 2021 20:33:42 UTC
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
Received on Saturday, 14 August 2021 20:33:42 UTC