How to identify GraphQL requests about graphql-over-http HOT 10 CLOSED

I think this issue can be closed, as #161 is merged.

from graphql-over-http.

I think I can write a first draft for this, after the next mtg.

I'm not sure which direction to go for it, so that first draft might be very preliminary and include options or notes for discussion.

from graphql-over-http.

As per the current state of the spec, the server can recognize a client request as a GraphQL request by the Content-Type header value. It should equal application/graphql+json if the request is intended to be handled as a GraphQL request.

Things changed. Now server should deal with Accept header. No application/graphql+json mime for requests anymore, application/graphql-response+json only for responses.

from graphql-over-http.

@kettanaito That's the intention after the watershed, but before then very few servers are likely to support it.

from graphql-over-http.

@mmatsa might be worth reading this PR and seeing whether there's some overlap. #83

from graphql-over-http.

As per the current state of the spec, the server can recognize a client request as a GraphQL request by the Content-Type header value. It should equal application/graphql+json if the request is intended to be handled as a GraphQL request.

from graphql-over-http.

Oh, that's useful! Thanks, @sungam3r.

To recap, is this the expected transaction?

Request:
POST /graphql
Accept: application/graphql-response+json
Content-Type: application/json // still need to describe sent body

{"query":"..."}

Response:
200 OK /graphql
Content-Type: application/graphql-response+json

from graphql-over-http.

The server may respond with Content-Type: application/graphql-response+json; charset=utf-8

See: https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md#media-types

from graphql-over-http.

(For GraphQL.NET Server 7.1, released a few days ago, that is the default response content type, but the server will honor recognized ‘Accept’ headers.)

from graphql-over-http.

In the mean time, it

is RECOMMENDED that a client set the Accept header to application/graphql-response+json; charset=utf-8, application/json; charset=utf-8.
-- https://graphql.github.io/graphql-over-http/draft/#sel-EALHLDFAADHCA_zQ

This should maximize compatibility. If you want to use @stream/@defer then things get a little more complex...

from graphql-over-http.