Fix RFC 1123 mention to RFC 7231 #565
Merged
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
Also makes how we refer to RFCs numerically in text. We had a mix of `RFC \d+` and `RFC\d+`. I wanted to make them consistent so they are easier (more consistent) to search.
JeffreyRichter
approved these changes
Jan 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We referenced RFC 1123 in a couple of places - one to mention how it differs from RFC 7231 that effectively, eventually replaced it - but in one place that should've been updated to RFC 7231 previously on Mar 25, 2022 when all the other references were updated. Or maybe it was added later by mistake.
Also makes how we refer to RFCs numerically in text. We had a mix of
RFC \d+andRFC\d+. I wanted to make them consistent so they are easier (more consistent) to search.