How It Works — Cloud

The pipes that carry everything else. How a browser reaches a server, how a name becomes an address, how a connection is opened and encrypted, how state survives a stateless protocol.

Foundations [Foundations] {1}

Small, self-contained mechanisms every later flow quietly assumes you already know.

Client/Server — One Side Asks, One Side Answers [Client / Server] {1}

The Stateless Nature of HTTP Requests [Stateless Problem] {1}

Cookies — A Memory Mechanism for HTTP Requests [Cookies] {1}

Cookies — Tracking Users Across Requests [Cookies Tracking] {1}

Redirect — How One Server Sends a Browser to Another [Redirect] {1}

Form POST Redirect — How a Server Redirects with a Body [Form POST Redirect] {1}

Networking & DNS [Networking] {1}

How a name becomes an address, how a connection is opened and encrypted, how the plumbing under HTTP actually works.

Recursive DNS Resolution [DNS] {1}

DNSSEC Chain of Trust [DNSSEC] {1}

HTTP/1.1 Request Lifecycle [HTTP] {1}

HTTP/2 Multiplexing — Many Requests on One Connection [HTTP/2] {1}

WebSocket Handshake [WebSocket] {1}

TCP Three-Way Handshake [TCP] {1}

TLS 1.3 Handshake [TLS] {1}

Mobile [Mobile] {1}

Client environments where the network changes mid-connection and the OS sits between the browser and the app.

QUIC Connection Migration — WiFi to Cellular Without a Reconnect [QUIC] {1}

Universal Links — Opening a Native App from an HTTPS URL [Universal Links] {1}

Push Notifications — APNs and FCM [Push Notifications] {1}