Evolution of HTTP: From 0.9 to HTTP/3 and QUIC
This article traces the development of the HTTP protocol from its earliest 0.9 version through HTTP/1.1, HTTP/2, and finally HTTP/3 built on QUIC, highlighting how each iteration improved speed, efficiency, and mitigated head‑of‑line blocking while introducing new challenges.
HTTP has evolved from version 0.9 to HTTP/3, driven by the need for higher speed and efficiency.
Early versions (0.9, 1.0) lacked connection reuse; HTTP/1.1 introduced TCP connection reuse and parallel connections, reducing handshake overhead but still suffered from head‑of‑line (HOL) blocking.
HTTP/2 (originating from SPDY) added multiplexed streams, header compression (HPACK), and server push, eliminating HTTP‑level HOL blocking while still inheriting TCP‑level issues.
HTTP/3 adopts QUIC over UDP, providing true multiplexed streams, 0‑RTT/1‑RTT connection establishment, stronger DH key exchange, user‑space implementation, and seamless connection migration, thereby solving TCP’s HOL blocking.
Nevertheless, QUIC faces challenges such as slower kernel UDP processing, higher CPU usage, and network devices that restrict UDP traffic.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Byte Quality Assurance Team
World-leading audio and video quality assurance team, safeguarding the AV experience of hundreds of millions of users.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.