Update references to RFC9110, RFC9111 and RFC9112 #154
Conversation
This file contains 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
We eventually switched to the `https://httpwg.org/specs/` versions for RFC9110, RFC9111 and RFC9112 in the cross-references database, because they are more readable. Unfortunately, this means that references to sections in these specs need to be updated again, as was done in w3c#144. This update uses the new (and in theory now stable) fragment identifiers.
|
Note that the underlying data has apparently not yet propagated to the online Bikeshed service, so PR Preview failed to generate the right links. This should happen soon, I just don't know when... |
garretrieger
approved these changes
Nov 27, 2023
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 eventually switched to the
https://httpwg.org/specs/versions for RFC9110, RFC9111 and RFC9112 in the cross-references database, because they are more readable.Unfortunately, this means that references to sections in these specs need to be updated again, as was done in #144. This update uses the new (and in theory now stable) fragment identifiers.
Preview | Diff