HTTP/1.1
The text-based version of HTTP in which one connection carries one request and response at a time.
In more detail
Messages are readable lines of text: a request line, headers, a blank line, then the body. Because a connection handles one exchange at a time, a slow answer holds up the ones queued behind it.
Examples
In the APIs course: The course service speaks HTTP/1.1 because that is what the Python standard library server implements.curl -so /dev/null -w '%{http_version}\n' localhost:8765/tasksRelated terms
- HTTP — The protocol web browsers and web servers use to send requests and responses.
- HTTP/2 — A version of HTTP that sends the same methods, statuses and headers in a binary format and runs many requests at once over one connection.
- HTTP/3 — The newest version of HTTP, which keeps the meaning of HTTP/2 but runs over QUIC on UDP instead of TCP.
- TCP — The internet protocol that delivers data between programs reliably and in order, used by the web and most databases.
- keep-alive — Keeping a TCP connection open after an HTTP response so the same client can send further requests over it.
- head-of-line blocking — A delay where one slow or lost item at the front of a queue holds up everything behind it.
Taught in
- What An API Is, And The Alternatives — Modern API Architecture: REST, GraphQL & gRPC
- Native HTTP Server: Request & Response Lifecycles — Node.js Internals & Backend Services
- Native HTTP/2 Protocols: Multiplexed Streams & Push — Node.js Internals & Backend Services