It didn’t happen that way unfortunately. The handler was called once for each
require. Maybe I was doing something wrong.
> On Dec 22, 2015, at 5:19 PM, André Warnier (tomcat) wrote:
>
> The way in which I understand the pod and the code, is that you don't have to
> do anything to get the requ
The way in which I understand the pod and the code, is that you don't have to do anything
to get the requires as a list/array : they just come that way.
The first element of the array seems to be the "keyword" (like "user" in "Require user xxx
yyy" etc.), and the following list elements are then
Hi Sergei.
My turn to thank you for providing the information below (and also to Michael Schout of
course). That will also be invaluable to me, when I get around to update my own mod_perl
AAA modules.
On 22.12.2015 17:57, Sergei Gerasenko wrote:
Yep, I can see what I should do now. For the be
Yep, I can see what I should do now. For the benefit of others here are the
differences:
OLD STYLE
=
PerlAuthzHandler YOUR_MODULE->YOUR_METHOD
require user fred
require group fred
```
Then in your YOUR_METHOD you would do something like:
my $requires = $r->requires
process
Hi André,
This is definitely going to be helpful. I was considering just accessing
the raw config values, but could only find dir_config that remotely
resembled what I needed.
I ended up introducing a custom directive, but that's clunky in my opinion.
So, Apache2::Directive is already a big improv
Hi.
I don't have anything very precise to tell you, but here is what I know :
The AAA part has been significantly changed in Apache httpd 2.4, as compared to
2.2.
Therefore I suspect - but I am not sure - that some corresponding changes had to be made
in mod_perl, to adapt to these changes.
One
