graphql/graphql-over-http

Issues

• Response body for non-well-formed GraphQL-over-HTTP requests

  #293 opened 2 months ago by atrigent
  6

• Define behavior of a shorthand query document and a specified operationName

  #312 opened 4 months ago by Ethan-Arrowood
  3

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

  #280 opened a year ago by benjie
  11

• [2024-01-25] Contact Apollo about persisted operations appendix

  #287 opened 5 months ago by benjie
  2

• Question regarding well-formedness of GQL over http responses

  #292 opened 8 months ago by duzinkie
  5

• What is the rationale for handling Invalid parameters as 400?

  #288 opened a year ago by wheresrhys
  15

• Allow non-UTF-8 encodings

  #229 opened a year ago by Shane32
  2

• [2023-10] Add RFC2 status to next GraphQL Spec WG

  #273 opened a year ago by benjie
  1

• [2023-10] Add changes promoting spec to RFC 2 status

  #272 opened a year ago by benjie
  0

• Make it clear that extra keys in the request/response payloads are not allowed

  #271 opened a year ago by benjie
  2

• Create the "Action Item" issue template

  #274 opened a year ago by benjie
  0

• Should we explicitly support `Content-Type: application/graphql`?

  #249 opened 2 years ago by benjie
  13

• Should the query property really be required?

  #250 opened 2 years ago by michaelstaib
  1

• Optional query discussion

  #216 opened 2 years ago by yaacovCR
  13

• Kitchen sink HTTP requests

  #228 opened 2 years ago by tobias-tengler
  3

• Clarification for `Accept: */*`

  #242 opened 2 years ago by tobias-tengler
  8

• Status codes 404 and 410

  #234 opened 2 years ago by saerdnaer
  1

• What is well-formed response

  #230 opened 2 years ago by TomokiMiyauci
  3

• [Incremental Delivery Questions] How is the response protocol determined in different scenarios

  #167 opened 3 years ago by n1ru4l
  10

• GraphQL request optional parameters

  #218 opened 2 years ago by dariuszkuc
  2

• Status codes for unauthenticated OAuth errors

  #213 opened 2 years ago by tadhglewis
  1

• [2022-06-27] Schedule a meeting after the July spec WG

  #196 opened 2 years ago by benjie
  0

• [2022-06-27] Copy over relevant issue labels from main spec repo

  #195 opened 2 years ago by benjie
  2

• [2022-06-27] Go through the issues and close those that are not relevant any more

  #194 opened 2 years ago by benjie
  0

• [2022-06-27] Check spec-md is working correctly and split the spec up into sections

  #193 opened 2 years ago by benjie
  0

• [2022-06-27] Contact Denis to discuss compatibility with websockets and SSE spec

  #192 opened 2 years ago by benjie
  0

• [2022-06-27] Incorporate David's and working group's feedback

  #191 opened 2 years ago by benjie
  0

• Next meeting: Thurs July 21st 17:00 UTC?

  #184 opened 2 years ago by benjie
  12

• Clarify the use of HTTP GET and POST request

  #205 opened 2 years ago by TomokiMiyauci
  2

• Consider dropping GraphQL via GET (at least for Mutations)

  #123 opened 3 years ago by andimarek
  10

• Response status code as `application/json` content

  #203 opened 2 years ago by TomokiMiyauci
  5

• Consider adding SSE for Subscription operations to the specification

  #183 opened 2 years ago by n1ru4l
  11

• Spec references RFC7231 which is obsoleted

  #201 opened 2 years ago by rivantsov
  4

• Set up rendered URL

  #182 opened 2 years ago by leebyron
  1

• Use specmd "metadata" file for back refs to spec

  #181 opened 2 years ago by leebyron
  0

• General HTTP guidance improvements

  #149 opened 4 years ago by jayadeba
  1

• HTTP status code for partial responses

  #172 opened 3 years ago by saerdnaer
  3

• Directives for HTTP Metadata

  #150 opened 4 years ago by jayadeba
  1

• ietf spec submission?

  #155 opened 3 years ago by acao
  4

• Define directives for HTTP compression on the client-side and HTTP caching on the server-side

  #169 opened 3 years ago by isocroft
  9

• Next meeting - Monday 27th June, 17:00 UTC?

  #177 opened 3 years ago by benjie
  7

• Accept requests where `query` is a parsed AST representation

  #176 opened 3 years ago by spawnia
  4

• Setting up EasyCLA to manage GraphQL specification memberships

  #156 opened 4 years ago by brianwarner
  1

• [Incremental Delivery RFC] Requirement on Content-Length

  #136 opened 4 years ago by ificator
  1

• Proposal: Merge to spec more frequently

  #148 opened 4 years ago by mmatsa
  3

• 29 September 2020 - working group

  #141 opened 4 years ago by sjparsons
  0

• Allow for arbitrary boundaries in incremental delivery RFC

  #135 opened 4 years ago by benjie
  8

• 25 August 2020 - working group meeting

  #132 opened 4 years ago by sjparsons
  3

• Updated: Find the best time for the GraphQL over HTTP working group

  #131 opened 4 years ago by sjparsons
  1

• Cancelled: July working group meeting

  #128 opened 4 years ago by sjparsons
  1