HTTP/HTTPS — Part 2: Architecture, Methods, Headers & the Connection Model

What is this?

In Part 1 we said HTTP is a strict postcard format that every web client and server agrees on. Now we turn the postcard over and read the fine print. What exactly is written on it? What does the first line mean versus the lines below the fold? How does a forgetful server suddenly "remember" your shopping cart? And once the postcard is delivered, does the mail carrier go home — or hang around to carry the next one?

This part is about the anatomy and the plumbing: the precise shape of requests and responses, the verbs (methods) and the fine print (headers), the cookie trick that smuggles state past a stateless protocol, and the connection mechanics that decide whether your site feels fast or sluggish.

The one-line idea: an HTTP message is just a start-line, a block of headers, a blank line, and an optional body — and almost every clever thing HTTP does (auth, caching, compression, cookies, CORS) is just another header riding on that simple shape.

That's the beautiful part. The structure barely changes; the headers do all the work.