Another fix required for correct signature using query string arrays #26
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
… query parameter arrays. Because the canonical string must be generated in a repeatable, consistent way, if a query parameter appears multiple times in the request, it must be ordered by it's value alphanumerically.
jlagnese-allata
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.
One more fix is required to correctly generate canonical strings with query parameter arrays.
Because the canonical string must be generated in a repeatable, consistent way, if a query parameter appears multiple times in the request, it must be ordered by it's value alphanumerically when generating the canonical string.
For example, if the request contains this query parameter array:
?ids=C&ids=A&ids=B
The canonical string must be:
?ids=A&ids=B&ids=C