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

I should add, it's possible to check if there are any bytes currently pending on a socket, and read them if there are, and don't do anything if there aren't, but that's not an operation any browser's TCP logic has previously had to support.  Chrome does have that ability in its socket layer now (with SSL support that doesn't get confused by extra SSL control messages, I believe), but didn't for most of its existence.

As previously noted, of course, that effort is necessarily best-effort, and could get confused by other messages over the wire.

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