Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Adapt to official media type changes in GraphQL over HTTP spec #563

Closed
bclozel opened this issue Dec 3, 2022 · 0 comments
Closed

Adapt to official media type changes in GraphQL over HTTP spec #563

bclozel opened this issue Dec 3, 2022 · 0 comments
Assignees
@bclozel
Labels
type: enhancement A general enhancement
Milestone
1.1.1

Comments

@bclozel
Copy link
Member

bclozel commented Dec 3, 2022

As of graphql/graphql-over-http#215, the GraphQL over HTTP spec decided to change the official media type for GraphQL responses over HTTP. This means that:

  • clients are expected to send requests as "application/json"
  • servers are expected to reply with "application/json" or "application/graphql-response+json", with content negotiation

With this issue, we need to deprecate "application/graphql+json" and introduce support for "application/graphql-response+json".

See spring-projects/spring-framework#29617
@bclozel bclozel added the type: enhancement A general enhancement label Dec 3, 2022
@bclozel bclozel added this to the 1.1.1 milestone Dec 3, 2022
@bclozel bclozel self-assigned this Dec 3, 2022
@bclozel bclozel closed this as completed in 573e899 Dec 5, 2022
bclozel added a commit that referenced this issue Dec 6, 2022
@bclozel
Reflect media type changes in reference documentation
6029e45 
This commit mentions the `"application/graphql-response+json`" media
type in the reference documentation as the main media type used by the
server.

See gh-563
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bclozel bclozel

Labels
type: enhancement A general enhancement
Projects
None yet
Milestone
1.1.1
Development

No branches or pull requests
1 participant
@bclozel