The content of the oauth2/resource/profile endpoint is a JSON object, but the content-type header is text/html. This throws off some parsers and client libraries, like JQuery.
Description
Description
Details
Details
Related Changes in Gerrit:
Customize query in gerrit
Event Timeline
Comment Actions
This isn't a big deal, but it's the kind of detail that can be annoying for client developers.
Comment Actions
Change #1058229 had a related patch set uploaded (by AutumnFeather; author: AutumnFeather):
[mediawiki/extensions/OAuth@master] UNTESTED Fix resource response to use JSON content type header
Comment Actions
Change #1058258 had a related patch set uploaded (by Urbanecm; author: AutumnFeather):
[mediawiki/extensions/OAuth@wmf/1.43.0-wmf.16] Fix resource response to use JSON content type header
Comment Actions
Change #1058259 had a related patch set uploaded (by Urbanecm; author: AutumnFeather):
[mediawiki/extensions/OAuth@wmf/1.43.0-wmf.15] Fix resource response to use JSON content type header
Comment Actions
Change #1058258 merged by jenkins-bot:
[mediawiki/extensions/OAuth@wmf/1.43.0-wmf.16] Fix resource response to use JSON content type header
Comment Actions
Change #1058259 merged by jenkins-bot:
[mediawiki/extensions/OAuth@wmf/1.43.0-wmf.15] Fix resource response to use JSON content type header
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2024-07-30T21:45:42Z] <urbanecm@deploy1003> Started scap sync-world: Backport for [[gerrit:1058258|Fix resource response to use JSON content type header (T263870)]], [[gerrit:1058259|Fix resource response to use JSON content type header (T263870)]]
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2024-07-30T21:53:51Z] <urbanecm@deploy1003> Finished scap: Backport for [[gerrit:1058258|Fix resource response to use JSON content type header (T263870)]], [[gerrit:1058259|Fix resource response to use JSON content type header (T263870)]] (duration: 08m 09s)
Comment Actions
Change #1058229 merged by jenkins-bot:
[mediawiki/extensions/OAuth@master] Fix resource response to use JSON content type header