Core Concepts and Principles of HTTP Requests

1. Core Concepts of HTTP Requests

URL (Uniform Resource Locator) identifies the location of a resource on a server and includes protocol, host, port, path, and query parameters.

Request Method defines the operation to perform; common methods are GET (retrieve), POST (submit), PUT (update), and DELETE (remove).

Request Header carries metadata such as User-Agent and Content-Type.

Request Body contains data sent to the server, typically empty for GET and used for POST/PUT to transmit form data or JSON.

Response Status Code indicates the result of the request; examples include 200 (success), 404 (not found), and 500 (server error).

Response Header provides metadata like Content-Type and Content-Length.

Response Body holds the returned data (HTML, JSON, XML, etc.) parsed according to the Content-Type.

2. Detailed Principles of HTTP Requests

Client establishes a TCP connection with the server using a three‑way handshake to ensure reliable transmission.

Client sends the request line and headers, specifying the method, resource path, and HTTP version.

The server processes the request based on the method and path, generates an appropriate response, and sends back the status code, headers, and body.

After the response, the TCP connection may be closed or kept alive for subsequent requests (HTTP/1.1 persistent connections).

3. Common HTTP Methods and Their Characteristics

GET : Retrieves resources; request body is empty; safe and idempotent. Example: GET /api/v1/users HTTP/1.1

POST : Submits data; includes a request body; not safe, not idempotent. Example: POST /api/v1/users HTTP/1.1

PUT : Updates resources; includes a request body; idempotent. Example: PUT /api/v1/users/123 HTTP/1.1

DELETE : Deletes resources; request body optional; idempotent. Example: DELETE /api/v1/users/123 HTTP/1.1

4. Status Code Classification

1xx – Informational : Request received, processing not yet complete.

2xx – Success : Request successfully processed (e.g., 200 OK).

3xx – Redirection : Further action needed to complete the request (e.g., 302 Found).

4xx – Client Error : Invalid request from the client (e.g., 404 Not Found).

5xx – Server Error : Server failed to fulfill a valid request (e.g., 500 Internal Server Error).

Conclusion

Understanding HTTP’s core concepts, request‑response workflow, methods, and status codes is essential for backend development and effective API testing.