[
https://issues.apache.org/jira/browse/HADOOP-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645966#action_12645966
]
Hadoop QA commented on HADOOP-4282:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12393277/4282_20081103.patch
against trunk revision 712344.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3555/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3555/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3555/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3555/console
This message is automatically generated.
> 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
>
>
> 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.
