perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Sinelnikov" <>
Subject RE: Controlling subversion access
Date Sun, 26 Mar 2006 23:28:39 GMT
Cool, thanks Torsten!

I ended up using PerlAccessHandler. 

I ran into problems using PerlAuthenHandler, maybe because I'm using a
client certificate to authenticate the user (SSLCACertificateFile,
SSLVerifyClient directives).  Thoughts?


Log errors when trying to use PerlAuthenHandler:
[Sun Mar 26 18:07:41 2006] [error] [client] Could not fetch
resource information.  [301, #0]
[Sun Mar 26 18:07:41 2006] [error] [client] (2)No such file or
directory: Requests for a collection must have a trailing slash on the URI.
[301, #0]

-----Original Message-----
From: Torsten Foertsch [] 
Sent: Sunday, March 26, 2006 3:02 PM
Subject: Re: Controlling subversion access

On Sunday 26 March 2006 21:37, Dennis Sinelnikov wrote:
> Right, read the doc over 20 times already :)
> It could be my environment or the client cert I'm using.
> I did try different environment configurations (i.e. older openssl
> versions). I got tired of looking through apache's c code and
> openssl code, to see if I could pinpoint where the problem is.
> In any case, it wasn't getting set while I know UID is there
> because I see it when I log the full DN.
> So that's why I decided to go mod_perl route, which I like b/c
> I have more control and flexibility, plus the best part --
> I'm learning mod_perl in the meantime :)

Well, if you want to do it in Perl you need to write a PerlAuthenHandler to 
set $r->user. To access mod_ssl variables at this stage you need 
Apache2::ModSSL or Apache::SSLLookup.


View raw message