07-31-2016, 02:20 AM
Quote:Users of the Google Chrome web browser are seeing some sites that they previously accessed over HTTP/2 falling back to HTTP/1. This is because of a policy change in the most recent update to Chrome, released in late May [version 51], which removes support for NPN, one method for upgrading a connection to HTTP/2.https://www.nginx.com/blog/supporting-ht...ome-users/
[..] Website administrators can restore HTTP/2 support for Chrome users by upgrading their OpenSSL installation to the recently released 1.0.2 version. Unfortunately, this requires either a major operating system upgrade or using a private build of NGINX.
The same goes for Apache, of course. A bit of a setback for HTTP/2 users who, like me, haven't been paying attention.
(Fixed it though).