John D Groenveld wrote:
> In message <[EMAIL PROTECTED]>, Geoffrey Young writes:
>
>>if ($authenticated) {
>> return OK
>>}
>>else {
>> $r->push_handlers(PerlFixupHandler => \&manage_cache);
>>}
>
>
> Thank you! This is working out very well. Clean and straightforward.
excellent.
>
> My he
In message <[EMAIL PROTECTED]>, Geoffrey Young writes:
>if ($authenticated) {
> return OK
>}
>else {
> $r->push_handlers(PerlFixupHandler => \&manage_cache);
>}
Thank you! This is working out very well. Clean and straightforward.
My head was so deep in Chris and Jason's hacks around the weird
John D Groenveld wrote:
In message <[EMAIL PROTECTED]>, Stas Bekman writes:
If the logic has to be more flexible, you could get_handlers(), look at who's
registered and then decide based on that whether to return OK or DECLINED?
In Apache::AuthenDumb, how do I go from the CODE refs returned
fro
John D Groenveld wrote:
> In message <[EMAIL PROTECTED]>, Stas Bekman writes:
>
>>If the logic has to be more flexible, you could get_handlers(), look at who's
>>registered and then decide based on that whether to return OK or DECLINED?
>
>
> In Apache::AuthenDumb, how do I go from the CODE r
In message <[EMAIL PROTECTED]>, Stas Bekman writes:
>If the logic has to be more flexible, you could get_handlers(), look at who's
>registered and then decide based on that whether to return OK or DECLINED?
In Apache::AuthenDumb, how do I go from the CODE refs returned
from $r->get_handlers('Perl
> thus AuthenCache (and others that relied on the incorrect RUN_ALL meme in
> authentication and translation) will need to be rewritten. I'm really sorry
> about that, but mp2 finally gets it right, which is better for everyone in
> the long run. in particular it should make the logic in Authen
John D Groenveld wrote:
> In message <[EMAIL PROTECTED]>, Stas Bekman writes:
>
>>Why can't you return DECLINED?
>
>
> The compelling part of AuthenCache under MP1 was that you got caching
> for existing authentication modules w/o code modification.
the auth phases are RUN_FIRST now for a re
In message <[EMAIL PROTECTED]>, Stas Bekman writes:
>Why can't you return DECLINED?
The compelling part of AuthenCache under MP1 was that you got caching
for existing authentication modules w/o code modification.
John
[EMAIL PROTECTED]
--
Report problems: http://perl.apache.org/bugs/
Mail lis
John D Groenveld wrote:
I'm trying to port AuthenCache to MP2, but hitting a wall, the stacked handler
behavior differences.
http://perl.apache.org/docs/2.0/user/handlers/intro.html#toc_C_RUN_FIRST_>
Is there an easy way to change PerlAuthenHandler's behavior to RUN_ALL
so that my authen module can
I'm trying to port AuthenCache to MP2, but hitting a wall, the stacked handler
behavior differences.
http://perl.apache.org/docs/2.0/user/handlers/intro.html#toc_C_RUN_FIRST_>
Is there an easy way to change PerlAuthenHandler's behavior to RUN_ALL
so that my authen module can return OK and AuthenCa
10 matches
Mail list logo