feat(auth): add content type and length to signature headers #804
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
71698a7 to
77deea0
Compare
wilsonianb
approved these changes
Nov 30, 2022
| @@ -69,18 +69,33 @@ export async function generateSigHeaders({ | |||
| body?: unknown | |||
| authorization?: string | |||
| } | |||
| }): Promise<{ sigInput: string; signature: string; contentDigest?: string }> { | |||
There was a problem hiding this comment.
Are we going to be able to just replace this with http-signature-utils' createSignatureHeaders?
There was a problem hiding this comment.
Yeah, pretty easily I think.
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.
Changes proposed in this pull request
Content-TypeandContent-Lengthto the signature input & signature components of a generated httpsig signature.Context
Checklist
fixes #number