Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: 6.1.22
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Ubuntu 10.04, OpenJDK Runtime Environment (IcedTea6 1.8) (6b18-1.8-0ubuntu1) and Sun JRE 6 (6.20dlj-1ubuntu3)
-
Number of attachments :
Description
Looks like something is flip-flopped. (I guess I could try forward-porting IPAccessHandler from jetty 5.)
Remote access isn't blocked at all, while local access is blocked (404 or 403 if GET .htaccess).
I've reduced the test case to this .htaccess:
<Limit>
allow from 127.0.0.1
</Limit>
And this context configuration is:
<Configure id="myContext" class="org.mortbay.jetty.servlet.Context">
<Set name="resourceBase"><SystemProperty name="jetty.home" default="."/>/webapps/root/</Set>
<Set name="contextPath">/</Set>
<Call name="setSecurityHandler">
<Arg>
<New class="org.mortbay.jetty.security.HTAccessHandler">
<Set name="protegee">
<Ref id="myContext"/>
</Set>
</New>
</Arg>
</Call>
<!-- etc -->
</Configure>
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Michael Gorovoy [ mgorovoy ] |
| Attachment | jetty-1239_patch.diff [ 52117 ] |
| Assignee | Michael Gorovoy [ mgorovoy ] | Greg Wilkins [ gregw ] |
| Assignee | Greg Wilkins [ gregw ] |
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Duplicate [ 3 ] |
I've been able to reproduce the problem.