Replace 'BEARER' with 'Bearer' everywhere for RFC6750 compliance. #2783
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RFC6750 indicates that the correct header format is 'Bearer <token>', not 'BEARER <token>'.
|
@GriffinSchneider thanks for the PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The OAuth spec says that the correct format is
Bearer <token>, notBEARER <token>. My server using node-oauth2-server was rejecting my request without this fix.It looks like the only place
BEARERwas in actual code wasmodules/swagger-codegen/src/main/resources/objc/Configuration-body.mustache. I experienced the issue in ObjC.This pullreq was created by running
and then ignoring all the whitespace-only changes that generates.