Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 56545 invoked from network); 5 Aug 2008 16:47:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Aug 2008 16:47:37 -0000 Received: (qmail 38074 invoked by uid 500); 5 Aug 2008 16:47:34 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 38046 invoked by uid 500); 5 Aug 2008 16:47:34 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 38035 invoked by uid 99); 5 Aug 2008 16:47:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Aug 2008 09:47:34 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Aug 2008 16:46:47 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 860B7234C194 for ; Tue, 5 Aug 2008 09:46:44 -0700 (PDT) Message-ID: <1218713310.1217954804548.JavaMail.jira@brutus> Date: Tue, 5 Aug 2008 09:46:44 -0700 (PDT) From: "Doug Cutting (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3854) org.apache.hadoop.http.HttpServer should support user configurable filter In-Reply-To: <1999234883.1217356891731.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619952#action_12619952 ] Doug Cutting commented on HADOOP-3854: -------------------------------------- > The filter mapping will solve the problem. But shouldn't the filter mapping be done in Hadoop, not by the application, so that when, e.g., we restructure Hadoop's urls, applications that use this feature don't have to be updated? Folks could specify an authentication filter that's called for user-facing pages. That seems like a much easier API for Hadoop to maintain compatibly. > 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.