FREE & OPEN
THE OPEN PROTOCOL PLAYGROUND

Make every packet make sense.

Explore the conversations that connect our world. One packet at a time.

66 protocolsZero paywalls. Endless curiosity.

HTTP/3

Web & applicationIntermediate

Map HTTP semantics onto independent QUIC streams.

SIMULATION01 / 04
Loading topology…
0.0s / 4.2s
01
STEP 1 OF 4Client → Server / peer

QUIC + h3 ready

A completed QUIC handshake negotiates h3 using TLS ALPN.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20QUIC + h3 ready
1.400192.0.2.10198.51.100.20Control stream SETTINGS
2.800192.0.2.10198.51.100.20Request HEADERS
4.200198.51.100.20192.0.2.10Response HEADERS + DATA

Map HTTP semantics onto independent QUIC streams.

Explain QUIC + h3 ready and distinguish it from Response HEADERS + DATA.

Prerequisites: QUIC, HTTP/1.1

Ready to test your understanding?

Rebuild the exchange. Read the fields. Find the mistakes.

Learn from the sourceRFC 9114Protocol guide

HTTP/3: protocol guide / panduan protokol

Map HTTP semantics onto independent QUIC streams.

Petakan semantik HTTP ke stream QUIC mandiri.

Communication walkthrough / Alur komunikasi

  1. QUIC + h3 ready

    A completed QUIC handshake negotiates h3 using TLS ALPN.

    Handshake QUIC yang selesai menegosiasikan h3 melalui TLS ALPN.

  2. Control stream SETTINGS

    A unidirectional control stream communicates HTTP/3 settings.

    Stream kontrol searah mengirim pengaturan HTTP/3.

  3. Request HEADERS

    QPACK compresses headers on a client-initiated bidirectional stream.

    QPACK mengompresi header pada stream dua arah yang dimulai klien.

  4. Response HEADERS + DATA

    The response returns on that request stream without TCP head-of-line blocking.

    Respons kembali pada stream request tanpa head-of-line blocking TCP.

Source and simulation scope

This is a simplified, deterministic teaching scenario. Timing is illustrative. Messages grouped within one event are explicitly condensed. Hexadecimal fixtures, where shown, contain only the indicated protocol ADU, not a full network capture. No PCAP files are supplied.

RFC 9114 ↗