Skip to content

HTTP/3

HTTP/3 carries HTTP over QUIC. Benefits and reachability also depend on the network and endpoints; a universal speed improvement is not established.

Cloud & Operations

What is HTTP/3?

HTTP/3 is an HTTP version that uses QUIC as its transport. RFC9114 describes the mapping of HTTP semantics onto QUIC and its separate, reliable streams. Connection establishment incorporates TLS. This gives the application no new permissions in the business workflow.

Example: also offering the portal over QUIC

In a fictional design, the public portal access point also supports HTTP/3. The team checks whether the client, access point and network can actually use that connection. The internal application server may be configured differently.

A network can prevent the required UDP communication. RFC9114 recommends that clients try TCP-based HTTP versions for such connectivity problems. The team should therefore also check the intended alternative access.

A faster user experience must be measured under the relevant conditions. The protocol version alone resolves neither slow application logic nor excessive data volumes, and does not confirm successful storage of a request.

Sources

Articles on this topic

Cloud & Operations with ASES

Hosting, deployment, maintenance and support