JavaScript Web Concepts, Part4 - HTTP Request, Components and Methods

What is HTTP request?

An HTTP request is a message sent by a client (usually a web browser or an application) to a server to request specific information or resources over the internet. The client initiates communication by sending this request to the server, which then processes it and returns an HTTP response with the requested data or an indication of the action's result.

Components of an HTTP Request

1. Request Line: The first line of an HTTP request that specifies:
2. Method: The HTTP method, indicating the action to be performed (e.g., GET, POST, PUT, DELETE).
3. URI (Uniform Resource Identifier): The path or location of the resource on the server (e.g., /index.html).
4. HTTP Version: The version of HTTP being used (e.g., HTTP/1.1, HTTP/2).
• Example: GET /index.html HTTP/1.1
5. Headers: Key-value pairs that provide additional information about the request, such as client details, accepted content types, and authentication data.
6. Host: Specifies the domain name of the server (e.g., Host: www.example.com).
7. User-Agent: Provides information about the client application (e.g., browser type and version).
8. Accept: Specifies the media types the client can handle, like text/html or application/json.
9. Body (Optional): Contains data sent to the server, typically included in methods like POST, PUT, or PATCH, where data needs to be submitted or updated. The body might contain form data, JSON, XML, or other types of content.

Common HTTP Methods

The method in the request line specifies the action the client wants the server to perform:

1. GET: Requests a resource from the server; used primarily for retrieving data.
2. POST: Sends data to the server to create a new resource.
3. PUT: Updates an existing resource on the server.
4. DELETE: Requests the deletion of a specified resource.
5. PATCH: Partially updates an existing resource.
6. OPTIONS: Requests information about the communication options available for the target resource.

Example of a Full HTTP Request

GET /index.html HTTP/1.1

Host: www.example.com

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)

Accept: text/html

How an HTTP Request Works

1. Client Initiation: The client creates an HTTP request and sends it to the server.
2. Server Processing: The server receives the request, interprets it, and performs the required action.
3. Response Generation: The server generates an HTTP response based on the request, which includes the requested resource (if applicable) and status information.
4. Response Delivery: The server sends the response back to the client, completing the request-response cycle.

HTTP requests are the foundation of web communication, allowing clients to interact with servers to retrieve resources, submit data, or control actions.

What is HTTP request verb?

An HTTP request verb (also known as an HTTP method) is an instruction that specifies the type of action a client wants the server to perform on a given resource. HTTP verbs are fundamental to the request-response cycle in the HTTP protocol, indicating what operation is being requested by the client. Here are the most commonly used HTTP request verbs:

Common HTTP Verbs and Their Functions

GET

• Purpose: Retrieve data from a server at a specific resource URL.
• Characteristics: Safe, idempotent (does not modify data), can be cached.
• Example: Retrieving a webpage (GET /home).

POST

• Purpose: Send data to the server to create a new resource.
• Characteristics: Not idempotent (repeating a request can create multiple resources), often used in form submissions.
• Example: Submitting a form (POST /submit).

PUT

• Purpose: Update an existing resource or create it if it doesn’t exist.
• Characteristics: Idempotent (repeating the request has the same effect as a single request).
• Example: Updating a user profile (PUT /user/123).

DELETE

• Purpose: Remove a specified resource on the server.
• Characteristics: Idempotent, usually results in the deletion of data.
• Example: Deleting a post (DELETE /post/123).

PATCH

• Purpose: Partially update a resource (only certain fields, rather than the entire resource).
• Characteristics: Not always idempotent; useful for making incremental changes.
• Example: Updating a user's email only (PATCH /user/123).

OPTIONS

• Purpose: Request information about the communication options available for the target resource.
• Characteristics: Often used for CORS (Cross-Origin Resource Sharing) preflight requests to see which HTTP methods are allowed.
• Example: Checking options for /api/resource (OPTIONS /api/resource).

HEAD

• Purpose: Same as GET but without the response body; used to fetch metadata.
• Characteristics: Often used to check if a resource exists or to get headers before making a GET request.
• Example: Checking headers (HEAD /home).

Summary

HTTP verbs define the actions in a RESTful API and specify what the client is asking the server to do with a resource. These verbs help determine how data is created, read, updated, or deleted, guiding the server’s response and ensuring clear communication between client and server.

Related Post JavaScript Web Concept Part5