-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-standard X-Requested-With
should be opt-in not opt-out
#3273
Comments
Here is where it was decided to remove this erroneous header from Angular back in 2012: angular/angular.js#1004 |
A more recent take on this issue in Angular's issues: angular/angular.js#11008 (comment) |
BREAKING CHANGE: will no longer execute a CORS request by default, you must opt-in with the `crossDomain` flag in the config. closes #3273
@benlesh -- This could be a breaking change for some people that are using the |
@benlesh -- Isn't the "BREAKING CHANGE" notice in your second commit stating things backwards? It will now execute a CORS request by default, it will no longer execute an X-Requested-With request by default. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
X-Requested-With
is a non-standard header that isn't called for by the XMLHttpRequest living standard.This header should be presented only on an opt-in basis. Ajax requests should not come with this header by default.
The text was updated successfully, but these errors were encountered: