Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 15
    The REST camp say you should use HTTP as defined in the HTTP spec. i.e. RFC2616 Nothing more, nothing less. Commented Apr 12, 2010 at 1:12
  • 1
    @Darrel Referring ibm.com/developerworks/webservices/library/ws-restful: REST asks developers to use HTTP methods explicitly and in a way that's consistent with the protocol definition. This basic REST design principle establishes a one-to-one mapping between create, read, update, and delete (CRUD) operations and HTTP methods. According to this mapping: To create a resource on the server, use POST. To retrieve a resource, use GET. To change the state of a resource or to update it, use PUT. To remove or delete a resource, use DELETE. Commented Aug 30, 2011 at 23:11
  • 6
    Sorry but that's just plain wrong. REST requires compliance to a uniform interface. If you are using HTTP then that uniform interface is defined in part by RFC 2616. In that spec, there is not a one-to-one mapping between create, read, update, and delete and the HTTP methods. Commented Aug 31, 2011 at 0:09
  • 3
    GET and DELETE map pretty well to Read and Delete in CRUD, but using PUT/POST for Update and Create is not as straight-forward. See stackoverflow.com/questions/630453/put-vs-post-in-rest Commented Oct 12, 2011 at 22:53
  • 7
    Looking back at this 6 years later, and given that the question has been viewed ~100k times, I feel its worth putting in a small update. Darrel is correct according to Fielding's definition of REST (ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm) - there is no mention of mapping HTTP verbs to CRUD. IBM's developer advice (link in comment above) reflects common practice in implementing RESTful API's, not Fielding's definition of REST. Commented Feb 22, 2015 at 1:14