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.
feat: add OAuth Bearer token support to HttpClient #1168
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
base: master
Are you sure you want to change the base?
feat: add OAuth Bearer token support to HttpClient #1168
Changes from all commits
a21334b840049854c4b5e26c9fad86c51d53e0868cf649ffc384584fFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in commit 86c51d5: the constructor now throws immediately when accessToken is set alongside a non-HTTPS baseUrl. Additionally, post() was updated to fast-fail when neither accessToken nor botAccount credentials are present, and when an accessToken is available it submits XML once with Authorization: Bearer and Content-Type: application/xml, bypassing the Digest challenge loop entirely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in commit 3e0868c, which adds tests covering: (1) a caller-supplied Authorization header is not overwritten by the configured Bearer token; (2) a whitespace-only Authorization value is treated as absent and replaced with Bearer; (3) constructing MusicBrainzApi with accessToken and a non-HTTPS baseUrl throws; (4) post() sends exactly one request with the Bearer token and Content-Type: application/xml; (5) post() throws when neither accessToken nor bot credentials are configured. A follow-up commit (f649ffc) also adds the equivalent ISRC-submission tests for the Node entrypoint.