Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <772091411.1226360144238.JavaMail.jira@brutus>
Date: Mon, 10 Nov 2008 15:35:44 -0800 (PST)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4282) User configurable filter fails to
 filter accesses to certain directories
In-Reply-To: <910165611.1222392464213.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsz Wo (Nicholas), SZE commented on HADOOP-4282:
------------------------------------------------

The javadoc warning was due to HADOOP-4621.  I am not resubmitting the new patch since there is only a log message change.

> User configurable filter fails to filter accesses to certain directories
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-4282
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4282
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.19.0
>            Reporter: Kan Zhang
>            Assignee: Tsz Wo (Nicholas), SZE
>             Fix For: 0.19.1
>
>         Attachments: 4282_20081103.patch, 4282_20081110.patch
>
>
> Hadoop-3854 introduced a framework where users can add filters to the HTTP server to filter part of the HTTP interface, i.e., those user facing URLs. Directories "/logs/*" and "/static/*" are supposed to be filtered. However, files in those directories can be retrieved without triggering my configured filter. The corresponding junit test didn't catch the bug for 2 reasons. 1) it didn't try to access files in those 2 directories. 2) Even if it did, it might still fail to catch the bug, since according to my observation, only when accessing existent files my filter is bypassed. When accessing non-existent files (which is what the junit test does), my filter is triggered as expected.

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