On Mon, 17 Nov 2003, Christopher P. Lindsey wrote:
> Hi,
>
> I sent out an email yesterday describing some problems that I'm having
> with Apache::SSI. I've narrowed things down significantly and hope that
> this extra info can help someone point me in the right direction.
>
> Basically, it all boils down to the fact that once an SSI directive
> with #EXEC CGI is parsed, the document fails to parse any further
> SSI directives *if the script to be executed has a perl-script
> handler.*
>
this is a documented "feature"
from the manpage:
=head1 CAVEATS
* When chaining handlers via Apache::Filter, if you use <!--#include
...-->
or <!--#exec cgi=...-->, then Apache::SSI must be the last filter in the
chain. This is because Apache::SSI uses $r->lookup_uri(...)->run to
include
the files, and this sends the output through C's stdout rather than Perl's
STDOUT. Thus Apache::Filter can't catch it and filter it.
for a way around this, see recipe 10.2 in the mod_perl developer's
cookbook:
http://www.modperlcookbook.org/code/ch10/Cookbook/SSI.pm
you can also try Apache::FakeSSI (includes with Apache::SSI) but I haven't
tried it myself.
HTH
--Geoff
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
