How the Web Works

30 min read

DNSIP AddressesHTTP/HTTPSHTTP/2 & HTTP/3Request/Response Cycles

The Journey of a Request

Every time you type a URL and press Enter, a complex chain of events unfolds in milliseconds. Understanding this journey is the foundation of becoming a frontend expert.

DNS Resolution

Your browser first needs to convert the human-readable domain name (like google.com) into an IP address. This involves querying DNS servers in a hierarchical lookup: browser cache → OS cache → Router → ISP DNS → Root DNS servers.

HTTP/HTTPS Protocols

Once the IP is resolved, your browser establishes a connection using HTTP (or HTTPS for encrypted communication). In 2026, most traffic uses HTTP/2 (multiplexed streams) or HTTP/3 (built on QUIC/UDP for faster handshakes).

Request/Response Cycle

The browser sends a request with headers (method, cookies, accepted formats), and the server responds with a status code, headers, and the body (HTML, JSON, etc.).

The Journey of a Request

Every time you type a URL and press Enter, a complex chain of events unfolds in milliseconds. Understanding this journey is the foundation of becoming a frontend expert.

DNS Resolution

HTTP/HTTPS Protocols

Request/Response Cycle

The browser sends a request with headers (method, cookies, accepted formats), and the server responds with a status code, headers, and the body (HTML, JSON, etc.).