You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 30, 2018. It is now read-only.
While it is helpful to have xhr set the header X-Requested-With as it is a common case for CORS that fails because the end user doesn't know it is often required, if the server you are facing off doesn't allow the header to be specified in the OPTIONS preflight in that is performed in Chromium based browsers, the request fails with the message Request header field X-Requested-With is not allowed by Access-Control-Allow-Headers in preflight response. and there is no way to turn the header off.
Package Version: beta1
The text was updated successfully, but these errors were encountered:
* Adding a flag to disable automatic inclusion of the x-requested-with header, issue #328
* Documenting request options
* Busting IE cache for failed test, issue #328
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug
While it is helpful to have
xhr
set the headerX-Requested-With
as it is a common case for CORS that fails because the end user doesn't know it is often required, if the server you are facing off doesn't allow the header to be specified in theOPTIONS
preflight in that is performed in Chromium based browsers, the request fails with the messageRequest header field X-Requested-With is not allowed by Access-Control-Allow-Headers in preflight response.
and there is no way to turn the header off.Package Version: beta1
The text was updated successfully, but these errors were encountered: