Re: Report: Inconsistency in HTTP 204 response body parsing (#5227)

Long ago, I conducted a related survey on this topic: https://blogs.msdn.microsoft.com/ieinternals/2011/03/09/content-length-in-the-real-world/.

The Microsoft Edge team noted a real-world site with a compatibility issue related to ignoring junk: The page http://www.ntvmsnbc.com/id/25015435 sent back, "GET HTTP/1.1 301 Moved Permanentlyā€¯, as the status line.  This is obviously completely invalid, but since Chrome is allowing the 4 bytes of junk it succeeds.
 

View on GitHub: https://github.com/w3c/web-platform-tests/pull/5227#issuecomment-292201147

Received on Thursday, 6 April 2017 14:58:05 UTC