HTTP/1.1 Referenz
Referenz für HTTP/1.1 protocol: Methoden, headers, persistent connections, pipelining, und chunked transfer.
Protocol Features
HTTP/1.1 (RFC 9112) introduced persistent connections by default via Connection: keep-alive. Pipelining allows sending multiple requests without waiting for responses, though proxy support is poor. Chunked transfer encoding streams response bodies of unknown length. The Host header is mandatory, enabling virtual hosting. HTTP/1.1 defines content negotiation via Accept-* headers.
- keep-alive
- Persistent connections
- chunked
- Streaming bodies
- Host
- Mandatory header
default in 1.1Transfer-Encoding: chunkedvirtual hostingLimitations
HTTP/1.1 suffers from head-of-line blocking: a slow response blocks subsequent requests on the same connection. Browsers work around this by opening 6 connections per origin. Text-based framing adds overhead and complexity. Headers are uncompressed, leading to significant overhead for cookies and metadata. These limitations motivated HTTP/2 and HTTP/3 development. Connection reuse helps but does not solve HOL blocking.
- HOL blocking
- Slow request blocks pipeline
- 6 connections
- Browser workaround
- text framing
- Overhead vs binary
per connectionper originuncompressed headers