Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Headers in lowercase, including bearer
See original GitHub issue| Q | A |
|---|---|
| Bug or feature request? | Bug |
| Which Swagger/OpenAPI version? | 2.0 |
| Which Swagger-UI version? | 3.1.5 |
| How did you install Swagger-UI? | download of dist folder |
| Which broswer & version? | Chrome Version 60.0.3112.90 (Official Build) (64-bit) |
| Which operating system? | Mac OS 10.12.6 |
Demonstration API definition
API with OAuth2 support
Configuration (browser query string, constructor, config.yaml)
Defaults
Expected Behavior
I authorized swagger-ui using the default settings, against my OAuth 2 server, with the “implicit” grant.
When using “try it out”, it sends the following headers:
-H "accept: application/json" -H "authorization: bearer ..."
At least the “bearer” part of this should be uppercase: https://tools.ietf.org/html/rfc6750
Also, I think it’s more standard to send title-case headers, although they’re technically case-insensitive.
Current Behavior
“bearer” is lowercase.
Possible Solution
Context
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
When it comes to the value of a header, we should never change the lettering case.
This was just fixed in https://github.com/swagger-api/swagger-js/pull/1156. Swagger-UI will receive the patch as part of our release this Friday 🎉
Closing!