[
https://issues.apache.org/jira/browse/HDFS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458942#comment-13458942
]
Colin Patrick McCabe commented on HDFS-3932:
--------------------------------------------
>From wikipedia:
bq. The Internet standards (Request for Comments) for protocols mandate that
component hostname labels may contain only the ASCII letters 'a' through 'z'
(in a case-insensitive manner), the digits '0' through '9', and the hyphen
('-'). The original specification of hostnames in RFC 952, mandated that labels
could not start with a digit or with a hyphen, and must not end with a hyphen.
However, a subsequent specification (RFC 1123) permitted hostname labels to
start with digits. No other symbols, punctuation characters, or white space are
permitted.
So no URL encoding is necessary.
More documentation sounds like a good idea; I'll add that.
bq. The test should also check for the loopback IP for sanity
OK.
> NameNode Web UI broken if the rpc-address is set to the wildcard
> -------------------------------------------------------------------
>
> Key: HDFS-3932
> URL: https://issues.apache.org/jira/browse/HDFS-3932
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 1.0.3, 2.0.0-alpha
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: HDFS-3932.001.patch, HDFS-3932.002.patch,
> HDFS-3932.003.patch
>
>
> If {{dfs.namenode.rpc-address}} is set to the wildcard some of links in the
> dfsnodelist.jsp and browseDirectory.jsp pages are broken because the nnaddr
> field is passed verbatim (eg nnaddr=0.0.0.0:8021).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
