HTTP Methods Reference

Retrieves a resource without modifying server state. The most commonly used HTTP method.

Use case: Fetching a webpage, API data, or file.

Submits data to the server to create a new resource or trigger a process.

Use case: Form submission, creating a new record via API.

Replaces the entire target resource with the request payload.

Use case: Updating a user profile — replaces all fields.

Partially modifies a resource — only sends the fields that need updating.

Use case: Updating only the email of a user record.

Removes the target resource from the server.

Use case: Deleting a blog post or API record.

Same as GET but returns only headers, not the response body.

Use case: Checking if a URL exists or getting Content-Length.

Describes the communication options for the target resource. Used in CORS preflight.

Use case: CORS preflight requests.

Performs a message loop-back test along the path to the target resource.

Use case: Debugging proxy chains (rarely used, often disabled).

Establishes a tunnel to the server identified by the target resource.

Use case: HTTPS tunneling through HTTP proxies.