HTTP (Hypertext Transfer Protocol) defines several request methods or verbs that indicate the desired action to be performed on a resource located on a web server.
Each request method has a specific purpose and behavior.
See the below Request Methods and its causes.

Request Method



  • Requests data from the server.
  • Retrieves information from the server, typically using query parameters in the URL.
  • Should not have any side effects on the server (i.e., it should be safe and idempotent).
  • Can be cached by browsers and intermediary servers.


  • Submits data to be processed to a specified resource.
  • Commonly used to send data to the server, such as form submissions or data uploads.
  • Can have side effects on the server, like creating or updating resources.
  • Should not be used for idempotent operations.


  • Replaces the target resource with the request payload.
  • Used to update or create a resource at the specified URL.
  • The entire resource is replaced, so missing data in the payload may lead to data loss.
  • Often used for updating resources, but it can also create new resources when the URL uniquely identifies the resource.


  • Partially updates the target resource.
  • Used to apply partial modifications to a resource, sending only the changes to be applied.
  • Suitable for updating specific fields of a resource without replacing the entire resource.
  • More efficient than PUT when updating small portions of large resources.


  • Deletes the specified resource on the server.
  • Used to remove a resource from the server permanently.
  • Be cautious when using this method, as data deletion is irreversible.


  • Requests the headers of a resource without retrieving the actual content.
  • Used to check the status and metadata of a resource without transferring the data.
  • Useful for validating resource existence and caching purposes.


  • Requests information about the communication options available for a resource.
  • Used to check the allowed methods, supported headers, or capabilities of a server.
  • Helpful for cross-origin requests and preflight requests.


  • Establishes a network connection to the target resource, usually for proxy purposes.
  • Rarely used directly by web developers but is critical for HTTP proxies and tunneling.


  • Echoes back the received request for diagnostic purposes.
  • Allows a client to see what intermediate servers are changing in the request.
  • Rarely used in practice and may be disabled on some servers due to security concerns.

Quick Recap - Topics Covered


Practice With Examples in Compilers

The Concepts and codes you leart practice in Compilers till you are confident of doing on your own. A Various methods of examples, concepts, codes availble in our websites. Don't know where to start Down some code examples are given for this page topic use the code and compile or Try on own Now

Example 1
Example 1 Example 2 Example 3 Example 4 Example 5