You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Kan Zhang (JIRA)" <ji...@apache.org> on 2008/10/24 00:04:44 UTC

[jira] Commented: (HADOOP-4282) User configurable filter fails to filter accesses to certain directories

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

Kan Zhang commented on HADOOP-4282:
-----------------------------------

Note that with HADOOP-4284 now committed, this bug can be caught in junit test by trying to access a non-existent file in either /logs or /static directories. In other words, whether the tested file exists or not doesn't matter.

> 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
>
> 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.