third-party CGI stuff which could benefit from mod_perl. Also, how can one
cope with third party scripts which output their "Content-type:" via usual
print STDOUT so that it doesn't pop up into the filtered pipeline in
addition to the one supplied by the Filter mechanism??
After I thought it
che::SSIChain Apache::Registry
Options +ExecCGI
PerlSendHeader On
/Directory
/VirtualHost
What can be wrong?
TIA for any hints,
Vassilii
Subject: Re: Apache::SSI pain
Author: Ken Williams [EMAIL PROTECTED]
Date: Tue, 12 Oct 1999 22:13:54 -0500
The latest versio
ndler perl-script
PerlHandler Apache::OutputChain Apache::SSIChain Apache::Registry
Options +ExecCGI
PerlSendHeader On
/Directory
/VirtualHost
What can be wrong?
TIA for any hints,
Vassilii
Subject: Re: Apache::SSI pain
Author: Ken Williams [EMAIL PROTECTED]
Date: T
However, when I use Filter as suggested in Apache::Filter(3) (see the
config snippet below), the include directive gets propagated on to the
user agent and not expanded. Try http://win.tarunz.org/test.html to see
oops. It turns out that it has been specifically stated in the docs that
The thing that works best for me is to use an Apache::SSI object myself
rather than using any kind of chaining.
my $ssi = Apache::SSI-new($text, $r);
print $q-header; # send the HTTP header
$ssi-output();
Or you can capture the output instead of just sending it, like this:
my $ssi=
I've used the lines below and the various other provided incantations for
using Apache::SSI or Apache::SSIChain.
PerlModule Apache::SSIChain
PerlModule Apache::Filter
PerlModule Apache::SSI
PerlModule Apache::OutputChain
Alias /ssiperl/ /www/perl/ssibin/
Location /ssiperl
SetHandler
