graphql-over-http
graphql-over-http copied to clipboard
graphql
Working draft of "GraphQL over HTTP" specification
Reference: https://github.com/graphql/graphql-over-http/pull/175#discussion_r917932366 just pulling this out in case there is not another issue to track in my view, query should be optional so that persisted operations, automatic or otherwise, could...
Request parameter section currently specifies > Note: Specifying null in JSON (or equivalent values in other formats) as values for optional request parameters is equivalent to not specifying them at...
When it comes to sending large scalars over HTTP, @jaydenseric's [graphql multipart spec](https://github.com/jaydenseric/graphql-multipart-request-spec) is the _de facto_ standard at this point, being supported by many languages and tools, including Apollo's...
The terms "persisted queries" and "stored operations" are typically used interchangably. The traditional name is "persisted queries", but the term "stored operations" acknowledges that this approach can be used with...
Bit of context, I have an authenticated Apollo Server using OAuth. There is a bit of a conflict between OAuth spec and GraphQL as the [OAuth spec recommends returning 401...
(when we're ready) @jaydenseric Adding this an issue as it's a better primitive for tracking
from [GraphQL over HTTP Spec](https://graphql.github.io/graphql-over-http/draft/#sec-Request) > A server MUST accept POST requests, and MAY accept other HTTP methods, such as GET. For semantics and performance (caching, etc.), it seems to...
Server-Sent Events (SSE) is a server push technology enabling a client to receive automatic updates from a server via an HTTP connection, that does not require any complex protocol compared...
Here are couple of things I found that might be an issue: Section [Response](https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md#response) > A server must comply with RFC7231. First, it would be nice to provide RFC title...
Hi, I see that the proposed spec is supporting most HTTP status codes. Does this group have any opinion on the following; 1-Providing guidance in the specification to use appropriate...
