You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generating a sigv4 presigned URL when the base URL contains a query parameter without a value results in a presigned URL that doesn't contain the parameter at all, because parse_qs strips blank parameters by default.
For example, 'https://s3.amazonaws.com/mybucket/mykey?uploads' is a base URL for creating a multipart upload URL, and the resulting presigned URL that is generated by the following code no longer has an 'uploads' param when SigV4 is used:
The text was updated successfully, but these errors were encountered:
eukaryote
changed the title
SigV4 Presigned URLs broken if URL contains blank query params
Blank params in base URL not preserved in SigV4 Presigned URL
Oct 22, 2016
eukaryote
added a commit
to eukaryote/botocore
that referenced
this issue
Oct 22, 2016
* release-1.4.79:
Bumping version to 1.4.79
Update S3 SigV2 param whitelist
Update to latest models
Update documentation for raw_config_parse
Properly log skipping environment credentials
JSON load request data when presigning
Add support disabling subsection parsing
changelog entry for #1059
sigv4 presigned URL should preserve blank values #1059
unit test showing bug
Generating a sigv4 presigned URL when the base URL contains a query parameter without a value results in a presigned URL that doesn't contain the parameter at all, because parse_qs strips blank parameters by default.
For example, 'https://s3.amazonaws.com/mybucket/mykey?uploads' is a base URL for creating a multipart upload URL, and the resulting presigned URL that is generated by the following code no longer has an 'uploads' param when SigV4 is used:
The text was updated successfully, but these errors were encountered: