AWS S3: Fix plus char usage in s3 key #1738
Merged
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
ennru
reviewed
Jun 3, 2019
s3/src/main/scala/akka/stream/alpakka/s3/impl/auth/Signer.scala
Outdated
Show resolved
Hide resolved
ennru
changed the title
|
Thank you for fixing it! |
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.
Purpose
Fixes issue with using
+char in a S3 object keyReferences
#838 S3 Connector - Using
+(plus) symbol causes mismatched request signatureChanges
Raw-Request-URIto the built request. The header contains stringified uri of a request with all+characters replaced with the url-encoded representation%2B.Raw-Request-URI.