Chrome will be upgraded to the end of May to the fifty-first version, when most users will not be able to use HTTP/2

User Chrome

Linuxyidianyuankaiyuan· 2016-05-28 00:51:22

as early as last August, the Chromium project has been decided to start an abandoned NPN negotiation protocol (a transport layer security protocol extension protocol). The upcoming release of the Chrome 51 stable version in May 31st, the NPN agreement will be officially abolished, only to support the ALPN agreement. That is, all of the current NPN based negotiation protocol based on the HTTP/2 protocol will not be used, and was downgraded to HTTP/1.1. < the client not too big effect, but to the server using protocol HTTP/2, the NPN upgrade to ALPN, is not an easy thing, OpenSSL at least need to upgrade to version 1.0.2 can support ALPN. The

table is a common server operating system version OpenSSL version comes with:

OpenSSL
CentOS 50.9.8e
CentOS 61.0.1e
CentOS 71.0.1e
Ubuntu 14.04 LTS1.0.1f
Ubuntu 16.04 LTS 1.0.2g
Debi An 7 (wheezy) 1.0.1e
Debian 8 (Jessie) 1.0.1k

from this table can be seen, the server version, the default OpenSSL to 1.0.2 only Ubuntu 16.04 LTS. If you want to upgrade the OpenSSL version, the cost is very high, because there are a lot of packages rely on OpenSSL, these packages are required to re package and test. On the other hand, 1.0.1 OpenSSL's support will end in December 31, 2016. < p > in a traditional build lamp (Linux, Apache, mysql, PHP) server, usually rely on OpenSSL library software:

$lsof | grep libssl | awk ' {print $1}' | sort | uniq. Fail2ban gdbus gmain httpd postfix mysqld NetworkManager nginx PHP FPM puppet sshd sudo tuned ZABBIX Zabbix_agent

say, if the escalation of the OpenSSL version of the system, these packages are need to repack, if the API is not compatible, upgrade costs will be higher. < before the stable version of chrome 51, the following example of negotiation results will use protocol HTTP/2:

coolex ~ # nghttp - V - n https://ma.ttias.be [0.252] connected [0.507][NPN] server offers: * H2 * http / 1.1 the negotiated your h2

but after the upgrade, due to NPN negotiation logic has been abandoned, chrome will not negotiation server access protocol support HTTP/2, and relegation into the HTTP / 1.1 protocol.

for the problem, the most simple way to look at the present, is to run into a container, such as Docker, etc.. />


Linux Eden open source community (linuxeden_com)

The lastest articles of Linuxyidianyuankaiyuan

In Docker (six): deploy your application like Google

Daily articles featured 20161020

Nginx1.10.2 release, high performance Web server

PyCharm2016.3EAP4, new Python development experience

Drupal8.2.0 release, CMS content management system

Daily articles featured 20161004

Daily articles featured 20161003

ArchLinux2016.10.01 release

SparkIM2.8.1 release, repair a large number of bug

Vue2.0 official version released, a substantial increase in performance