Add test to exercise excluded headers in aws-sigv4 #1890
Merged
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.
Motivation and Context
This commit addresses #1392 by adding a test for the functionality introduced in #1381.
Description
Prior to this PR, there was an existing test
presigning_header_exclusion
that exercised the said functionality but it only covered the behavior partially, i.e. only a case where theexcluded_headers
field inSigningSettings
contained justuser-agent
. The new test is aproptest
and will randomly add headers toexcluded_headers
to verify the functionality works as expected.Testing
Ran
cargo t
within theaws-sigv4
crate.Checklist
CHANGELOG.next.toml
if I made changes to the AWS SDK, generated SDK code, or SDK runtime cratesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.