[
https://issues.apache.org/jira/browse/HADOOP-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619743#action_12619743
]
Doug Cutting commented on HADOOP-3854:
--------------------------------------
I agree that authentication and logging on our web servers needs to be
extensible. I am also aware that filters support universal functions. What I
question is whether we want to support authentication and logging extensibility
with such a universal function, or whether it might be better to provide more
specific extensibility mechanisms for these cases. Should we perhaps instead
have one filter we call to authenticate requests, and another to log them, that
folks can separately replace? In the authentication case, should we support a
standard mechanism of annotating the http request with the user's credentials?
Or do you think for some reason those would be overkill, that the more-general
mechanism is more appropriate here?
I don't necessarily think this is a bad approach, I'm just trying to better
understand its motivation.
> 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.
