http: add RFC references for each status code#33671
Closed
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Reference format: `RFC <rfc id> <section path>`
Reference format is as follows RFC <rfc id> <section path>. Using the RFC reference makes it easier to get more information regarding the status code directly from IETF.
jasnell approved these changes Jun 1, 2020
Contributor
Ethan-Arrowood commented Jun 1, 2020
Is there any interest in duplicating this list in the HTTP docs as well? We could also link to MDN docs for these codes which is one of my go to resources for it |
ContributorAuthor
Voltra commented Jun 2, 2020
If there is such interest, I would be more than happy to work on it (maybe as a follow up pull request). I'm thinking about referencing, under a new section, all status code using the following format: |
Contributor
Ethan-Arrowood commented Jun 2, 2020
+1 for a separate PR - feel free to tag me I'll help review 😄 |
rexagod approved these changes Jun 8, 2020
rickyes approved these changes Aug 10, 2020
github-actionsbot removed the request-ci 
Collaborator
rickyes added the author ready rickyes pushed a commit that referenced this pull request Aug 15, 2020
Reference format: `RFC <rfc id> <section path>` PR-URL: #33671 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Pranshu Srivastava <[email protected]> Reviewed-By: Ricky Zhou <[email protected]>
Contributor
rickyes commented Aug 15, 2020
MylesBorins pushed a commit that referenced this pull request Aug 17, 2020
Reference format: `RFC <rfc id> <section path>` PR-URL: #33671 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Pranshu Srivastava <[email protected]> Reviewed-By: Ricky Zhou <[email protected]>
Merged
BethGriggs pushed a commit that referenced this pull request Aug 20, 2020
Reference format: `RFC <rfc id> <section path>` PR-URL: #33671 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Pranshu Srivastava <[email protected]> Reviewed-By: Ricky Zhou <[email protected]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reference format is as follows
RFC <rfc id> <section path>. Using the RFC reference makes it easier to get more information regarding the status code directly from IETF.Checklist