Skip to content

Add a section about the HTTP protocol #376

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

Open
martinbonnin wants to merge 5 commits into
base: main
Choose a base branch
from
+19 −0
Open

Add a section about the HTTP protocol #376

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3b87602
Add a note about the HTTP protocol
martinbonnin Apr 2, 2026
4081cc5
Reword
martinbonnin Apr 2, 2026
1b80e45
Reduce diff
martinbonnin Apr 2, 2026
54fcc9b
Use consistent links
martinbonnin Apr 2, 2026
6899648
make the HTTP section a bit easier to read and not just about compliance
martinbonnin Apr 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions spec/GraphQLOverHTTP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,25 @@ interact with a _GraphQL service_.
Note: GraphQL Subscriptions are beyond the scope of this specification at this
time.

# HTTP protocol

The details of the HTTP protocol used by GraphQL clients and servers are outside
this specification.

Where applicable, server and clients MUST comply with
[RFC7231](https://datatracker.ietf.org/doc/html/rfc7231) semantics.

In particular, "header", "status code", "body", "Accept", and "Content-Type" are
Copy link
Copy Markdown
Contributor Author

@martinbonnin martinbonnin Apr 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note from wg: we should wrap those in spec-md formatting.

cf https://github.com/graphql/graphql-over-http/blob/main/spec/metadata.json

to be interpreted according to
[RFC7231](https://datatracker.ietf.org/doc/html/rfc7231).

A server MUST support at least one version of the HTTP message format, such as
[HTTP/1.1](https://datatracker.ietf.org/doc/html/rfc7230) or
[HTTP/2](https://datatracker.ietf.org/doc/html/rfc9113).
Comment on lines +133 to +134
Copy link
Copy Markdown
Contributor Author

@martinbonnin martinbonnin Apr 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note from wg: remove this, do not bind ourselves to this.


A server MAY support several versions of the HTTP message format for wider
compatibility.
Comment on lines +136 to +137
Copy link
Copy Markdown
Contributor Author

@martinbonnin martinbonnin Apr 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note from wg: We can also remove that sentence, it's redundent with the above.


# URL

A _server_ MUST enable GraphQL requests to one or more GraphQL schemas.
Expand Down
Loading