Vol. I · No. 46The protocol sectionSat, 10 Oct 2026
Layer 7 · Web · HTTP with TCP taken out from under it

HTTP/3

HTTP over QUIC

HTTP/3 is HTTP/2’s multiplexing, finally done properly. It keeps the same semantics and streams but runs on QUIC over UDP instead of TCP, so loss on one stream does not stall every other stream and the connection survives a change of network entirely.

HTTP/3 moves HTTP onto QUIC — no TCP connection-wide head-of-line blocking, a faster handshake, and a session that follows you between networks.

Operates at
Layer 7
over QUIC
Port
443/udp
not TCP
Encryption
Always
TLS 1.3 inside QUIC
Standardised
2022
RFC 9114

How it works

The same request, one layer lower down
HTTP/2 over TCP
S1
S3
S5
Streams are independent to HTTP — but TCP below delivers in order, so one loss stalls all of them.
HTTP/3 over QUIC
S1
S3
S5
QUIC knows about streams, so unaffected streams keep moving while missing stream data is recovered.
QPACK

Header compression rebuilt for QUIC streams; a stream can still wait for referenced table updates, but not for unrelated packet delivery.

Alt-Svc

A server advertises h3 over its HTTP/2 response; the browser upgrades on the next visit.

Connection migration

Wi-Fi to cellular keeps the same connection ID — the download doesn’t restart.

The application layer barely changed: the same methods, headers and status codes ride on a transport that finally matches how the web actually behaves — and clients keep a TCP path ready in case UDP 443 is blocked.

The main points

What HTTP/3 does, step by step

1
Discover the upgrade

An Alt-Svc header or an HTTPS DNS record tells the client that h3 is available on UDP 443.

2
Open a QUIC connection

One round trip sets up transport and TLS 1.3 together — or zero, resuming a previous session.

3
Request on a stream

Each request takes its own QUIC stream, headers compressed with QPACK.

4
Recover independently

Missing data is recovered without stalling unaffected streams, and the connection can survive an IP change.

What it inherits from QUIC
Per-stream loss — no cross-stream stalling
0-RTT resume — data in the first packet
Connection IDs — migration between networks
Encrypted transport — headers protected too
User-space — shipped by the browser
UDP fallback — TCP path kept in reserve

In cybersecurity

HTTP/3 is encrypted end to end by construction — good for users, and a real change for anyone who relied on reading HTTP off the wire to defend a network.

Content is protected

HTTP content and most QUIC fields are encrypted; IP addresses, UDP ports, packet sizes and timing remain observable.

Middleboxes go blind

Appliances that parsed HTTP now see opaque UDP — inspection has to move to the endpoints.

0-RTT replay

Early data can be replayed, so only idempotent requests belong in it.

Amplification limits

A server may not send much more than it received until the client’s address is validated.

UDP filtering

Networks that block UDP 443 silently push everyone back to HTTP/2 — watch for the fallback.

Same app-layer risks

XSS, CSRF and injection are untouched by any of this; they live above the transport.

Rides in the stack

IPUDPQUICHTTP/3

TLS is not a separate layer here — QUIC has it built in, so there is no “HTTP/3 without encryption”.

Works with

HTTP/2QUIC

HTTP/2 or HTTP/3?

HTTP/2HTTP/3
TransportTCPQUIC / UDP
HOL blockingAcross streams at TCPLimited to affected stream data
Handshake2–3 RTT1-RTT or 0
HeadersHPACKQPACK