[
https://issues.apache.org/jira/browse/HADOOP-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793624#action_12793624
]
Todd Lipcon commented on HADOOP-6408:
-------------------------------------
bq. That's much simpler to handle than filtering content.
I may be incorrect, but I *believe* the filter could be as simple as "Show 404
Forbidden for /conf". Shouldn't be more than a few lines of code to do that.
So, I'm in favor of ignoring the security issue and if people have an issue we
can provide some sample code for that filter. As the web apps gain proper
security in 22, this will be protected just the same.
> Add a /conf servlet to dump running configuration
> -------------------------------------------------
>
> Key: HADOOP-6408
> URL: https://issues.apache.org/jira/browse/HADOOP-6408
> Project: Hadoop Common
> Issue Type: New Feature
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.22.0
>
> Attachments: hadoop-6408.txt, hadoop-6408.txt, hadoop-6408.txt,
> hadoop-6408.txt
>
>
> HADOOP-6184 added a command line flag to dump the running configuration. It
> would be great for cluster troubleshooting to provide access to this as a
> servlet, preferably in both JSON and XML formats. But really, any format
> would be better than nothing. This should/could go into all of the daemons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
