HTTP Methods
HTTP methods define the action a client wants to perform on a resource. Each method has defined semantics for safety, idempotency, and cacheability. Defined in RFC 9110 §9.
| Method | Description | Safe | Idempotent | Cacheable | Body | Spec |
|---|---|---|---|---|---|---|
| GET | GET retrieves a representation of the specified resource. | Yes | Yes | Yes | No / Yes | RFC 9110 |
| POST | POST submits data to create a resource or trigger an action. | No | No | No | Yes / Yes | RFC 9110 |
| PUT | PUT replaces a resource entirely with the supplied representation. | No | Yes | No | Yes / No | RFC 9110 |
| PATCH | PATCH applies partial modifications to a resource. | No | No | No | Yes / Yes | RFC 5789 |
| DELETE | DELETE removes the specified resource. | No | Yes | No | No / No | RFC 9110 |
| HEAD | HEAD is identical to GET but the server returns only headers, not the response body. | Yes | Yes | Yes | No / No | RFC 9110 |
| OPTIONS | OPTIONS describes the communication options for the target resource. | Yes | Yes | No | No / Yes | RFC 9110 |
| TRACE | TRACE performs a message loop-back test along the path to the target resource. | Yes | Yes | No | No / Yes | RFC 9110 |
| CONNECT | CONNECT establishes a TCP tunnel through an HTTP proxy to a target host and port. | No | No | No | No / No | RFC 9110 |
| QUERY | QUERY is a safe, idempotent HTTP method that carries a request body describing the query to perform. | Yes | Yes | Yes | Yes / Yes | RFC 10008 |
Body column shows Request Body / Response Body availability.