- From: Anne van Kesteren <web-platform-tests-notifications@w3.org>
- Date: Fri, 10 Mar 2017 07:01:59 GMT
- To: public-web-platform-tests-notifications@w3.org
Right, it seems suspicious that all user agents support HTTP/2.0 and case-insensitive mostly worked. There's also a difference between returning a network error and continuing to treat as HTTP/0.9 (the latter is what Firefox does and Edge maybe (although Edge uses the status code 520), the former is more like Safari and Chrome (although Chrome only does one scenario that way)). So if some of this is required it would be good if the HTTP specification actually said so. Otherwise it's hard to come up with pass/fail criteria here and get browsers to align on how they handle pass/fail. View on GitHub: https://github.com/w3c/web-platform-tests/pull/5102#issuecomment-285593890
Received on Friday, 10 March 2017 07:02:11 UTC