Commit 5be24973 authored by Nigel Kukard's avatar Nigel Kukard
Browse files

Updated PUT to say 'replace' instead of 'update'

parent cf44dbdc
......@@ -43,7 +43,7 @@ Do not expose unsafe operations via GET—it should never modify any resources o
* GET http://www.example.com/buckets/sample
## PUT
PUT is most-often utilized for **update** capabilities, PUT-ing to a known resource URI with the request body containing the newly-updated representation of the original resource.
PUT is most-often utilized for **replace** capabilities, PUT-ing to a known resource URI with the request body containing the newly-replaced representation of the original resource.
However, PUT can also be used to create a resource in the case where the resource ID is chosen by the client instead of by the server. In other words, if the PUT is to a URI that contains the value of a non-existent resource ID. Again, the request body contains a resource representation. Many feel this is convoluted and confusing. Consequently, this method of creation should be used sparingly, if at all.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment