How is the HTTP protocol structured?

HTTP (Hypertext Transfer Protocol) is an application layer protocol used for transferring data, such as web pages. It operates on a "client-server" model.

The client (usually a browser) sends a request to the server, and the server processes the request and sends a response back to the client.

Main elements of an HTTP message:

Start line: Defines the message type (request or response) and main parameters.
- Request: Method (GET, POST, PUT, DELETE, etc.), resource path, protocol version.
- Response: Protocol version, status code (200 OK, 404 Not Found, 500 Internal Server Error, etc.), status text.
```
GET /index.html HTTP/1.1 // Example of a request start line
```
```
HTTP/1.1 200 OK // Example of a response start line
```
Headers: Contain metadata about the message and the message body. Each header is represented as "HeaderName: Value".
- Request headers: Host, User-Agent, Accept, Content-Type, Content-Length, etc.
- Response headers: Content-Type, Content-Length, Server, Set-Cookie, etc.
```
Host: example.com // Example of Host header
User-Agent: Mozilla/5.0 // Example of User-Agent header
```
Blank line: Separates headers from the message body.
Message body: Contains the transmitted data. It may be absent in some requests (e.g., GET) and responses (e.g., 204 No Content). In POST or PUT requests, the body usually contains the data being sent. In responses, the body contains the requested resource (e.g., HTML code, images, JSON).
```
<!DOCTYPE html>
<html>
<head>
    <title>Example</title>
</head>
<body>
    <h1>Hello!</h1>
</body>
</html>
```

Main HTTP methods:

Method	Description	Usage
GET	Requests a resource at the specified URL.	Retrieving data without changing server state.
POST	Sends data to be processed on the server.	Submitting forms, uploading files, creating resources.
PUT	Updates or creates a resource at the URL.	Updating existing resources.
DELETE	Deletes the resource at the URL.	Removing resources.
HEAD	Requests headers of a resource without its body.	Getting meta-information about the resource.

HTTP is a stateless protocol. Each request is independent. Mechanisms like cookies and sessions are used to maintain state.