Skip to content
This repository has been archived by the owner on Jul 30, 2018. It is now read-only.

request provider always sets X-Requested-With #328

Closed
kitsonk opened this issue Apr 29, 2017 · 0 comments
Closed

request provider always sets X-Requested-With #328

kitsonk opened this issue Apr 29, 2017 · 0 comments
Assignees
Milestone

Comments

@kitsonk
Copy link
Member

kitsonk commented Apr 29, 2017

Bug

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

@kitsonk kitsonk added the bug label Apr 29, 2017
@dylans dylans added this to the 2017.05 milestone May 5, 2017
@eheasley eheasley modified the milestones: 2017.05, 2017.06 Jun 6, 2017
@dylans dylans modified the milestones: 2017.06, 2017.07 Jul 4, 2017
@kitsonk kitsonk added the beta3 label Jul 27, 2017
@kitsonk kitsonk modified the milestones: 2017.08, 2017.07 Jul 27, 2017
rorticus added a commit to rorticus/core that referenced this issue Jul 31, 2017
rorticus added a commit to rorticus/core that referenced this issue Aug 1, 2017
rorticus added a commit that referenced this issue Aug 1, 2017
* 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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants