fix: Explicitly declare accpet type to json when exchanging oauth token #801
+1
−0
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.
When exchanging OAuth token, explicitly declare the accept type to JSON as it's potentially indicated
Motivation and Context
When using official github mcp server, the default response is not a valid json and causes json parse error. (Returned something like
access_token=[some token]&scope=[some scope]&token_type=bearer
). After adding the header the response is json. So the type may need to be explicitly declared if it will be treated as json format.How Has This Been Tested?
Tested with github mcp server
Breaking Changes
No
Types of changes
Checklist