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.

WebSocket

Web & applicationIntermediate

Upgrade HTTP/1.1 into a bidirectional message channel.

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

Upgrade request

The client sends a key and requests the websocket upgrade.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20Upgrade request
1.400198.51.100.20192.0.2.10101 Switching Protocols
2.800192.0.2.10198.51.100.20Masked text frame
4.200198.51.100.20192.0.2.10Unmasked text frame

Upgrade HTTP/1.1 into a bidirectional message channel.

Explain Upgrade request and distinguish it from Unmasked text frame.

Prerequisites: HTTP/1.1

Ready to test your understanding?

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

Learn from the sourceRFC 6455Protocol guide

WebSocket: protocol guide / panduan protokol

Upgrade HTTP/1.1 into a bidirectional message channel.

Upgrade HTTP/1.1 menjadi kanal pesan dua arah.

Communication walkthrough / Alur komunikasi

  1. Upgrade request

    The client sends a key and requests the websocket upgrade.

    Klien mengirim key dan meminta upgrade websocket.

  2. 101 Switching Protocols

    The server derives Sec-WebSocket-Accept from the client key.

    Server menghitung Sec-WebSocket-Accept dari key klien.

  3. Masked text frame

    Client-to-server frames are masked; masking is not encryption.

    Frame klien ke server dimasking; masking bukan enkripsi.

  4. Unmasked text frame

    Server-to-client frames are not masked.

    Frame server ke klien tidak dimasking.

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