Home/ Questions/Q 8434567
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T06:41:31+00:00

I’ve never used PUT or DELETE HTTP Request methods. My tendency is to use

  • 0

I’ve never used PUT or DELETE HTTP Request methods. My tendency is to use GET when the state of the system (my application or website) may not be affected (like a product listing) and to use POST when it is affected (like placing an order). Aren’t those two always sufficient, or am I missing something?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    DELETE is for deleting the request resource:

    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 client cannot be guaranteed that the operation has been carried out, even if the status code returned from the origin server indicates that the action has been completed successfully …

    PUT is for putting or updating a resource on the server:

    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. If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create the resource with that URI …

    For the full specification visit:

    Since current browsers unfortunately do not support any other verbs than POST and GET in HTML forms, you usually cannot utilize HTTP to it’s full extent with them (you can still hijack their submission via JavaScript though). The absence of support for these methods in HTML forms led to URIs containing verbs, like for instance 

    POST http://example.com/order/1/delete

    or even worse

    POST http://example.com/deleteOrder/id/1

    effectively tunneling CRUD semantics over HTTP. But verbs were never meant to be part of the URI. Instead HTTP already provides the mechanism and semantics to CRUD a Resource (e.g. an order) through the HTTP methods. HTTP is a protocol and not just some data tunneling service.

    So to delete a Resource on the webserver, you’d call 

    DELETE http://example.com/order/1

    and to update it you’d call

    PUT http://example.com/order/1

    and provide the updated Resource Representation in the PUT body for the webserver to apply then.

    So, if you are building some sort of client for a REST API, you will likely make it send PUT and DELETE requests. This could be a client built inside a browser, e.g. sending requests via JavaScript or it could be some tool running on a server, etc.

    For some more details visit:

    • 0