A very small update was sent to the nginx-announce mailing list today. And I do mean very small:
Changes with nginx 1.10.0 -– 26 Apr 2016
*) 1.10.x stable branch.
-–
Maxim Dounin
At first, you wouldn’t think much of it.
However, this new release includes support for HTTP/2. That means from now on, HTTP/2 is available in the stable Nginx releases and you no longer need the “experimental” mainline releases.
$ nginx -V nginx version: nginx/1.10.0 built by gcc 4.4.7 20120313 (Red Hat 4.4.7-16) (GCC) built with OpenSSL 1.0.1e-fips 11 Feb 2013 TLS SNI support enabled configure arguments: ... --with-http_v2_module
This is very good news for the adoption of HTTP/2! If you’re running Nginx from their official repositories and you have SSL/TLS enabled, I suggest you go ahead and enable HTTP/2 right now.
If you’re new to HTTP/2 and want to learn more about it, here are some resources I created:
- Video: my HTTP/2 for PHP Developers talk at FOSDEM 2016
- Podcast: delving into HTTP/2
- Architecting websites for the HTTP/2 era (a set of best practices for HTTP/2)
- How to enable HTTP/2 in Nginx
- HTTP/1.1 vs HTTP/2 page loading benchmark
- Server Side Push in HTTP/2
- How to view the HTTP/2 protocol in Chrome
Exciting news!
Update: Alan kindly reminded of the impending doom happening on May 15th when Chrome disables NPN support. In short: having the http2 option enabled won’t help, as your OS will no longer be able to support HTTP/2.