Shulou(Shulou.com)06/02 Report--

Client okhttp/3.4.1

Http2.0 protocol itself does not require to be based on https, but browsers and servers all require http2.0 over https. After all, https is the trend of the times. To experience the low latency of 2. 0, do a good job of https.

Therefore, the use of unencrypted http2.0 requires modification of the okhttp source code, which is not complicated. My strategy is to determine host when the protocol is http. If it is our domain name xxx.suning.com, the protocol returns HTTP_2.

Server nginx/1.10

In the past, it was always thought that http2.0 must and can only be configured on port 443 of server and on port 80, which must report an error. After practice, it should be like this, http2.0 can not be configured on port 80, all other ports can, such as 81,82,83,443.

During the test, http2.0 was configured on port 81. The client accesses http://xxx.suning.com:81 and the protocol is h3.

Action

For a single interface, if you remove the SSL handshake process, you can reduce about 180ms.

There is still no enforcement of https, and unencrypted http2.0 still has a chance to use its talents.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.