drop X-Requested-With header from the default $http config #1004

IgorMinar opened this Issue May 31, 2012 · 24 comments


None yet

IgorMinar commented May 31, 2012

X-Requested-With causes CORS requests to trigger preflight checks which complicates things for many simple things.

The header is not very useful except for certain edge-cases (e.g. I think that Rails uses the header to switch full page and page fragment rendering).


IgorMinar commented Jun 11, 2012

better then completely dropping the header would be to send it only for same-domain requests. this will require moving the header from the default header config into a filter or something similar.

zvictor commented Jun 11, 2012

I agree, I was having the same problem and I had to change server headers.

AshD commented Aug 28, 2012


vitch commented Sep 14, 2012


olragon commented Sep 17, 2012



escalant3 commented Sep 18, 2012



rkirov commented Sep 28, 2012

I had a chat with Misko about this. It might be easier to completely remove this header and let people add it on demand. Otherwise we would need to keep two sets of default headers - headers.common and headers.commonCrossDomain, which would add more complexity and documentation.


IgorMinar commented Oct 12, 2012

Let's just remove it as it makes the documentation and expectations easier to manage. Adding the header to the defaults is trivial.


rkirov commented Oct 12, 2012

For the record, here is the snippet to reenable the previous behavior that Igor mentioned:

myModule.config(function($httpProvider) {
  $httpProvider.defaults.headers.common['X-Requested-With'] = 'XMLHttpRequest';

taralx commented Nov 13, 2012


tchatel commented Nov 17, 2012

Since a few days, with this header all CORS requests to Google APIs fail, causing an "Origin [...] is not allowed by Access-Control-Allow-Origin" error.

You can see the error in Vojta's Task Manager : http://task-manager-angular.appspot.com/app/index.html
It it does no longer work, as any AngularJS application making $http requests to Google APIs.

+1 to only sending for same-domain requests. -1 to removing it.

IgorMinar closed this in 3a75b11 Nov 26, 2012

I realize that this header can be added back and that it's just being removed by default, but there are some good reasons everyone might want to use it: for some basic CSRF protection: https://nealpoole.com/blog/2010/11/preventing-csrf-attacks-with-ajax-and-http-headers/#comment-1675

Are you using something different for CSRF protection?


rkirov commented Dec 7, 2012

Yes, Angular provides X-XSRF-TOKEN specifically for that purpose (see http://docs.angularjs.org/api/ng.$http). It will require some collaboration from your server, but it is a more robust solution.

hakisa-jerome referenced this issue in mnot/hinclude Mar 29, 2013


Add X-Requested-With header #16

I just updated to version 1.1.4 and my Angular app does not work with my Rails backend anymore.
There are more people with this issue as you can see on this stackoverflow question.

Dropping this header is really the right thing to do?

NickClark referenced this issue in hiravgandhi/angularjs-rails Jun 12, 2013


Angularjs 1.1.5 doesn't work for me #16

gwright commented Jun 23, 2013

I added some more background on the Rails interaction in this comment.


eddiemonge commented Aug 23, 2013

seems removing this has caused some problems. the docs should at least state that this was removed as the default. only way i found this was the cause of my api requests failing is that i examined the request in detail, with old and updated ngcore code.

janmarek commented Oct 1, 2013

Nette Framework also uses this header.

kromped commented Oct 1, 2013

@eddiemonge I agree with you. I spent hours trying to debug what happened to the httpProvider because it was not working. Turns out they removed the default http headers and I had to search the change log to see why they removed it. Please update the docs!

Django also uses this in it's request.is_ajax() method. IMO the better solution is what jquery does. Yes, it is simple to add that single line but identifying the problem as 'X-Requested-With' may not be so easy for some people. I personally found it pretty easy, but I enjoy tracing through my (and everyone elses) code with the debugger ;)

this is quite weird for me, as many cases Backend, use is_xhr, or is_ajax etc to check whether user is made requests from browser with ajax, or not.

Symfony2 2.3.x also can't detect if the request is XHR without this header


gkalpak commented Aug 17, 2016

Fortunately, anyone is free to add this header to the default headers sent with every request 😄

butonic referenced this issue in owncloud/core Jan 12, 2017


IE11 caches AJAX requests #26922

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment