mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #353] Bearer token doesn’t work with CORS when only authorization header is allowed #130
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#130
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mhusar on GitHub (Nov 27, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/353
Version: commit
37c41086d2When 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 commented on GitHub (Nov 27, 2019):
Issue has been identified. Let us investigate what went wrong and get back to you in a jiffy.