On August 27, 2002 03:32 pm, Randy Kobes wrote: > > Thats close to what I want to do, but as the existing code has its entry > > already in the webserver config. > > > > What I mean is something like "$r->next(mod_include); OK;" > > or items to that effect. > > > > Is there a direct apache api hook I can use to tell the system to call > > mod_include with the current content? > > The Apache-WinBitHack module, available through > http://www.modperlcookbook.org/download/, may do something > similar to what you want - after it's through, it does > $r->handler('server-parsed'); > return OK; > to let mod_include pick things up from there.
Darn. After reading what handler does, its not quite what I need. It would send the whole request to mod_include. as the uri is a virtual one handled entirely in the perl module, there's no file for mod_include to jump on. I was trying to avoid Apache::SSI and its brethren, and just jump back into mod_include. It appears after Yet Another rereading of the apache.pm doc, that since mod_perl normally hooks into almost all request phases, this kind of functionality is not really there. Its assumed on the part of the mod_perl code that if you are in mod_perl you'll want to stay there, not post process with other modules. I'm using mod_gzip and it hooks into a very late phase that mod_perl leaves alone. My config includes an item: mod_gzip_item_include handler ^perl-script$. Which, if I understand it, instructs gzip to process output of that named handler. I guess I'm kind of asking for a way to tell mod_include to participate after the perl handler has returned. And if I understand mod_include, it doesn't want to participate that late. Thanks for the pointers, all. It looks like I'm stuck with Apache::SSI or DIY. Right now I'm DIY, and after getting bitten by a bug I thought I could just use mod include and avoid these kind of bugs in the future. -- Jay "yohimbe" Thorne [EMAIL PROTECTED] Mgr Sys & Tech, Userfriendly.org
