- From: MattMenke <web-platform-tests-notifications@w3.org>
- Date: Tue, 11 Apr 2017 15:03:50 GMT
- To: public-web-platform-tests-notifications@w3.org
Chrome's behavior here does not vary by platform, and Chrome does not internally generate bogus 502 response codes. Given that the chart claims both FireFox and Chrome are displaying a 502 when a server is not, according to the description, returning a 502 error, I suspect there's some sort of proxy present, or a different test server is being used on different platforms. Anyhow, I'd treat the chart as unreliable. Note that the new "net::ERR_INVALID_HTTP_RESPONSE" error is because we removed support for HTTP/0.9 on non-standard ports recently. If the server were using port 80, the final request would succeed on current versions of Chrome. View on GitHub: https://github.com/w3c/web-platform-tests/pull/5227#issuecomment-293292568
Received on Tuesday, 11 April 2017 15:04:03 UTC