perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fof <...@brainstorm.net.au>
Subject Re: PerlAuthenHandler and ErrorDocument 401
Date Wed, 21 May 2008 00:11:59 GMT


Torsten Foertsch wrote:
> 
> On Tue 20 May 2008, fof wrote:
>>         <Location />
>>                 PerlAuthenHandler MyAuthenHandler
>>                 AuthType Basic
>>                 AuthName "REST Interface"
>>                 Require valid-user
>>         </Location>
>>
>>         ErrorDocument 401 /http/401.html
> 
> Try:
> 
> <Files /http/401.html>
> 	Satisfy any
> </Files>
> 
> Torsten
> 
> --
> Need professional mod_perl support?
> Just hire me: torsten.foertsch@gmx.net
> 
> 

Hey Torsten thanks for the reply but no that does not work either. I think
the real problem I am facing revolves around the reasons why the directory
/REST/ from my document root cannot be secured with a PerlAuthenHandler on
its own. 

It does not matter if I set the Location as <Location /REST/> or <Location
/> in the VirtualHost configuration the PerlAuthenHandler still kicks in for
the root directory regardless. That is to say that
http://rest.mydomain.com/REST/abc.html and http://rest.mydomain.com/abc.html
are secured by the PerlAuthenHandler regardless of what I set the <Location>
path to. 

This is the part that is puzzling me the most. I think if I solve that then
the other stuff will just work. I am going to try removing the
PerlAuthenHandler and simply secure the directory with a htpasswd thus
taking mod_perl out of the picture. This will tell me if some Apache setting
in the main server config is being inherited by my virtual host and stuffing
things up and if it is a mod_perl problem.

Any other suggestions would be appreciated :)

Let ya know how I go.

Geoff T
-- 
View this message in context: http://www.nabble.com/PerlAuthenHandler-and-ErrorDocument-401-tp17330888p17353562.html
Sent from the mod_perl - General mailing list archive at Nabble.com.


Mime
View raw message