At 09:36 09/12/2000 +0000, Matt Sergeant wrote:
>On Sat, 9 Dec 2000, Robin Berjon wrote:
>> Basically, I'm trying to some up with a way to implement custom
>> directives by applying Perl source filters in httpd.conf, but for some
>> reason it isn't working.
>
>It slipped past me on a busy day, but looks like it could work well to
>solve the segfaulting AxKit+PHP problems...
Yes that's one thing I had in mind when I started playing around with this
idea. Using a filter wouldn't allow one to do more than what is already
possible either with XS, PerlSetVar or of course <Perl>, but it would be
imho easier (both for the author and for the users that always seem to run
into problems) than XS, more powerful than PerlSetVar and would allow one
to stick to a configuration syntax more readable than Perl (which wasn't
meant to be used that way and doesn't look as obvious). Of course, some
twisted mind could always show up and implement Apache configuration in
Latin, but that's another story ;)
>I'm wondering if its something simple like the filter needs to read the
>file based on caller() in order to run the filter? I'd have to check the
>source for Filter to be certain though.
I think it's probably that <Perl> sections are eval()ed so that the filter
does not apply. That seems obvious from the fact that the filter() sub
never gets called at all, even though the filter itself is loaded,
initialised and added. Unfortunately I don't know enough about
Perl/mod_perl internals to think about a way to change this.
-- robin b.
There's too much blood in my caffeine system.
