You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just have some questions in relation to moving over to the GraphQL over Http standard mentioned here in the future. Hopefully someone is able to answer these for me and apologies if I've mistaken something, thanks.
Currently response content-type looks to always be application/json. Will response content-type always be application/json or will it change according to the subgraph service to support the GraphQL over Http spec? e.g. application/graphql-response+json possibly being returned instead
When an error occurs that returns a 4xx or 5xx status code from the subgraph service, apollo router currently adds the error details to the errors array in the response and returns it along with a 200 status code. The GraphQL over Http says for application/graphql-response+json, if the client basically has an auth issue, it should reply with a 401/403 or similar status code.
Is the status code expected to be altered to follow GraphQL over Http along with no additional error being added in the future or would it stay as it is?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I just have some questions in relation to moving over to the GraphQL over Http standard mentioned here in the future. Hopefully someone is able to answer these for me and apologies if I've mistaken something, thanks.
Is the status code expected to be altered to follow GraphQL over Http along with no additional error being added in the future or would it stay as it is?
Beta Was this translation helpful? Give feedback.
All reactions