HTTP methods are defined to indicate the desired action to be performed on the identified resource. Often, the resource corresponds to a file or the output of an executable residing on the server.
HTTP/1.1 specification defines the following methods.
1) CONNECT
2) DELETE
3) GET
4) HEAD
5) OPTIONS
6) PATCH
7) POST
8) PUT
9) TRACE
1) CONNECT
Converts the request connection to a transparent TCP/IP tunnel, usually to facilitate SSL-encrypted communication (HTTPS) through an unencrypted HTTP proxy.
2) DELETE
Deletes the specified resource.
3) GET
Requests a representation of the specified resource. Requests using GET should only retrieve data and should have no other effect.
4) HEAD
Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content.
5) OPTIONS
Returns the HTTP methods that the server supports for specified URL. This can be used to check the functionality of a web server by requesting ” * ” instead of a specific resource.
6) PATCH
Is used to apply partial modifications to a resource.
7) POST
Requests that the server accept the entity enclosed in the request as a new subordinate of the web resource identified by the URI. The data POSTed might be, as examples, an annotation for existing resources; a message for a bulletin board, newsgroup, mailing list, or comment thread; a block of data that is the result of submitting a web form to a data-handling process; or an item to add to a database.
8) PUT
Requests that the enclosed entity be stored under the supplied URI. If the URI refers to an already existing resource, it is modified; if the URI does not point to an existing resource, then the server can create the resource with that URI.
9) TRACE
Echoes back the received request so that a client can see what (if any) changes or additions have been made by intermediate servers.
