[
https://issues.apache.org/jira/browse/HADOOP-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619729#action_12619729
]
Doug Cutting commented on HADOOP-3854:
--------------------------------------
I'm trying to think of use cases for this. Logging and authentication are core
functionalities of Hadoop, that folks shouldn't be replacing in this way, no?
We should consistently log using a logging API, and provide ways for folks to
replace that. Similarly for authentication: we should provide an extensible
authentication API that folks can replace. Both logging and authentication are
done in other places besides from HTTP servers. I can see this as a nice
internal API, as a way to call the standard logging and authentication APIs,
but, once we've done that, do we want to support users overriding that and
specifying different logging and authentication mechanisms, just for the HTTP
services, and not for the RPC and raw socket interfaces? That sounds
error-prone. Or am I missing something?
> org.apache.hadoop.http.HttpServer should support user configurable filter
> -------------------------------------------------------------------------
>
> Key: HADOOP-3854
> URL: https://issues.apache.org/jira/browse/HADOOP-3854
> Project: Hadoop Core
> Issue Type: New Feature
> Reporter: Tsz Wo (Nicholas), SZE
> Attachments: 3854_20080729.patch, 3854_20080730.patch,
> LoggingFilter.java, SampleInitializer.java
>
>
> Filters provide universal functions such as authentication, logging and
> auditing, etc. HttpServer should support configurable filters, so that
> individual site administrators could possibly configure filters for their web
> site.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
