The Complete Guide to HTTP for Developers -...

HTTP is the protocol the web runs on. Every API call, page load, and asset fetch is an HTTP request and response underneath. This guide covers it end to end — how a request is shaped, the methods, the status codes, and the headers — so the next time you're staring at a failing request, you know exactly where to look.

Prefer a focused read? Jump to Anatomy of an HTTP Request for the structure, HTTP Request Methods for GET/POST/PUT/DELETE, HTTP Status Codes Explained for the response codes, or How to Read HTTP Headers for the metadata.

What HTTP is

HTTP (HyperText Transfer Protocol) is a request–response protocol: a client (a browser, an app, curl) sends a request to a server, and the server sends back a response. It is stateless — each request stands on its own, and anything the server needs to "remember" travels in headers (like cookies or auth tokens) on every request.

HTTPS is the same protocol over an encrypted TLS connection. The messages look identical; TLS just keeps them private and tamper-evident in transit.

Anatomy of a request and response

A request has four parts: a method and path (the request line), a set of headers, and an optional body:

POST /api/users HTTP/1.1
Host: example.com
Content-Type: application/json

{ "name": "Ada" }

A response mirrors that shape: a status line (protocol + status code), its own headers, and usually a body:

HTTP/1.1 201 Created
Content-Type: application/json

{ "id": 1, "name": "Ada" }

Full breakdown in Anatomy of an HTTP Request and Response.

Methods: what you're asking for

The method (or verb) states your intent. The everyday set:

GET — read a resource (no body, safe, cacheable)
POST — create a resource or trigger an action
PUT — replace a resource; PATCH — partially update it
DELETE — remove a resource

Two properties matter: safe methods don't change server state (GET), and idempotent methods give the same result if repeated (GET, PUT, DELETE). See HTTP Request Methods for the full table.

Status codes: how it went

The response status code tells you the outcome, grouped into five classes:

1xx informational · 2xx success · 3xx redirection · 4xx client error · 5xx server error

A quick rule: 4xx is your fault (bad request, unauthorized, not found), 5xx is the server's. Deep dive in HTTP Status Codes Explained, or look one up in the status code tool.

Headers: the metadata

Headers carry everything about the message that isn't the body — content type, length, auth tokens, caching rules, cookies, CORS. Content-Type: application/json tells the other side how to read the body; Authorization: Bearer … carries a token; Cache-Control governs caching. See How to Read and Parse HTTP Headers.

Debug real requests with the HTTP Status Code lookup, HTTP Headers Parser, and cURL Formatter — all client-side, nothing uploaded.

Try it

Paste a status code or a block of response headers into the tools above and get an instant, readable breakdown — right in your browser.

The Complete Guide to HTTP for Developers