Re: Test HTTP parsing (#5102)

most of these non HTTP/1 cases are being interpreted as HTTP 0.9... which is fair enough - they aren't HTTP/1 and there is no version negotiation outside of the TCP stream. There is no response code in 0.9 so calling it 200 or parsing it and calling it 280 all seem fair game. Not a useful test.

The exception is the HTTP/2 case (in what is obviously not RFC 7540 HTTP2..).. as mark notes, that's just a bugwards accommodation for shoutcast to treat that as http/1. Similarly allowing mixed-case HttP is something that a receiver is just going to do for legacy interop. We've cleaned it up going forward


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

Received on Thursday, 9 March 2017 22:01:19 UTC