Understanding HTTP Protocol: Concepts, Features, Workflow, Headers, Caching and Applications

1. Concept

HTTP (Hypertext Transfer Protocol) is an application‑layer protocol that defines how browsers and web servers communicate, allowing HTML and other resources to be transferred over TCP/IP. It is stateless, meaning each request is independent, and it can operate over TLS/SSL to become HTTPS.

2. Characteristics

Client/Server model with basic and secure authentication.

Simple and fast request methods (GET, HEAD, POST, etc.).

Flexible content transfer via the Content‑Type header.

Supports both non‑persistent (HTTP/0.9, 1.0) and persistent (HTTP/1.1) connections (keep‑alive).

Statelessness requires the client to resend any needed state.

Only client‑initiated requests; the server cannot push data without a request.

Default ports: 80 for HTTP, 443 for HTTPS.

3. Workflow

An HTTP transaction consists of four steps: (1) client establishes a TCP connection to the server; (2) client sends a request line, headers and optional body; (3) server replies with a status line, headers and optional body; (4) client receives the response and the connection is closed (or kept alive in HTTP/1.1).

4. Header Fields

Each header consists of a name, a colon and a value. Important request headers include Accept , Accept‑Charset , Accept‑Encoding , Accept‑Language , User‑Agent , Host , Cookie , Content‑Length , Content‑Type , etc. Common response headers include Location , Server , Set‑Cookie , Cache‑Control , Expires , ETag , Last‑Modified , and others.

HTTP methods defined in the protocol:

GET     – retrieve a resource (no side effects)
POST    – submit data to be processed
HEAD    – like GET but without a response body
PUT     – upload a new version of a resource
DELETE  – remove the specified resource
TRACE   – echo the received request (diagnostic)
CONNECT – change the connection to a tunnel (proxy)
OPTIONS – list the supported methods for a resource

Status line format: HTTP-Version SP Status-Code SP Reason-Phrase CRLF . Representative status codes:

1xx (Informational): 100 Continue, 101 Switching Protocols
2xx (Success): 200 OK, 201 Created, 204 No Content
3xx (Redirection): 301 Moved Permanently, 302 Found, 304 Not Modified
4xx (Client error): 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found
5xx (Server error): 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable

5. Caching Implementation

Web caches store copies of responses (HTML, images, files) and serve them for identical subsequent requests, reducing latency and bandwidth. HTTP defines freshness (Expires, max‑age), validation (ETag, If‑Modified‑Since), and invalidation mechanisms.

6. Applications

Resumable download: Uses the GET method with Range and Content‑Range headers; server returns 206 Partial Content for the requested byte range.

Multithreaded download: Multiple parallel GET requests each with a distinct byte range; results are merged locally.

HTTP proxy: Acts as an intermediary, forwarding client requests, optionally caching responses, and providing functions such as access control, anonymity and bandwidth saving.

Virtual hosting: A single web server serves multiple domain names distinguished by the Host header, allowing separate sites on the same IP address.