ProtoStackv0.1

Interactive Protocol Visualizer

Application LayerCore trackIntermediateOSI: Application LayerDefault Port: 443 (UDP)Standard: RFC 9114

HTTP/3

— Hypertext Transfer Protocol Version 3

HTTP/3 keeps the familiar request and response model but runs it over QUIC instead of TCP. Every stream is independent at the transport layer, so a lost datagram only stalls the stream it belonged to, and encryption is built in because QUIC always carries TLS 1.3.

Read first: HTTP/2, QUICContent reviewed 2026-11-18

Interactive Session: How HTTP/3 Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

Interact with a live or clearly-labelled simulated instance of HTTP/3.

Threat Model & Attack Simulation

How this protocol is attacked in practice, what defenders can see, and which control stops it.

Threat model & attack simulation

Simulated

Defensive education. Every step runs in this page; no traffic is generated or sent.

Attack library

0-RTT replay

Injection

Early data captured from a previous connection is replayed to a server that accepts 0-RTT.

Attackersimulated
HTTP/3target
Attack step 1 of 3
Capture early data

The attacker records a 0-RTT request, for example a state-changing API call.

What a defender can see

Repeated early-data requests with identical content.

Impact if unmitigated

Duplicate transactions and state corruption.

Defences that matter
  • Accept 0-RTT only for replay-safe methods
  • Server-side replay protection
  • Disable 0-RTT for authenticated state changes

This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.

Protocol Specification & Architecture

Key characteristics, real-world deployment patterns, and trade-offs.

Core Technical Features

  • Runs over QUIC, which is carried in UDP datagrams
  • Independent streams with no cross-stream head-of-line blocking
  • QPACK header compression (RFC 9204) designed for out-of-order delivery
  • Unidirectional control streams for SETTINGS and QPACK state
  • 0-RTT resumption for repeat visitors

Real-World Use Cases

  • Low-latency web delivery on lossy mobile networks
  • Video streaming and large asset downloads
  • Any HTTPS service already fronted by a QUIC-capable CDN

Advantages & Strengths

  • No transport-level head-of-line blocking between streams
  • Faster connection setup with 1-RTT and 0-RTT handshakes
  • Survives client IP changes through QUIC connection migration

Limitations & Vulnerabilities

  • Some enterprise firewalls still throttle or block UDP 443
  • Higher CPU cost for user-space QUIC processing