Lesson 3.0

Orientation: from "the internet" to a stack of layers

Artifact: A four-layer picture of the internet you carry through the chapter

1. The promise

You'll know what this chapter teaches, in what order, and why. By the end you can point at four named layers under every web request — IP, TCP, HTTP, HTTPS — and say in one sentence what each does. Right now "the internet" is one word for a thing you can't point at. By the end of this chapter, you can.

2. The mental model

The internet is a postal system stacked with extra services.

  • The bottom layer just hands envelopes around. Each envelope has a "to" address and a "from" address. That's IP.
  • On top of that is a registered-mail service. It promises every envelope arrives, in the order you sent them. That's TCP.
  • On top of that is a standard letter template both ends agree to. When you ask for a page, you write it like this. When the other end replies, they write it like that. That's HTTP.
  • On top of that is a sealed envelope nobody in the middle can read or tamper with. That's HTTPS, which uses a system called TLS to do the sealing.

Each layer assumes the one below is doing its job and adds something new.

A quick definition before we move on. A protocol is an agreed set of rules two computers follow so they can talk. Like the rules of a phone call: who speaks first, how you say goodbye, what to do if the line drops. A stack is what we call the picture of one protocol sitting on top of another, each one trusting the layer beneath it.

(DIAGRAM: the four-layer stack — annotated SVG — four stacked labelled boxes, IP at the bottom, then TCP, then HTTP, then HTTPS at the top, each with a one-line job description on the right)

3. You do it, with me

There's nothing to install in this unit. Read along and open one tab.

Open Chrome. Type example.com in the address bar and press Enter.

(SCREENSHOT: Chrome with the example.com homepage loaded — full window — no highlights)

Now open DevTools. Press F12 on Windows, or Cmd+Option+I on macOS. Click the Network tab. Reload the page with Ctrl+R or Cmd+R.

The Network tab fills with rows. Each row is one HTTP request the browser made to load this page.

(SCREENSHOT: Chrome DevTools Network tab during a page reload of example.com — full window — the first row, the HTML document, highlighted)

That first row is the main HTML document. Everything in this chapter is about what had to happen for that one row to appear on your screen.

Here's the path through the chapter, in plain English:

  • Units 3.1 to 3.4 cover the bottom of the stack: addresses, names, the reliable conversation, and door numbers on a machine.
  • Units 3.5 to 3.9 cover the web's own protocol: methods, status codes, headers, and the encrypted version.
  • Units 3.10 to 3.13 cover the supporting cast: caches, CDNs, cookies, and the browser's main cross-site rule.
  • Unit 3.14 puts every panel of DevTools to work on one live request.
  • The chapter assignment asks you to write the whole trace out yourself.

The order matters. If you skip the bottom and start with HTTP, HTTP will feel like magic for the rest of the course. The wire-up order means every concept lands on something that already makes sense.

(SCREENSHOT: the chapter index for Ch 3 in the browser — full window — the orientation unit highlighted)

4. What you should be seeing

A picture in your head with four labelled layers stacked on top of each other. The bottom one moves packets between addresses. The next one makes the conversation reliable. The next one is the web's letter format. The top one wraps it in a sealed envelope.

If you can list those four in order with one sentence each, you're ready for 3.1.

5. Common stumbles

  • You try to skip 3.1 to 3.4 and jump straight to HTTP. Don't. Every later unit assumes the layers below. You'll spend the rest of the chapter confused about why anything works.
  • You try to memorise every status code and every header in one sitting. The point of this chapter is recognition, not memorisation. The cheat sheets stay. You're learning to read them, not recite them.
  • You read this whole chapter in one afternoon. Don't. This chapter is denser than Ch 0 and Ch 2. Two days at three units a day is the honest pace.

6. You should know

1/16
Next