#Put it to rest synonym update#
You can use this to create, but also to update something, as long as you're sending a complete representation. In either case, it completely ignores whatever is in there. It creates the new file at the destination if it doesn't exist, or replaces whatever exists. A good analogy is the mv command in a shell. This is a convention adopted by some frameworks, but it has nothing to do with REST constraints.Ī PUT request asks the server to replace whatever is at the given URI with the enclosed representation, completely ignoring the current contents. There's no strict correspondence between HTTP methods and CRUD. One might want to POST their message to a message board, and then PUT additional content into their message at a later date. I believe the nomenclature goes back a long ways, consider the early web. I usually look at POST as it should be the URI that will handle the content of my request (in most cases the params as form values) and thus creating a new resource, and PUT as the URI which is the subject of my request (/users/1234), a resource which already exists. I do see where you are coming from based on the names themselves however. Server MUST NOT attempt to apply the request to some other resource. The request - the user agent knows what URI is intended and the InĬontrast, the URI in a PUT request identifies the entity enclosed with Some other protocol, or a separate entity that accepts annotations. That resource might be a data-accepting process, a gateway to POST request identifies the resource that will handle the enclosedĮntity. Reflected in the different meaning of the Request-URI.
The fundamental difference between the POST and PUT requests is The difference is that a PUT is for a known resource, and therefor used for updating, as stated here in rfc2616.
0 kommentar(er)
