hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-11691) Add a proper scheme to the datanode links in NN web UI
Date Fri, 21 Apr 2017 20:43:04 GMT

     [ https://issues.apache.org/jira/browse/HDFS-11691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kihwal Lee updated HDFS-11691:
------------------------------
    Description: 
On the datanodes page of the namenode web UI, the datanode links may not be correct if the
namenode is serving the page through http but https is also enabled.  This is because {{dfshealth.js}}
does not put a proper scheme in front of the address.  It already determines whether the address
is non-secure or secure. It can simply prepend {{http:}} or {{https:}} to what it is currently
setting.

The existing mechanism would work for YARN and MAPRED, since they can only serve one protocol,
HTTP or HTTPS.

  was:
On the datanodes page of the namenode web UI, the datanode links may not be correct if the
namenode is serving the page through http but https is also enabled.  This is because {{dfshealth.html}}
does not put a proper scheme in front of the address.  It already determines whether the address
is non-secure or secure. It can simply prepend {{http:}} or {{https:}} to what it is currently
setting.

The existing mechanism would work for YARN and MAPRED, since they can only serve one protocol,
HTTP or HTTPS.


> Add a proper scheme to the datanode links in NN web UI
> ------------------------------------------------------
>
>                 Key: HDFS-11691
>                 URL: https://issues.apache.org/jira/browse/HDFS-11691
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Kihwal Lee
>
> On the datanodes page of the namenode web UI, the datanode links may not be correct if
the namenode is serving the page through http but https is also enabled.  This is because
{{dfshealth.js}} does not put a proper scheme in front of the address.  It already determines
whether the address is non-secure or secure. It can simply prepend {{http:}} or {{https:}}
to what it is currently setting.
> The existing mechanism would work for YARN and MAPRED, since they can only serve one
protocol, HTTP or HTTPS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message