LOPTR LAB / NETWORKING FOUNDATIONS

← Career tracks

HTTP/3 and QUIC

Learn the transport beneath modern web delivery from standards first, then test what it means for real applications.

STANDARDS-LED LEARNING PATH

Start with the protocol stack

HTTP/3 maps HTTP semantics onto QUIC. QUIC runs over UDP and provides encrypted, multiplexed streams, connection management, and transport reliability. QUIC uses TLS 1.3 as specified by the QUIC-TLS mapping. These are related layers, not interchangeable names.

Layer or concernWhat to learnPrimary reference
HTTP semanticsRequests, responses, methods, headers, caching, status codes.MDN: Overview of HTTP
HTTP/3HTTP framing over QUIC, request streams, control streams, settings, and protocol mapping.IETF RFC 9114
QUIC transportConnection establishment, stream multiplexing, flow control, connection migration, and loss recovery concepts.IETF RFC 9000
SecurityHow TLS 1.3 is integrated into QUIC; handshake and key phases.IETF RFC 9001
Loss and congestionPacket number spaces, acknowledgements, loss detection, and congestion control.IETF RFC 9002

A short study sequence

  1. Review HTTP basics. Explain a request and response, identify headers, and inspect a cache-control example.
  2. Compare HTTP/2 and HTTP/3. Draw the layers. Identify TCP in a common HTTP/2 deployment and QUIC/UDP in HTTP/3.
  3. Understand QUIC streams. Explain why independent streams can reduce transport-level head-of-line blocking between requests.
  4. Trace security. Describe why QUIC integrates TLS 1.3 rather than treating encryption as an optional add-on.
  5. Inspect a real deployment. Use browser developer tools or a server you control to check negotiated protocol and response headers. Record the test environment.
  6. Write a bounded finding. State what you observed, what you did not test, and what evidence would be needed before making a performance claim.

What this does—and does not—mean for games

HTTP/3 can improve the delivery of web content, APIs, launchers, patches, account services, and other HTTP traffic under some network conditions. It is not a universal replacement for a game's real-time networking design. Multiplayer games may use custom UDP protocols, WebSockets, WebRTC, or other transports depending on latency, reliability, platform, security, and gameplay requirements. Measure the actual workload before choosing a protocol.

Authoritative and maintained references

Standards and browser implementations evolve. Check the current RFC status, errata, browser support, and platform documentation before using this material to make production decisions.