After years of hard work, on June 6, 2022, the IETF (Internet Engineering Task Force) officially released the RFC for HTTP/3, the third major version of the Hypertext Transfer Protocol (HTTP), and the full RFC is over 20,000 words and explains HTTP/3 in great detail.
At the same time, the Internet Engineering Task Force (IETF) has also updated the HTTP/1.1 and HTTP/2 protocols, as follows:
HTTP/3 - RFC 9114 protocol:The hyperlink login is visible.
HTTP/2 - RFC 9113 protocol:The hyperlink login is visible.
HTTP/1.1 - RFC 9112 protocol:The hyperlink login is visible.
QUIC
QUIC (Quick UDP Internet Connection) is one of a kind developed by GoogleBased on UDPLow latency Internet transport layer protocol. In November 2016, the International Internet Engineering Task Force (IETF) held the first QUIC working group meeting, which received widespread attention from the industry. This also means that QUIC has begun its standardization process as a next-generation transport layer protocol.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol for exchanging information on the World Wide Web, along with HTTP/1.1 and HTTP/2. HTTP/3 always runs on QUIC (not TCP for TCP/IP, QUIC replaces it), and it's done (and is at the heart of HTTP/3).
There are many ways to implement HTTP/3, such as Cloudflare's quiche, Caddy's experimental branch, and Nginx's official QUIC branch.
Since Openssl does not officially support the QUIC protocol, the reason given is that they are still busy developing Openssl-3.0 and QUIC updates are too fast, so we need to use a branch developed by GoogleBoringssl。
BoringSSL is a fork of OpenSSL created by Google, but code using BoringSSL does not guarantee the stability of the API or ABI, so Google will continue to submit bug fixes to OpenSSL and continue to fund the Core Infrastructure Initiative and the OpenBSD Foundation.
Background: Google used over 70 OpenSSL patches, some of which were accepted into the OpenSSL main repository, but most did not. As Android, Chrome, and other projects begin to require a subset of these patches, things become increasingly complicated, and it takes too much effort to ensure that all patches work correctly across different codebases. So they decided to create an OpenSSL branch.
nginx official website quic branch site:The hyperlink login is visible.
Demo site for nginx-quic:The hyperlink login is visible.
How fast is HTTP/3?
New York, USA: Here are the HTTP/2 vs. HTTP/3 response times when requesting from three different sites from the New York data center:
HTTP/3 in:
Small sites are 200 milliseconds faster
The content site is 325 milliseconds faster
Single-page apps are 300 milliseconds faster
Minnesota is 1000 miles (approximately equal to 160 kilometers) from New York; This length is nothing for a network connection. However, it is important that HTTP/3 is able to improve performance even over relatively short distances.
The test supports QUIC-HTTP/3
Currently, there are two websites that can be used to test whether our website supports QUIC-HTTP/3, as follows:
The hyperlink login is visible.
The hyperlink login is visible.
(End)
|
Posted on 6/12/2022 2:07:25 PM
|
|
|
|
Landlord|
Posted on 6/12/2022 2:08:31 PM
|
