HTTP/3 is not just another update; it's a substantial leap forward in web technology. As of June 2022, it's officially a Proposed Standard in RFC 9114. If you’re in the web game, like us at Uploadcare, you should be on this.
HTTP/3 is pretty much the same as its ancestors in the semantics—think status codes and request methods. But it's like they've been through a makeover for the modern web. It's HTTP but with less latency and more speed. Real-world usage shows it can be over 3x faster than HTTP/1.
As of now, 94% of tracked browsers support HTTP/3, and it's being used on 26% of the top 10 million websites. This includes major players like Google Chrome, Microsoft Edge, and Firefox. Safari's playing hard to get; it’s there but disabled by default.
HTTP/3 has roots in a draft by the QUIC working group. It was initially a sequel to HTTP/2 but quickly earned its unique identity and name. The name change was proposed by Mark Nottingham, Chair of the IETF HTTP and QUIC Working Groups, to highlight its uniqueness.
HTTP/3 uses QUIC, a protocol designed to fix the "head-of-line blocking" issue—a packet loss problem that plagued HTTP/2. QUIC is like that friend who ensures you get to the party on time, no matter how chaotic the traffic.
HTTP/3 introduces new DNS resource records, SVCB and HTTPS, allowing quicker connections without the usual handshaking dance. It's like skipping the line at a club because you know the bouncer.
LiteSpeed Web Server was the first to enable HTTP/3 by default in June 2021. Nginx jumped on the bandwagon in May 2023. Even Microsoft IIS has native support in Windows Server 2022/Windows 11.
For us at Uploadcare, HTTP/3's low latency and high speed are tempting. But we're also looking at server-side implementations and CPU usage. HTTP/3 is the future of the internet, and we are closely monitoring its development and planning to support it in the future.
Previous term: What is http 2
Next term: What is cloud hosting