-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(signature-v4): add support to override the set of unsignableHeaders #420
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Relevant discussions from internal issue tracker below. Findings:
Proposed accepted solution:
interface RequestSigningArguments extends SigningArguments {
/**
* A set of strings whose members represents headers that cannot be signed.
* All headers in the provided request will have their names converted to
* lower case and then checked for existence in the unsignableHeaders set.
*/
unsignableHeaders?: Set<string>;
/**
* A set of strings whose members represents headers that should be signed.
* All headers in the provided request will have their names converted to
* lower case before signing.
*/
signableHeaders?: Set<string>;
} |
Other findings:
This PR provides a way for customers to explicitly opt-in to signing the user agent header |
Co-Authored-By: Trivikram Kamat <16024985+trivikr@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Issue #, if available:
Add support to override the set of unsignableHeaders; in cases where signing those headers (such as user-agent) would be desirable.
Description of changes:
Added a new set of signableHeaders, which is checked for inclusion before the specified header is removed for being an unsignable one.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.