bk99.de entertain the web since 1997

bk99.de
RFC · WebStandard explained

RFC 9114: HTTP/3 over QUIC

Summary

RFC 9114 maps HTTP semantics onto QUIC and avoids TCP-induced blocking between independent streams. HTTP/3 ties application and transport development more closely together than earlier versions. UDP reachability becomes an important operational factor again.

Ideas

  • Each request typically uses one QUIC stream.
  • QPACK compresses headers for independent streams.
  • QUIC takes care of security, loss handling and path changes.

Remarks

  • RFC 9114 has the status “Proposed Standard”; current errata and successor documents should also be checked.

Recommendations

  • Test HTTP/3 with real firewalls and mobile network paths.
  • Keep a reliable HTTP/2 fallback.

References

Read the RFC at the RFC Editor

Search the Web Archive

RFC · 2015

RFC 7540: HTTP/2: Multiplexing over one connection

RFC 7540 introduces binary frames, parallel streams and header compression for HTTP. RFC 7540 was superseded by RFC 9113. Multiplexing reduces application delay but remains tied to TCP packet loss.

RFC · 2026

RFC 10008: HTTP QUERY: Safe, idempotent queries with content

RFC 10008 defines the HTTP method QUERY for complex, safe and idempotent queries with request content. New methods close gaps when established semantics do not fit cleanly. Explicit semantics are better than misused POST requests.

RFC · 2022

RFC 9110: HTTP semantics reorganised

RFC 9110 defines the shared semantics of HTTP independently of the concrete transport versions. Separate semantics allow HTTP/1.1, HTTP/2 and HTTP/3 to share a common basis. Clear terms reduce contradictory implementations.