On Mon, 2008-09-29 at 22:28 +0200, André Warnier wrote:
> The first thing maybe to check is if you don't by any chance have some
> sections that override your section.
Yup, that got me on the right track.
I had a spurious I copied
from a httpd.conf that was used for an application
on a dedic
On Mon, Sep 29, 2008 at 5:20 PM, André Warnier <[EMAIL PROTECTED]> wrote:
> Eric Covener wrote:
Order deny,allow
Allow from 192.168
Deny from all
AllowOverride All
Options -Indexes
>>
JkMount /protected/jsp/* tomcat_w
Eric Covener wrote:
Order deny,allow
Allow from 192.168
Deny from all
AllowOverride All
Options -Indexes
JkMount /protected/jsp/* tomcat_worker
141.x.x.x - - [23/Sep/2008:13:28:34 +0200] "GET /protected/index.html HTTP/1.0" 200 7675
"-" "Wget/1.11"
>>
>> Order deny,allow
>> Allow from 192.168
>> Deny from all
>> AllowOverride All
>> Options -Indexes
>>
>> JkMount /protected/jsp/* tomcat_worker
>> 141.x.x.x - - [23/Sep/2008:13:28:34 +0200] "GET /protected/index.html
>> HTTP/1.0" 200 7675 "-" "Wget/1
Hi.
On the face of it, I do not understand it either.
I have re-read the doc, and I believe your Order, Allow and Deny
directives are correct for what you want to do.
The first thing maybe to check is if you don't by any chance have some
sections that override your section.
Also, I encoun
Hi,
Just for the record, I worked around the problem
using a rewrite to a 404 page for the clients not allowed.
I'm still curious about the actual problem.
Anyone ? Do I need to provide some more details ?
Yours,
Steffen
On Tue, 2008-09-23 at 13:48 +0200, Steffen Neumann wrote:
> Hi,
>
> Se
