Open martinheidegger opened 7 years ago
Looks like it's just if the incorrect Authorization header is there. If there's no auth header, then it does return JSON. If you have an incorrect token, then you must send it without an Authorization header.
Yes, it works if the Authorization header is missing. However: I would like to process the error (in case the authorization is wrong) with on a JSON basis and not a HTML response. (it breaks my graphql library: showing a JSON error...)
Both the management and regular graphql endpoints return HTML code if the bearer token is incorrect. It should always return JSON code on an error on the endpoint: