[v16] Fix AWS SigV4 parsing #51044
Open
[v16] Fix AWS SigV4 parsing #51044
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
Parsing the AWS SigV4 Authorization header no longer requires spaces between the components - only the comma delimiter is required. * add test case for empty signed header list
GavinFrazar
force-pushed
the
gavinfrazar/v16-fix-sigv4-parsing
branch
from
16ff6db to
a4d46b6
Compare
greedy52
approved these changes
Jan 14, 2025
GavinFrazar
changed the title
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.
Backport #50973 to branch/v16
changelog: Fixed AWS SigV4 parse errors in app access when the application omits the optional spaces between the SigV4 components.