Home Education Computer Education Learn About Seven HTTP Request Methods And Its Working

Learn About Seven HTTP Request Methods And Its Working


HTTP Request Methods List

There Are about seven HTTP Request Methods according W3.org . These seven methods are as follows

  • GET
  • POST
  • HEAD
  • PUT


The OPTIONS method represents a request for information about the communication options .

available on the request/response chain identified by the Request-URI .

This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a web server, without implying a resource action or initiating a resource retrieval.

Responses to this method are not cacheable.


The GET method means retrieve identified information by the Request-URI.

This Request-URI pass a matter for decision to a data-producing process . It is the produced data which shall be returned as the entity .It is not the source text of the process .


The POST method is used to request that the web server accept the entity enclosed in the request as a new lower in rank of the resource identified by the Request-URI in the Request-Line.

POST is designed to allow a uniform method to cover the following functions:


The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request SHOULD be identical to the information sent in response to a GET request.


The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server.


The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method MAY be overridden by human intervention (or other means) on the origin server.


The TRACE method is used to invoke a remote, application-layer loop- back of the request message. The final recipient of the request SHOULD reflect the message received back to the client as the entity-body of a 200 (OK) response. The final recipient is either the


This specification reserves the method name CONNECT for use with a proxy that can dynamically switch to being a tunnel