Do not encode ~ in V4 S3 signing #798
Merged
Conversation
This file contains hidden or 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
kannappanr
reviewed
Sep 13, 2019
Co-Authored-By: kannappanr <[email protected]>
|
We have roughly 700 files that failed to upload out of 1.5M objects. We are happy to test this out later this week or early next week if the fix gets reviewed by @harshavardhana and merged. |
kannappanr
approved these changes
Sep 17, 2019
harshavardhana
approved these changes
Sep 17, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Uploading an object whose name contains a ~ fails with
signature mismatch error. The reason is that ~ should not
be encoded to %7E as other special characters.
Fix #795