Remove X-Requested-With

[gaearon]

There is no API to “undo” setting request headers on XHR so it really should be up to the client to specify this (or any other) header.

[akre54]

Cool. There seems to be good precedent here: angular/angular.js@3a75b11.

Do we not need to handle the cross-domain logic jQuery has to mess with?

[gaearon]

In my opinion if someone deems it necessary, they will have no trouble adding it in options.
It is only useful if you check for its presence on server to guard against CSRF. I'm not sure if any popular web frameworks do this automatically (they may), and if you do this check on your own, you might as well specify the header when calling NativeAjax.

[gaearon]

BTW thanks for the repo. I finally got around to dropping jQuery dependency in our codebase and thanks to Backbone.NativeView and Backbone.NativeAjax I actually made it through, in just one day. I tried to do this twice before but to gave up; these drop-in replacements saved much of the hassle.

[gaearon]

Allowing to use a custom Deferred is also a classy touch.

[akre54]

Rails uses it for request.xhr?. I'd rather not break peoples' apps who are relying on this one line, but I think it should be fine in this case. I'll make sure to document it in the breaking changes.

angular/angular.js#1004
https://groups.google.com/forum/#!topic/angular/gLh3tBg5lhc

[akre54]

And thanks, glad you like it. The Deferred stuff is all Paul's doing, but there was a proposal to add Backbone.Deferred to Backbone proper a little while back in jashkenas/backbone#2489. Maybe it'll have some more support now that Promises have landed in browsers.