HTTP/2 and wordpress?

Ready for action would be a stretch at the moment. ??

It was approved as a proposed standard yesterday, but has yet to be published as such.

Currently, Firefox and IE only support HTTP/2 over TLS, and Chrome’s support for HTTP/2 is not enabled by default.

Then, the hosting providers need to launch support for it at the server level. At the moment, neither Apache nor Nginx support HTTP/2. It’s only supported by IIS in Windows 10 and OpenLiteSpeed 1.3.6 and 1.4.4.

I think we’ve still got a very long way to go before it’s ready for action and platforms start to think about how they’ll take advantage of it (or if they should just leave those details up to the server software).

ah, they way all the media outlets talk about it made me think it is ready ??

Thanks for letting me know ??

You’re welcome!

Well, it appears HTTP/2 is probably going to ramp up more quickly than you think, @macmanx : Firefox 36 implements it and is deployed *today*, Microsoft has started implementing it in IIS for Windows 10, Nginx will be ready to play quickly (they already have a SPDY implementation, and HTTP/2 largely relies on SPDY…

Outstanding, Apache still needs to be on board though for this to apply to 90% of the sites out there though, and it would be nice to have Chrome ship with support for it.

Indeed, Apache is very close to supporting HTTP/2 : mod_spdy is already there, and SPDY is close to HTTP/2… Chrome Canary implements it as well.

IMHO the only factor that will slow down (or even prevent) HTTP/2 to be massively deployed is that it enforces HTTPS use, and therefore buying a SSL certificate. Not all site may invest on that… ??

So, the next question is, how would you see WordPress taking advantage of this?

WordPress didn’t need to do anything to take advantage of SPDY, that was all at the server level, and unless I’m missing something, this is fundamentally no different.