- From: MattMenke <web-platform-tests-notifications@w3.org>
- Date: Thu, 13 Apr 2017 22:06:18 GMT
- To: public-web-platform-tests-notifications@w3.org
I'm not sure why Chrome isn't treating it as an HTTP/0.9 response, if I'm understanding what's happening. Is the server closing the socket after the second response, or keeping it open? If the socket isn't closed, and it's not a fetch request, it may be held up at the mime sniffer, unless it has a mime type that doesn't trigger sniffing. View on GitHub: https://github.com/w3c/web-platform-tests/pull/5227#issuecomment-294034104
Received on Thursday, 13 April 2017 22:06:31 UTC