Skip to content

Conversation

@nikolavp
Copy link
Contributor

The content type header contains full mimetype string which might contain parameters. The getJSON function doesn't account for this and so some responses fail to parse although they are perfectly acceptable. For example

curl -vv 'https://github.com/.well-known/oauth-authorization-server/login/oauth'

returns a content type header with the value

content-type: application/json; charset=utf-8

which is perfectly valid but fails in the current logic.

Copy link
Contributor

@jba jba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@jba jba merged commit e009bac into modelcontextprotocol:main Dec 12, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants