| 1 | GET | Request the specified page information and return the entity body. |
| 2 | HEAD | Similar to a GET request, but the response does not include the actual content—used to retrieve headers only. |
| 3 | POST | Submits data to the specified resource for processing (e.g., form submission or file upload). The data is included in the request body. A POST request may result in the creation of new resources and/or modification of existing ones. |
| 4 | PUT | Data transmitted from the client to the server replaces the content of the specified document. |
| 5 | DELETE | Request the server to delete the specified page. |
| 6 | CONNECT | Reserved in HTTP/1.1 for proxies that can switch the connection to pipelining mode. |
| 7 | OPTIONS | "Allows the client to view the server's performance. |
| 8 | TRACE | "Echoes the request received by the server, primarily used for testing or diagnostics. |
| 9 | PATCH | "The entity contains a table that describes the differences between the content represented by this URI and the original content. |
| 10 | MOVE | Instruct the server to redirect the specified page to a new network address. |
| 11 | COPY | Instruct the server to replicate the specified page to a different network address. |
| 12 | LINK | Instruct the server to create a connection between the entities. |
| 13 | UNLINK | Terminate the association between the linked entities. |
| 14 | WRAPPED | Permit clients to transmit requests in an encapsulated format. |
| 15 | Extension-mothed | The protocol remains unchanged, but an alternative approach may be introduced. |
