Basics of HTTP

HTTP is an extensible protocol that relies on concepts like resources and Uniform Resource Identifiers (URIs), simple message structure, and client-server communication flow. On top of these basic concepts, numerous extensions have been developed over the years that add updated functionality and semantics with new HTTP methods or headers.

Articles

Overview of HTTP: Describes what HTTP is and its role in web architecture, including its position in the protocol stack.
Evolution of HTTP: HTTP was created in the early 1990s and has been extended several times. This article goes through its history and describes HTTP/0.9, HTTP/1.0, HTTP/1.1, and the modern HTTP/2, as well as novelties introduced over the years.
URIs: URIs are used to locate resources on the web and can be used as the targets of HTTP requests.
MIME types: Since HTTP/1.0, different types of content can be transmitted. This article explains how this is accomplished using the Content-Type header and the MIME standard.
Flow of an HTTP session: This article describes a typical HTTP session; i.e. what happens when you follow a link or load an image into a web page.
HTTP Messages: HTTP Messages transmitted during requests or responses have a very clear structure. This introductory article describes this structure, its purpose, and its possibilities.
Frame and message structure in HTTP/2: HTTP/2 encapsulates and represents HTTP/1.x messages in a binary frame. This article explains the frame structure, its purpose, and the way it's encoded.
Connection management in HTTP/1.x: HTTP/1.1 was the first version of HTTP to support persistent connection and pipelining. This article explains both concepts.
Connection management in HTTP/2: HTTP/2 completely revisited how connections are created and maintained. This article explains how HTTP frames allow multiplexing and solve the 'head-of-line' blocking problem of former HTTP versions.
Content Negotiation: HTTP introduces a set of headers, starting with Accept as a way for a browser to announce the format, language, or encoding it prefers. This article explains how this advertisement happens, how the server is expected to react, and how it chooses the most adequate response.