[
https://issues.apache.org/jira/browse/HADOOP-14114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882465#comment-15882465
]
Hudson commented on HADOOP-14114:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11298 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11298/])
HADOOP-14114 S3A can no longer handle unencoded + in URIs. Contributed (stevel:
rev 9c22a91662af24569191ce45289ef8266e8755cc)
* (edit)
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3native/TestS3xLoginHelper.java
* (edit)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3native/S3xLoginHelper.java
> S3A can no longer handle unencoded + in URIs
> ---------------------------------------------
>
> Key: HADOOP-14114
> URL: https://issues.apache.org/jira/browse/HADOOP-14114
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 2.8.0
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Minor
> Fix For: 2.8.1
>
> Attachments: HADOOP-14114.001.patch
>
>
> Amazon secret access keys can include alphanumeric characters, but also / and
> + (I wish there was an official source that was really specific on what they
> can contain, but I'll have to rely on a few blog posts and my own experience).
> Keys containing slashes used to be impossible to embed in the URL (e.g.
> s3a://access_key:secret_key@bucket/) but it is now possible to do it via URL
> encoding. Pluses used to work, but that is now *only* possible via URL
> encoding.
> In the case of pluses, they don't appear to cause any other problems for
> parsing. So IMO the best all-around solution here is for people to URL-encode
> these keys always, but so that keys that used to work just fine can continue
> to work fine, all we need to do is detect that, log a warning, and we can
> re-encode it for the user.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
