(I found a better way to do what I wanted, avoiding PerlChildInitHandler completely, but still...)
My reason for wanting PerlChildInitHandler (and PerlChildExitHandler) inside VirtualHost is to be able to keep these declarations close to the PerlHandlers that rely on them. I like to put my VirtualHost conf sections inside separate Include config files so that I can leave the main httpd.conf fairly static. If ChildInitHandler is not allowed inside VirtualHost, it should generate an exception when the config file is parsed. Instead, it silently ignores the declaration. -Jason Cees Hek wrote: >Quoting Jason W May <[EMAIL PROTECTED]>: > > > >>Running mod_perl 1.26 on Apache 1.3.24. >> >>I've found that if I place my PerlChildInitHandler inside a VirtualHost >>block, it is never called. >> >> > >It doesn't really make sense to put a PerlChildInitHandler inside a VirtualHost >directive. It is only called when the Apache Child process is created, not when >a new request comes in. > >If you explain what you are trying to accomplish, maybe we can recommend a >better Handler to tie into. > >Cees > >
