Fix query string handling, add test for S3 list_objects_v2 proxying #55
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
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.
Fix query string handling, add test for S3
list_objects_v2proxying.This is a follow-up to PR #54 which reproduces a customer issue that has been detected in a support call today. Turns out that we were incorrectly parsing the query strings from the incoming request in the proxy. This is reproducible with S3
list_objects_v2, where the input parameters are passed as query params, something likeGET /test-bucket-10b298b9?list-type=2&prefix=test%2F&encoding-type=url.This is now also covered by a small test, to avoid regressions in the future.