Re: [whatwg/fetch] HTTP/1 parsing (#1156)

Another fun one:  Chrome allows 4 bytes of random slop between requests, before the start of headers.  I believe this was copied from FireFox of IE's behavior at the time.  I don't believe all browsers currently do this, so it may be easier to remove.  My main concern is servers sending 0-length compressed gzip bodies with "Content-Length: 0", which aren't actually of length 0.  In this case, there's slop on the end, which I suspect this logic deals with.

-- 
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/1156#issuecomment-772659635