[
https://issues.apache.org/jira/browse/HADOOP-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990505#comment-13990505
]
Daniel Darabos commented on HADOOP-10511:
-----------------------------------------
Thanks! I get the same exception. It seems that the exception is at least not
my fault — I get it both with and without my patch. But it would sure be good
to be able to demonstrate the fix from the command line. I'll try to figure out
what's wrong.
Yes, the patch has everything.
> s3n:// incorrectly handles URLs with secret keys that contain a slash
> ---------------------------------------------------------------------
>
> Key: HADOOP-10511
> URL: https://issues.apache.org/jira/browse/HADOOP-10511
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Reporter: Daniel Darabos
> Attachments: HADOOP-10511.patch
>
>
> This is similar to HADOOP-3733, but happens on s3n:// instead of s3://.
> Essentially if I have a path like "s3n://key:pass%[email protected]/test",
> it will under certain circumstances be replaced with "s3n://key:pass/test"
> which then causes "Invalid hostname in URI" exceptions.
> I have a unit test and a fix for this. I'll make a pull request in a moment.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
