Skip to content
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

Bearer token doesn’t work with CORS when only authorization header is allowed #353

Closed
mhusar opened this issue Nov 27, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@mhusar
Copy link

mhusar commented Nov 27, 2019

Version: commit 37c4108

When I use the "Authentication" tab and choose "Bearer Token" as authentication type and define a token, the "Access-Control-Request-Headers" header is faulty.

current:
Access-Control-Request-Headers: authorization,undefined
should be:
Access-Control-Request-Headers: authorization

But on the server-side I defined, that only the authorization header is allowed:
Access-Control-Allow-Headers: authorization

When I define the "Authorization" header directly in the "Headers" tab, there is no problem. Reproducable with Firefox (Nightly) and Chrome (76).

@liyasthomas
Copy link
Member

Issue has been identified. Let us investigate what went wrong and get back to you in a jiffy.

@liyasthomas liyasthomas added the bug Something isn't working label Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants