perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin A. McGrail" <>
Subject Re: Apache 2.4 and AAA
Date Fri, 29 May 2015 18:07:26 GMT
On 5/29/2015 1:52 PM, André Warnier wrote:
> Kevin A. McGrail wrote:
>> On 5/29/2015 1:20 PM, André Warnier wrote:
>>> Over the years, I have created and modified and re-modified my own 
>>> Apache/mod_perl authentication module, which was originally derived 
>>> from Apache(2?)::AuthCookie (pilfered would be the correct term I 
>>> guess).
>>> It currently runs up to Apache 2.2, but I have heard/read in various 
>>> places that the Apache AAA interface had been changed significantly 
>>> in 2.4.
>>> I figure that I should thus start updating my module, before all my 
>>> customers update their Apache and make my module obsolete.
>>> But although I have seen many warnings about the changes, I have not 
>>> really see yet any real outline of the changes in mod_perl AAA API 
>>> calls, that would likely have to be made to accomodate this.
>>> Would anyone have more info or pointers on that general subject ? 
>> Sounds like a good time to read 
>> and to 
>> play with the 2.0.9-rc2 (they discussed releasing it today...)
>> Beyond that, I don't know that anyone will have any specific input 
>> without seeing the module and what errors you are having with 
>> 2.4/mp2.0.9rc1 or rc2.
> Thank you for the pointer.
> I read it, but that is of the same order as what I was mentioning 
> above : it discusses the internal changes to Apache httpd, from the 
> point of view of, for example, the developers of mod_perl themselves.
> My own module does not interface directly with Apache at the C level. 
> I merely use the methods/functions available in mod_perl, as described 
> here for example :
> Have these functions changed ?
> And if yes, do you know if any updated mod_perl documentation exists 
> about that ?
> Or, better yet, has the interface to these functions not changed, the 
> dirty work having already been done by the mod_perl developers to make 
> this update totally transparent (which of course I would love) ?
> My module hasn't come up with any error yet with Apache 2.4, for the 
> simple reason that I have not tried it yet with Apache 2.4.  I am just 
> trying to be prepared. 
Well, if you look at and, you'll see 
how the documentation rippled down from 2.4 to MP and how I implemented 
$c->client_ip instead of $c->remote_ip

So while I understand you are writing in perl, the documentation at about the 
changes is a good starting point.  It's what I used to make my first 
pass at a fix for the code on SpamAssassin that used it. Beyond that, 
support for httpd 2.4 in mod_perl is in release candidate with the first 
release candidate about 1 week old so I'm not aware of more 
documentation.  But without A) seeing your module or B) having any 
errors to comment on, not really sure there is much more to go on.

Anyway to answer your issue, looking at Apache2::Access in mod_perl 
2.0.9rc1, my belief is that it's essentially going to provide a buffer 
between your version of Apache so those calls won't change whether it's 
2.2 or 2.4.

Highly recommend you compile 2.0.9 rc1 or rc2 and a version of 2.4 and 
test it.  If you find an issue, it might even be fixable before 2.0.9 is 
released which is the first official MP support for httpd 2.4.


View raw message