I have a Collection that needs to POST some data to its url to get the data it needs. The answer to these two questions, Fetch a collection using a POST request? and Overriding fetch() method in backbone model, make it seem like I should be able to get it to work like this:
fetch: function( options ) {
this.constructor.__super__.fetch.apply(this, _.extend(options,{data: {whatever: 42}, type: 'POST'}));
}
, but Firebug still shows me a 404 error that is happening because a GET is being executed against the url in question (and the underlying Rails route only allows POST). Should this be working? If so, what else might I try? If not, what have I done wrong?
I have a Collection that needs to POST some data to its url to get the data it needs. The answer to these two questions, Fetch a collection using a POST request? and Overriding fetch() method in backbone model, make it seem like I should be able to get it to work like this:
fetch: function( options ) {
this.constructor.__super__.fetch.apply(this, _.extend(options,{data: {whatever: 42}, type: 'POST'}));
}
, but Firebug still shows me a 404 error that is happening because a GET is being executed against the url in question (and the underlying Rails route only allows POST). Should this be working? If so, what else might I try? If not, what have I done wrong?
Share Improve this question edited May 23, 2017 at 11:46 CommunityBot 11 silver badge asked Mar 11, 2013 at 22:32 cbmanicacbmanica 3,8697 gold badges39 silver badges59 bronze badges 5-
Have you considered overriding Backbone's
syncorajaxmethods? – mu is too short Commented Mar 11, 2013 at 22:48 - I would, if 1) I could figure out how, and 2) I could be convinced that overriding all of sync (which sounds hard and involved), was necessary because overriding fetch (which seems like it should be easy) has no chance of working. – cbmanica Commented Mar 11, 2013 at 22:55
-
1
Incidentally, the actual answer is that one of the posts I linked to didn't make it clear that the second argument to
applyhas to be an array. D'oh. – cbmanica Commented Mar 13, 2013 at 22:36 -
Right, I missed that! I always get the
callandapplysignatures mixed up. – mu is too short Commented Mar 14, 2013 at 0:49 - Possible duplicate of What is the least ugly way to force Backbone.sync updates to use POST instead of PUT? – Emile Bergeron Commented Dec 12, 2016 at 2:13
1 Answer
Reset to default 16After reading the question again, here's a way to force the fetch to use POST per fetch call. (Thanks for the ments)
yourCollection.fetch({
data: $.param({id: 1234}),
type: 'POST',
success: function(d){
console.log('success');
}
});
Another approach is to override the AJAX implementation itself to use POST for all calls.
Backbone.ajax = function() {
var args = Array.prototype.slice.call(arguments, 0);
_.extend(args[0], { type: 'POST' });
return Backbone.$.ajax.apply(Backbone.$, args);
};