HTTP request-response client-server model

Summary

HTTP is an application-layer request–response protocol used in the client–server model. A client (such as a web browser or other user agent) sends an HTTP request to a server, and the server processes it and returns an HTTP response. The response includes headers that describe the outcome and, when applicable, a body containing the requested resource (e.g., HTML or other content) or an error message. HTTP runs over an underlying transport connection (typically TCP for HTTP/1.1 and earlier, and QUIC over UDP for HTTP/3). Communication is organized as a sequence of request/response messages within a session/connection, and connections may be closed or kept alive depending on the HTTP version and headers. HTTP is also designed to support intermediate network elements (like proxies and caches), with some headers treated as hop-by-hop and others as end-to-end, enabling performance and routing optimizations.

Key Points

• 1

  HTTP follows a client–server request–response transaction: client sends a request, server returns a response with status/disposition and optional content.

• 2

  HTTP relies on an underlying transport connection (TCP for earlier versions; QUIC over UDP for HTTP/3) and can close or reuse connections depending on version and headers.

• 3

  Persistent connections and related optimizations reduce latency by avoiding repeated TCP setup and enabling more efficient data transfer.

• 4

  HTTP supports intermediate nodes (proxies/caches) by distinguishing hop-by-hop headers from end-to-end headers.