HTTP
In depthProtocol / format
Also known as: HyperText Transfer Protocol
The protocol the web runs on: request and response between client and server.
HTTP, explained
Written by EduVerseWhat it is
HTTP (HyperText Transfer Protocol) is how browsers, apps and servers talk to each other on the web. A client sends a request with a method such as GET or POST, a path, headers and sometimes a body. The server answers with a status code like 200 or 404, headers and usually a body.
Why teams use it
Because it’s a simple, open standard that every language and platform supports, any client can talk to any server without special arrangements. Almost every website, API and webhook you’ll touch runs on it. Once you understand methods, headers and status codes, most web bugs become readable instead of mysterious.
An example from work
You submit a form and nothing happens. In the Network tab of DevTools you click the request and see it went out as POST /api/orders and came back with status 422, plus a response body explaining that the email field is missing. The bug is in your form, not on the server.
Our own explanation, not a quote from the book.
In the book
Sentences from The Software Realm, Decoded that mention HTTP, exactly as printed.
4 more passages about HTTP in the full book
Read every conversation where HTTP comes up, with the interactive slides and demos.
Where it fits
The basis of all web communication
Coverage in the book
Covered in depth: multiple pages with explanations, examples and simulations.
