HTTP/3 and QUIC: how modern web transport works

HTTP/3 is a version of HTTP that uses QUIC instead of the familiar HTTP/2, TLS and TCP combination. QUIC runs over UDP but adds reliable streams, congestion control and secure connection establishment. Supporting HTTP/3 alone does not make every page fast.

What changes from HTTP/2

Methods such as GET and response codes keep their usual meaning; the transport of messages changes. HTTP/2 multiplexes streams over one TCP connection. A missing TCP segment can delay delivery of data from other streams at the transport layer. QUIC manages multiple streams itself, so loss in one stream does not hold up other streams in the same way. This can help on lossy networks, but it cannot remove physical distance or a slow server.

QUIC integrates security based on TLS 1.3 into its handshake. “Over UDP” does not mean sending page content in plain text: HTTP/3 uses a protected connection. Some repeat connections can avoid part of the setup delay, depending on what client and server already know. The benefit varies with implementation and network conditions rather than being a fixed speed boost.

Port 443 and fallback

HTTP/3 commonly uses UDP port 443; HTTPS with HTTP/2 commonly uses TCP port 443. If a network firewall blocks UDP, a QUIC connection may fail to start. Clients can use another supported version of HTTP over TCP instead. Blocking UDP 443 therefore need not make a site unreachable, although it may alter performance or make diagnosis confusing. A TCP 443 port test does not establish HTTP/3 support.

Browser developer tools can show the protocol used by an individual request. Do not rely only on a hosting provider’s feature list: a CDN, reverse proxy and resources embedded in the page may use different connections. To verify the live site, make a request with a capable client and inspect what was negotiated.

Where it can help

HTTP/3 can help when packets are lost or a mobile device changes network path, provided the implementations support the relevant mechanisms. It will not repair oversized images, unnecessary scripts or slow application code. Measure page loading and user experience, not just the protocol label. The HTTP/3 and QUIC specifications define the details. The TCP and UDP guide explains the underlying transport choices.