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.
Bug
While it is helpful to have
xhrset the headerX-Requested-Withas 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 theOPTIONSpreflight 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