update signature headers to point to rfc9421 #41530
Draft
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
github-actions
bot
added
Content:HTTP
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Update the
Signature,Accept-Signature, andSignature-Inputheaders to point to the RFC9421 rather than a WICG draft. AlsoSigned-Headersseems to to not be used, so changing in favor ofSignature-Inputwhich is defined. Based on this issue, the WICG http message signatures seems somewhat obsoleted?Motivation
Points to the adopted RFC rather than draft documents
Additional details
n/a
Related issues and pull requests
(WICG/webpackage#713)
(#37701)