Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <3F09A8B3.1000607@modperlcookbook.org>
Date: Mon, 07 Jul 2003 10:06:59 -0700
From: Geoffrey Young <geoff@modperlcookbook.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.1) Gecko/20020823 Netscape/7.0
MIME-Version: 1.0
To: Martin Wickman <martin@wickman.com>
CC: modperl@perl.apache.org
Subject: Re: Combining authen-handler with mod_auth
References: <20030705171548.GA23837@wickman.com>
 <3F0718B9.1040908@modperlcookbook.org> <20030705220642.GA5990@wickman.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


> Thanks!
> 
> I guess that may be possible, but somewhat problematic since I like to
> stay with the distros apache-version. Btw, I remember seeing something
> about APR_HOOK_(LAST|FIRST|...) in the docs on perl.apache.org. Not
> implemented yet?

I'm not sure what docs you're thinking about, but that change should 
be ok.  I know that I'm using those constants in some XS and all is ok.

> 
> I think a lot of interesting password policies could be implemented if
> it was possible to run perl-code before and after existing
> authentication modules. Is it feasible to add this to the current
> mod_perl as a runtime option?

runtime is not likely to be possible.  I'm considering a patch that 
would make the hook behavior configurable as a compile-time option, 
however - modperl_hooks.c is autogenerated during the config process, 
so it should be trivial to change the hook order without folks like 
you needing to patch the code yourself.

--Geoff