On 8 Jan 2003, Philippe M. Chiasson wrote: > Simply put, there is a small difference in behaviour (bug) in apache's > config parsing code. For now, just put > <Perl > instead of <Perl> > > Apache assumes <> containers to always have a value argument, like in > <Foo /var>. > > Will eventually be fixed though.
Thanks for pointing me in that direction. While <Perl > did not work as you suggested (produced error 'no <Perl> handler specified'), it did cause me to grep for this error message, and it is in file src/modules/perl/modperl_cmd.c. I was able to get some information from that code: mod_perl wants directive of the form <Perl handler=Some::Handler> where Some::Handler actually looks like a valid handler, i.e. has a subroutine called handler(). The module is compiled and handler() is called during config parse time. Unfortunately, I could not figure out how to set Apache directives from that subroutine. Simply setting global $ServerAdmin does not produce the desired effect. Is there a global Apache config namespace or hash? Also, my httpd.conf has things like this: <Perl> $PerlConfig = " <VirtualHost _default_:$ssl_port> # some directives here. </VirtualHost> "; </Perl> I am at a loss as to how I'd go about replicating these dynamically generated directives in the new mod_perl model. Eagerly waiting for suggestions, - Dmitri. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
