Skip to content
This repository has been archived by the owner on Nov 21, 2019. It is now read-only.

CORS error is misinterpreted and not handled correctly #2005

Open
alonbg opened this issue Aug 13, 2018 · 0 comments
Open

CORS error is misinterpreted and not handled correctly #2005

alonbg opened this issue Aug 13, 2018 · 0 comments

Comments

@alonbg
Copy link

alonbg commented Aug 13, 2018

Browser <-> nginx proxy <-> Private blockchain Parity 1.11.8

Parity is set with --jsonrpc-cors all

Chrome asks for Access-Control-Request-Headers: authorization,content-type
but Authorization was not included in the Access-Control-Allow-Headers response header

Chrome's console:

Access to XMLHttpRequest at 'https://<***********> from origin 'https://www.myetherwallet.com' has been blocked by CORS policy: Request header field Authorization is not allowed by Access-Control-Allow-Headers in preflight response.

etherwallet-master.js:53478 TypeError: _callbacks[i] is not a function
    at etherwallet-master.js:16182
    at etherwallet-master.js:16202
    at processQueue (etherwallet-master.js:55807)
    at etherwallet-master.js:55856
    at Scope.$digest (etherwallet-master.js:56965)
    at Scope.$apply (etherwallet-master.js:57254)
    at done (etherwallet-master.js:51352)
    at completeRequest (etherwallet-master.js:51588)
    at XMLHttpRequest.requestError (etherwallet-master.js:51517) "Possibly unhandled rejection: {}"
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant