[
https://issues.apache.org/jira/browse/HDFS-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoy Antony updated HDFS-5660:
-------------------------------
Description:
When SSL is enabled by setting "hadoop.ssl.enabled", SSL will be enabled on the
regular port (infoport) on Datanode. (case 1)
When SSL on HDFS is enabled by setting "dfs.https.enable", SSL will be enabled
on a separate port (infoSecurePort) on Datanode. (case 2)
if SSL is enabled , the Namenode always redirects to infoSecurePort.
"infoSecurePort" will be 0 in case 1 above.
This breaks the file browsing via web.
was:
When SSL is enabled by setting "hadoop.ssl.enabled", SSL will be enabled on the
regular port (infoport) on Datanode. (case 1)
When SSL on HDFS is enabled by setting "dfs.https.enable", SSL will be enabled
on a separate port (infoSecurePort) on Datanode. (case 2)
if SSL is enabled , the Namenode always redirects to infoSecurePort.
"infoSecurePort" will be 0 in case 1 above.
This breaks the file browsing via web.
> When SSL is enabled , the Namenode WEBUI redirects to Infosecport, which
> could be 0
> -----------------------------------------------------------------------------------
>
> Key: HDFS-5660
> URL: https://issues.apache.org/jira/browse/HDFS-5660
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Attachments: HDFS-5660.patch
>
>
> When SSL is enabled by setting "hadoop.ssl.enabled", SSL will be enabled on
> the regular port (infoport) on Datanode. (case 1)
> When SSL on HDFS is enabled by setting "dfs.https.enable", SSL will be
> enabled on a separate port (infoSecurePort) on Datanode. (case 2)
> if SSL is enabled , the Namenode always redirects to infoSecurePort.
> "infoSecurePort" will be 0 in case 1 above.
> This breaks the file browsing via web.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
