HTTP and the Web Page in Your Browser

Lesson 9 · taught by Pip

In the last lesson we met the client (your browser), the server (the computer holding the page), and the idea that one asks and one answers. Today we learn the actual language they speak when they do it. That language is called HTTP.

HTTP is just an agreed way to say "please send me this" and "here you go." Nothing mystical — it's a polite, predictable exchange of notes.

The plain idea

Think of ordering at a deli counter. You say a specific thing: "One turkey on rye, please." The person behind the counter either hands you the sandwich, or says "we're out of rye" — and either way you get a clear answer back. You don't shout your whole life story; you make one tidy request, and you get one tidy response.

HTTP works the same way. Your browser sends a request — "GET me the page at this address" — and the server sends a response — the page itself, or a note explaining why it can't.

Watching one page get built

Type an address and hit enter. Here's what happens, in order:

1. Your browser sends a request that names the page it wants. The most common request is a GET, which simply means "fetch this for me."

1. The server answers with a status code — a short number that says how it went. 200 means "all good, here it is." 404 means "I looked, that page isn't here." 500 means "something broke on my end." You've seen 404 before; now you know it's just HTTP being honest.

1. Along with the status, the server sends the page's HTML — the text and structure of the page.

But here's the part most people miss: that first response is rarely the whole page. The HTML is more like a recipe than a finished meal. As your browser reads it, it discovers the page also needs a stylesheet here, three images there, a logo up top. So it fires off more HTTP requests — one for each piece — and assembles them as the answers arrive.

That's why a page often appears in stages: the text shows first, then a picture pops in, then the styling snaps into place. You're literally watching a stack of small requests and responses finish at different speeds.

Why this matters

Every web page you've ever loaded — a news article, a shop, a branded business assistant like the ones Portmint builds — is just this conversation repeated, sometimes dozens of times, in under a second. When something "won't load," it usually means one of these requests got a sad status code instead of a 200.

Your turn

Open any website, then open your browser's developer tools (often F12 or right-click → "Inspect") and find the Network tab. Reload the page and watch the list of requests stream in — each row is one HTTP request and its status code. Spot a few 200s.

That's HTTP: a tidy back-and-forth that builds the page in front of you. Next we'll add a lock to this conversation — how HTTPS keeps it private and safe. 🔦