Protocols
Saved & recent

HTTP/1.1

Also called: HTTP 1.1, persistent HTTP connection

HTTP/1.1 defines a textual message format and connection rules for HTTP exchanges. A start line and header lines precede any body; framing rules identify where that body ends. Connections can be reused for multiple exchanges, avoiding a fresh connection for every resource.

Imagine requesting a large image and then a small stylesheet on one connection. Even with pipelined requests, HTTP/1.1 responses must arrive in request order, so the stylesheet can wait behind the image. Browsers can use additional connections for concurrency. The protocol version changes message handling without changing what GET or a 404 response means.

Read first
HTTP
Related
HTTP/2, TCP, HTTP headers
Further reading
IETF RFC 9112 — HTTP/1.1
client server one persistent connection requests sent before replies 1 · GET image 2 · GET stylesheet pipelined request example 1 · large image response 2 · stylesheet responses follow request order time
Illustrative pipelining on one HTTP/1.1 connection. The stylesheet response follows the earlier image response even if it is ready sooner. Pipelining is possible, not universal client behavior.

View in the full Protocols collection