Backbone.save POST instead of PUT

Question

just a short question:

Having the new instance of a model and issuing a model.save() with URL set to /api/store/category, Backbone issues a POST. According to my knowledge, it should use PUT, like mentioned in this "PUT or POST: The REST of the Story" blog post.

Who is right? BB or this article's author?

score 13 · Accepted Answer · edited May 23 '17 at 11:53

13

According to Backbone documentation, saving a new model will result in a POST request, and saving an existing model (having an id) will emit a PUT request.

save model.save([attributes], [options])
...
If the model isNew, the save will be a "create" (HTTP POST), if the model already exists on the server, the save will be an "update" (HTTP PUT).

And if you are wondering if Backbone should use a POST for creation, check

PUT vs POST in REST
RESTful web services on Wikipedia

In the light of these articles, I'd say that, in the context of Backbone, the verbs are correctly used:

saving a new model causes a change in the system, a new URL is added, the action is not idempotent, it should be a POST,
saving a known model replaces a resource at a given URL, the action is idempotent, it should be a PUT.

edited May 23 '17 at 11:53

Community

1
1

answered Jun 13 '12 at 10:39

nikoshr

32,926
33
91
105

1

Right, so in the response to the post request you should send newly created id back. – Yaroslav Jun 13 '12 at 11:45
Thanks, I already knew that. Maybe my question was a bit inaccurate. I was wondering if backbone is off-standard ;-) – Jannick Jun 13 '12 at 12:54
@Jan I modified my answer to answer the choice of POST/PUT – nikoshr Jun 13 '12 at 13:25

Backbone.save POST instead of PUT

1 Answers1

Linked