You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This spec is in the draft stage of development, and can change before reaching
Accepted stage. For more information, please see the Roadmap
or how to get involved.
HTTP is the most common choice as the client-server protocol when using GraphQL
because of its ubiquity. However the
GraphQL specification deliberately
does not specify the transport layer.
The closest thing to an official specification is the article
Serving over HTTP. Leading
implementations on both client and server have mostly upheld those best
practices and thus established a de-facto standard that is commonly used
throughout the ecosystem.
This specification is intended to fill this gap by specifying how GraphQL should
be served over HTTP. The main intention of this specification is to provide
interoperability between different client libraries, tools and server
implementations.
To initiate the signature process please open a PR against this repo. The
EasyCLA bot will block the merge if we still need a membership agreement from
you.
If your company benefits from GraphQL and you would like to provide essential
financial support for the systems and people that power our community, please
also consider membership in the
GraphQL Foundation.