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
Currently, we return an error response if the status code is != 2xx. I realized recently that the status codes in the GraphQL over HTTP spec are more for proxies and other links in the chain that do not speak GraphQL than for the client.
Investigate under what conditions we can parse the response and return it to the user (always? Or depending on the returned Content-Type?)
Also add graphql-response+json to the list of accepted content-types.
martinbonnin
changed the title
Clarify the handling of HTTP status codes
Clarify the handling of HTTP status codes and Accept graphql-response+json
Jul 27, 2024
Description
Currently, we return an error response if the status code is
!= 2xx
. I realized recently that the status codes in the GraphQL over HTTP spec are more for proxies and other links in the chain that do not speak GraphQL than for the client.Investigate under what conditions we can parse the response and return it to the user (always? Or depending on the returned
Content-Type
?)Also add
graphql-response+json
to the list of accepted content-types.See https://graphql.github.io/graphql-over-http/draft/#sec-Processing-the-response
The text was updated successfully, but these errors were encountered: