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/2

Web & applicationIntermediate

Multiplex binary frames on a single TCP connection.

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

Connection preface + SETTINGS

After ALPN h2, the client sends the preface and connection settings.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20Connection preface + SETTINGS
1.400198.51.100.20192.0.2.10SETTINGS + ACK
2.800192.0.2.10198.51.100.20HEADERS
4.200198.51.100.20192.0.2.10HEADERS + DATA

Multiplex binary frames on a single TCP connection.

Explain Connection preface + SETTINGS and distinguish it from HEADERS + DATA.

Prerequisites: TCP, HTTP/1.1

Ready to test your understanding?

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

Learn from the sourceRFC 9113Protocol guide

HTTP/2: protocol guide / panduan protokol

Multiplex binary frames on a single TCP connection.

Multiplex frame biner pada satu koneksi TCP.

Communication walkthrough / Alur komunikasi

  1. Connection preface + SETTINGS

    After ALPN h2, the client sends the preface and connection settings.

    Setelah ALPN h2, klien mengirim preface dan pengaturan koneksi.

  2. SETTINGS + ACK

    The server sends its settings and acknowledges the client settings.

    Server mengirim pengaturan sendiri dan mengakui pengaturan klien.

  3. HEADERS

    A request uses a new stream with pseudo-headers encoded by HPACK.

    Request memakai stream baru dengan pseudo-header terenkode HPACK.

  4. HEADERS + DATA

    The response uses the same stream; END_STREAM finishes that direction.

    Respons memakai stream yang sama; END_STREAM mengakhiri arah tersebut.

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 9113 ↗