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

Web & applicationIntermediate

Inspect a readable request, response and cache validation.

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

GET /status

The request line selects a resource; Host identifies the virtual host. TCP is already established.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20GET /status
1.400198.51.100.20192.0.2.10200 OK
2.800192.0.2.10198.51.100.20Conditional GET
4.200198.51.100.20192.0.2.10304 Not Modified

Inspect a readable request, response and cache validation.

Explain GET /status and distinguish it from 304 Not Modified.

Prerequisites: Ethernet

Ready to test your understanding?

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

Learn from the sourceRFC 9112Protocol guide

HTTP/1.1: protocol guide / panduan protokol

Inspect a readable request, response and cache validation.

Periksa request, respons, dan validasi cache yang dapat dibaca.

Communication walkthrough / Alur komunikasi

  1. GET /status

    The request line selects a resource; Host identifies the virtual host. TCP is already established.

    Request line memilih resource; Host mengidentifikasi virtual host. TCP telah terbentuk.

  2. 200 OK

    The server sends a representation with framing and an entity tag.

    Server mengirim representasi dengan framing dan entity tag.

  3. Conditional GET

    If-None-Match asks whether the stored representation remains current.

    If-None-Match menanyakan apakah representasi tersimpan masih berlaku.

  4. 304 Not Modified

    No response body is sent; the browser can reuse its cached representation.

    Tidak ada body respons; browser dapat memakai representasi cache.

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