Skip to content

Consistency of reference to IETF RFCs #417

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

Merged
benjie merged 5 commits into from
Aug 5, 2026
+14 −12
Merged

Consistency of reference to IETF RFCs #417

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e5d98a9
Consistency of reference to IETF RFCs
benjie Aug 3, 2026
962d97f
Missed one
benjie Aug 3, 2026
a189f10
Fix wording around Accept
benjie Aug 3, 2026
9d61019
Add link
benjie Aug 3, 2026
9bffebb
Change Accept to Content Negotiation
benjie Aug 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
26 changes: 14 additions & 12 deletions spec/GraphQLOverHTTP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -225,8 +225,8 @@ be part of a well-formed _GraphQL-over-HTTP request_.
## Accept

A client MUST indicate the media types that it supports in responses using the
`Accept` HTTP header as specified in
[RFC7231](https://datatracker.ietf.org/doc/html/rfc7231).
`Accept` HTTP header; this header is specified in
[IETF RFC 9110](https://httpwg.org/specs/rfc9110.html#field.accept).

Note: If a client does not supply the `Accept` header then the server may
respond with an error, or with any content type it chooses (including serving a
Expand Down Expand Up @@ -282,7 +282,7 @@ necessary to conform with the long-established semantics of safe methods within
HTTP.

Note: If status code `405` is used then the `Allow` header must be included as
per [RFC9110](https://httpwg.org/specs/rfc9110.html#status.405).
required by [IETF RFC 9110](https://httpwg.org/specs/rfc9110.html#status.405).

### Example

Expand Down Expand Up @@ -312,7 +312,8 @@ _GraphQL-over-HTTP request_ parameters encoded in one of the officially
recognized GraphQL media types, or another media type supported by the server.

A client MUST indicate the media type of a request body using the `Content-Type`
header as specified in [RFC7231](https://datatracker.ietf.org/doc/html/rfc7231).
header; this header is specified in
[IETF RFC 9110](https://httpwg.org/specs/rfc9110.html#field.content-type).

A server MUST support POST requests encoded with the `application/json` media
type (as indicated by the `Content-Type` header) encoded with UTF-8.
Expand Down Expand Up @@ -410,7 +411,7 @@ validating and executing the requested operation if successful, and describes
any errors encountered during the request.

A server must comply with
[RFC7231](https://datatracker.ietf.org/doc/html/rfc7231).
[IETF RFC 9110](https://httpwg.org/specs/rfc9110.html).

## Body

Expand All @@ -433,9 +434,9 @@ header and attempt to encode the response in the highest priority media type
listed that is supported by the server.

In alignment with the
[HTTP 1.1 Accept](https://tools.ietf.org/html/rfc7231#section-5.3.2)
specification, when a client does not include at least one supported media type
in the `Accept` HTTP header, the server MUST either:
[IETF RFC 9110 Content Negotiation](https://httpwg.org/specs/rfc9110.html#content.negotiation),
when the request includes an `Accept` header and no supported media type is
acceptable according to that header, the server MUST either:

Comment thread
benjie marked this conversation as resolved.
1. Respond with a `406 Not Acceptable` status code and stop processing the
request; OR
Expand Down Expand Up @@ -645,7 +646,8 @@ response; it still indicates successful execution.
# Non-normative notes

This section of the specification is non-normative, even where the words and
phrases specified in RFC2119 are used.
phrases specified in [IETF RFC 2119](https://tools.ietf.org/html/rfc2119) are
used.

## Partial success

Expand Down Expand Up @@ -736,9 +738,9 @@ HTTP request size would suggest.
### Other resources

For more detailed security considerations, please refer to
[RFC 7231](https://tools.ietf.org/html/rfc7231),
[RFC 6454](https://tools.ietf.org/html/rfc6454), other relevant RFCs, and other
resources such as [OWASP](https://owasp.org).
[IETF RFC 9110](https://httpwg.org/specs/rfc9110.html),
[IETF RFC 6454](https://tools.ietf.org/html/rfc6454), other relevant RFCs, and
other resources such as [OWASP](https://owasp.org).

## Future compatibility

Expand Down
Loading