🌐HTTP/3

NEW

The third major version of HTTP built atop QUIC to reduce latency and improve reliability.

DESCRIPTION

HTTP/3 maps HTTP semantics to the QUIC transport protocol, replacing TCP with a UDP-based, multiplexed, encrypted transport. It mitigates head-of-line blocking and improves connection migration, startup, and recovery. Adoption across browsers and CDNs accelerates web performance and resilience under real-world network conditions. It integrates closely with TLS 1.3 and modern security practices, making secure-by-default transport standard. HTTP/3 coexists with HTTP/2, with servers and clients negotiating the most capable protocol.

ALTERNATIVE DEFINITIONS

IETF RFC 9114

This document specifies the core of HTTP/3, the mapping of HTTP semantics over the QUIC transport protocol.

Normative specification defining HTTP semantics over QUIC.

Source

MDN Web Docs

HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on top of the QUIC transport protocol.

Developer-focused overview highlighting QUIC foundation.

Source

Google Chrome Developers

HTTP/3 uses QUIC as its transport instead of TCP, enabling faster and more robust connections.

Emphasizes transport replacement and performance benefits.

Source

RELATED TERMS

QUIC TLS 1.3 UDP REST gRPC Content Delivery Network TLS

COMPETING TERMS

HTTP-2

KNOWLEDGE AREAS

Infrastructure Software Engineering Data Integration & Interoperability Real-time & Streaming Data

TARGET AUDIENCE

Software Developer DevOps Engineer Cloud Architect Security Architect Solution Architect

EXTERNAL SOURCES

• Wikipedia - HTTP/3
• IETF RFC 9114 - Official HTTP/3 specification
• MDN Web Docs - Developer overview of HTTP/3
• Cloudflare - Vendor explainer on HTTP/3

TOP QUESTIONS

What is HTTP/3 and why was it introduced?

HTTP/3 maps HTTP onto QUIC to solve TCP head-of-line blocking and improve performance, reliability, and security. It enables faster page loads and better resilience on diverse networks.

Category: Overview

How does HTTP/3 differ from HTTP/2?

HTTP/3 uses QUIC over UDP with stream multiplexing and connection migration, while HTTP/2 uses TCP. This removes TCP head-of-line blocking and improves handshake speed.

Category: Comparison

Why is QUIC central to HTTP/3?

QUIC provides encrypted, multiplexed streams, faster handshakes, and connection migration over UDP. These features enable HTTP/3’s performance and reliability improvements.

Category: Requirements

Is HTTP/3 widely supported today?

Support is strong across major browsers, CDNs, and cloud providers. Servers often offer HTTP/2 and HTTP/3, negotiating the best available protocol at runtime.

Category: Relevancy

What are common mistakes when configuring HTTP/3?

Ignoring UDP firewall policies, misconfiguring TLS 1.3, and not tuning congestion control can hinder performance or block traffic. Proper observability is essential.

Category: Mistakes

Does HTTP/3 improve security?

Yes. QUIC encrypts transport-level metadata and mandates modern TLS, reducing ossification and increasing privacy compared to legacy HTTP/TCP stacks.

Category: Risk

How do you enable HTTP/3 on a service?

Use a server or CDN supporting QUIC, enable UDP on firewalls, configure TLS 1.3, and verify negotiated protocols via browser dev tools or logs.

Category: HowTo

What metrics matter for HTTP/3 performance?

Handshake time, stream-level RTT, packet loss, congestion window behavior, and error rates. Use QUIC-aware telemetry for accurate insight.

Category: Observability

Which protocol competes with HTTP/3?

HTTP/2 remains widely used and efficient on stable networks. HTTP/3 typically outperforms it under lossy or mobile conditions.

Category: Alternatives