Search results

Should we use/encourage HTTP 422 for validation failures?

Status: Open.

#352 In graphql/graphql-over-http;

· benjie opened on Jun 19, 2025

Add assertion that unknown keys should be ignored

Status: Open.

#333 In graphql/graphql-over-http;

· benjie opened on Feb 22, 2025

Consider simplifying the specification?

Status: Open.

#329 In graphql/graphql-over-http;

· martinbonnin opened on Feb 7, 2025

Question regarding well-formedness of GQL over http responses

Status: Open.

#292 In graphql/graphql-over-http;

· duzinkie opened on May 16, 2024

[2023-11] Add notes about security to GraphQL-over-HTTP spec

Action item 🎬

Status: Open.

#280 In graphql/graphql-over-http;

· benjie opened on Nov 9, 2023

Should we explicitly support <code>Content-Type: application/graphql</code>?

question

Status: Open.

#249 In graphql/graphql-over-http;

· benjie opened on Apr 11, 2023

Clarification for <code>Accept: */*</code>

Status: Open.

#242 In graphql/graphql-over-http;

· tobias-tengler opened on Feb 18, 2023

Status codes 404 and 410

Status: Open.

#234 In graphql/graphql-over-http;

· saerdnaer opened on Dec 5, 2022

Optional query discussion

Status: Open.

#216 In graphql/graphql-over-http;

· yaacovCR opened on Aug 12, 2022

Status codes for unauthenticated OAuth errors

question

Status: Open.

#213 In graphql/graphql-over-http;

· tadhglewis opened on Jul 25, 2022

Clarify the use of HTTP GET and POST request

Status: Open.

#205 In graphql/graphql-over-http;

· TomokiMiyauci opened on Jul 19, 2022

· 

1.0 Release

Spec references RFC7231 which is obsoleted

enhancement

Status: Open.

#201 In graphql/graphql-over-http;

· rivantsov opened on Jul 13, 2022

· 

1.0 Release