hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-14114) S3A can no longer handle unencoded + in URIs
Date Thu, 23 Feb 2017 19:28:44 GMT
Sean Mackrory created HADOOP-14114:
--------------------------------------

             Summary: 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
            Reporter: Sean Mackrory
            Assignee: Sean Mackrory


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: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org


Mime
View raw message