>-----Original Message-----
>From: Ken Williams
>To: 'Surat Singh Bhati'
>Cc: [EMAIL PROTECTED]
>Sent: 3/17/01 12:42 PM
>Subject: RE: enable normal SSI for output of mod_perl script
>
>[EMAIL PROTECTED] (Geoffrey Young) wrote:
>>Surat Singh Bhati [mailto:[EMAIL PROTECTED]]
>>> Hi,
>>>
>>> I want to filter/process some files using my own
>>> handler as:
>>>
>>> <Location /foo>
>>> SetHandler perl-script
>>> PerlHandler Apache::Myprocessing
>>> </Location>
>>>
>>> Now, beofre sending the output of above handler to browser, I want
>>> to process it as normal server-parsed (i. e. apache should search for
>>> the SSI tags like <!--#exec cgi="/abc.cgi"--> , process them, and
>>> serve the final output to the browser.
>>
>>well, you can almost do this with Apache::SSI and Apache::Filter, but
>>Apache::SSI can't filter #exec or #include tags.
>
>That won't be a problem in this case, since the SSI tags are the last
>thing to happen before the page is sent to the browser. Just wanted to
>make sure it was clear that Apache::SSI does support "#exec cgi" and
>#include, it's just that Apache::Filter can't capture that output and
>let someone else filter it. Note that "#exec cmd" is fine.
right - sorry I wasn't clear. I mistakenly thought he wanted to filter SSI
-> MyProcessing and just wanted to warn him about using those two tags in
the middle of the chain...
my appologies...
--Geoff
