hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4284) Support for user configurable global filters on HttpServer
Date Fri, 26 Sep 2008 22:59:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635057#action_12635057
] 

Doug Cutting commented on HADOOP-4284:
--------------------------------------

> Currently, there are 3 servlets serving the HSFTP interface, namely /listPaths, /data,
and /streamFile.

Perhaps we need three regexs, with the convention that the first captured group is the URL?

> I feel this is a bigger task than this jira.

This issue in effect exposes a new public interface to Hadoop that must be maintained.  Its
simpler for us to maintain a back-compatible Java API than a URL API, particularly because
we already have mechanisms for this.


> Support for user configurable global filters on HttpServer
> ----------------------------------------------------------
>
>                 Key: HADOOP-4284
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4284
>             Project: Hadoop Core
>          Issue Type: New Feature
>            Reporter: Kan Zhang
>         Attachments: 4284_20080925_78.patch, 4284_20080926_79.patch
>
>
> HADOOP-3854 introduced a framework for adding filters to filter browser facing urls.
Sometimes, there is a need to filter all urls. For example, at Yahoo, we need to open an SSL
port on the HttpServer and only accept hsftp requests from clients who can authenticate themselves
using client certificate and is authorized according to certain policy file. For this to happen,
we need a method to add a user configurable "global" filter, which filters on all client requests.
For our purposes, such a global filter will block all https requests except those accessing
the hsftp interface (it will let all http requests go through, so accesses through the normal
http ports are unaffected). Moreover, those hsftp requests will be subject to further authorization
checking according to the policy file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message