There are 15 HTTP request methods (HTTP Request Method). According to the HTTP standard, an HTTP request can use several methods. HTTP1.0 defined three request methods: GET, POST and HEAD. HTTP1.1 added five request methods: OPTIONS, PUT, DELETE, TRACE and CONNECT.
| Index | Method | Description |
|---|---|---|
| 1 | GET | Requests the specified page information and returns the entity body. |
| 2 | HEAD | Similar to a get request, but the response returned contains no body; used to retrieve headers |
| 3 | POST | Submits data to the specified resource for processing (for example, submitting a form or uploading a file). The data is contained in the request body. POST requests may result in the creation of new resources and/or the modification of existing resources. |
| 4 | PUT | The data sent from the client to the server replaces the contents of the specified document. |
| 5 | DELETE | Ask the server to delete the specified page. |
| 6 | CONNECT | Reserved in HTTP/1.1 for proxy servers that can change a connection to pipelined mode. |
| 7 | OPTIONS | Allow the client to view server performance. |
| 8 | TRACE | Echoes back the request the server received, mainly for testing or diagnostics. |
| 9 | PATCH | The entity contains a table describing the difference from the original content at this URI. |
| 10 | MOVE | Requests the server to move the specified page to another network address. |
| 11 | COPY | Requests the server to copy the specified page to another network address. |
| 12 | LINK | Requests the server to establish a connection. |
| 13 | UNLINK | Unlink. |
| 14 | WRAPPED | Allow the client to send wrapped requests. |
| 15 | Extension-mothed | Additional methods can be added without modifying the protocol. |
This tool belongs to the “Reference tables” category.
Your input is processed locally in the browser whenever possible. We do not store it.
Some lookups expose a JSON endpoint; the full list is on the Network Tools → API reference page.
Specifications evolve. These pages list the common entries and note the last update — report anything wrong.
We keep the high-frequency entries to hold page weight and load time down.