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

Even non-keepalive connections can specify a length, and could theoretically have extra bytes on the wire, which I think corresponds to the case this is trying to consider an error?  Chunked encoding responses could also have extra bytes on the wire (which may not correspond to the issue this is targeted it), and there's the related question of not receiving the terminal when the connection is closed (Chrome treats this as an error, but other browsers do not, last I heard).

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