You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Harsh J Chouraria (JIRA)" <ji...@apache.org> on 2011/03/16 21:00:29 UTC

[jira] Commented: (HADOOP-1919) Add option to allow Binding Jetty to localhost

    [ https://issues.apache.org/jira/browse/HADOOP-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007668#comment-13007668 ] 

Harsh J Chouraria commented on HADOOP-1919:
-------------------------------------------

What the OP asks for, specifically, is possible by setting the dfs.http.address to localhost:port 'stead of 0.0.0.0. I think this can be closed with that tip.

As Raghu pointed out, distcp and hftp services will get affected by this, if being called upon external to the machine -- but nothing else apparently. Perhaps /fsck too will fail if used from a machine other than the NameNode's one.

> Add option to allow Binding Jetty to localhost
> ----------------------------------------------
>
>                 Key: HADOOP-1919
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1919
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 0.14.0
>            Reporter: Thurman Turner
>            Priority: Minor
>
> We would like a configurable option to have Jetty bound to the loopback address of the machine so that the dfs-browser is not accessible from outside the host.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira