Spec references RFC7231 which is obsoleted

Open
  • Is something wrong?
#201 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start in GraphQLOverHTTP.md at the Response section and review its RFC7231 reference and related subsection links, including HTTP 1.1 Accept. Check the current RFC references and determine the required link and title updates. Done means the specification consistently references the intended RFC and its relevant subsections.

Written by the indexing model from the issue text.

Description

enhancement

Here are couple of things I found that might be an issue:

Section Response

A server must comply with RFC7231.

First, it would be nice to provide RFC title along with numeric ID, just as a nice gesture to the reader.
Secondly, this RFC page has a note on top: "Obsoleted by: 9110"; should the spec reference the newer RFC? otherwise some comment is needed.

Note: If changing ref to 9110, then some other links to its subsections should be updated. Ex: link to "HTTP 1.1 Accept" section.

Dominant language
JavaScript
Stars
428
Forks
70
Avg merge
11m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphql/graphql-over-http

All issues in graphql/graphql-over-http

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.