Spring for GraphQL 1.4 M1 Released
On behalf of the Spring for GraphQL team, I am pleased to announce the availability of our first 1.4 milestone.
Aligning with the GraphQL over HTTP specification
The GraphQL over HTTP draft specification is making good progress,
so we have decided to fully align with it for our 1.4 release.
Previous versions of Spring for GraphQL already supported the official "application/graphql-response+json"
,
and it has been our default response media type for a while now.
Usually, GraphQL HTTP clients should expect 4xx/5xx HTTP responses if the server is unavailable,
security credentials are missing or if the request body is not valid JSON.
The remaining gap with this new specification was about the HTTP response status behavior in case of complete GraphQL engine failures.
With recent changes, "application/graphql-response+json" responses will also use 4xx statuses if the GraphQL document sent by the client cannot be parsed
or is considered invalid by the GraphQL engine. We are keeping the former behavior when clients request the "application/json"
…