Hacker News Reader

Good call, given that it's not enabled in modern browsers, and is unreliably supported in proxies and servers.

It's for the best that it becomes widely treated as a non-feature of HTTP/1.1.

Still somewhat baffling that it's apparently so buggy across servers and proxies that it was for the best to disable it across browsers. In comparison to http2 multiplexing it seems trivial to get right, yet posts like this one suggest that http2 works fine everywhere and in every regard, and http1.x doesn't.

It's because real life http2 makes encryption mandatory, so that middle boxes can't fiddle with the stream. Thanks to that everything arrives as it was intended on the server

Reply on news.ycombinator.com