Firefox 54 will no longer do HTTP/1 pipelining! https://bugzilla.mozilla.org/show_bug.cgi?id=1340655 … *hooray* I can't wait to rip that mess out from curl...
-
-
Replying to @bagder
Uhg, this seems like awful performance regression for users on high-latency lines. Will they uncap concurrent conns to compensate?
1 reply 0 retweets 0 likes -
Replying to @RichFelker
it is just too error-prone for most users anyway, HTTP/2 is a way way better way to help high-latency users
1 reply 0 retweets 1 like -
Replying to @bagder
Most sites don't do HTTP/2 and probably won't for a long time. Only big/CDN-backed/CF-using/etc. ones do...
2 replies 0 retweets 1 like -
Replying to @RichFelker
~13% of the top-10 million do, double the amount from last year. No desktop browser do pipelining by default due to its probs
1 reply 1 retweet 2 likes -
Replying to @bagder
Is that actually more sites adding support on their own hosting, or just more of the web moving the CF?
1 reply 0 retweets 0 likes -
Replying to @RichFelker
both, enabling HTTP/2 is easy for anyone who wants to
2 replies 0 retweets 0 likes
Not if it requires "upgrading" to an httpd that's 10x slower than your current one.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.