[compression-dictionary] Added link relation #2783
Merged
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
|
Thanks. Flows better with the suggested changes (PR updated). |
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.
This adds the definition for the
compression-dictionarylink relation type and relevant IANA registration information.The link relation provides a way to trigger the fetch of a stand-alone dictionary (e.g. for compressing HTML). The actual dictionary processing follows the standard path and headers once the fetch has been initiated.
There is discussion in issue #2772 as well as a related issue in the HTML spec.
In Chrome's current origin trial and the initial explainers this is the
dictionaryrelation type but that term is too generic for this specific case.Fix #2772