Original article by DANIEL STENBERG

Translator: UC International research and development Jothy


Welcome to the “UC International Technology” public account, we will provide you with the client, server, algorithm, testing, data, front-end and other related high-quality technical articles, not limited to original and translation.

The protocol that was long known as HTTP-over-QUIC is now officially known as HTTP/3. A decision that initially by Mark Nottingham proposal (https://mailarchive.ietf.org/arch/msg/quic/RLRs4nB1lwFCZ_7k0iuz0ZBa35s).

The QUIC working group in IETF is dedicated to creating the QUIC transport protocol. QUIC is a protocol implemented based on UDP to replace TCP. The QUIC protocol was originally a Project initiated by Google, and has gradually become the HTTP/2-encrypted-over-UDP protocol.

When IETF began its standardization work, the protocol was divided into two layers: the transport part and the HTTP part. The idea was to consider that the transport protocol could also be used to transport other data, not just HTTP or HTTP-like protocols. But the name is still QUIC.

The community uses the informal names iQUIC and gQUIC to refer to these different versions of the protocol in order to separate IETF from Google’s proposed QUIC protocol (because they differ in many details). For a long time in the past, the protocol for sending HTTP requests through iQUIC was called HQ (HTTP-over-QUIC).

Mike Bishop wowed the room at the QUIC Working Group meeting at IETF 103 when he demonstrated this powerpoint and explained what to expect from the logo…

On November 7, 2018, Dmitri of Litespeed announced that they and Facebook had successfully completed interoperability testing for two HTTP/3 implementations.



You can see Mike Bihop’s follow-up demo of the HTTPbis section on this topic in the Youtube video below. The meeting ended with a consensus on a new name: HTTP/3!

Video of Mike Bihop’s talk:


There is no doubt that a new version of HTTP is coming, and it is HTTP/3 based on QUIC transport!


英文原文 :

HTTP/3



Good article recommendation:

Have an in-depth understanding of V8’s Call Stack

The history of the JavaScript engine V8



UC International Technology is committed to sharing high quality technical articles with you

Please follow our official account and share this article with your friends