> 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
> 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
Apach
Hi, I have had a similar problem and didn't overcome it.
I am running apache 1.3.6 and the latest Bundle::Apache, mod-perl-1.21
and Apache::SSI-2.08 (all the dependants are from yesterday's CPAN).
When I use the (deprecated according to this Ken's message)
Apache-OutputChain-0.07, I also have the
I just hacked the into Apache::SSI (v. 2.08) because I
desperately needed it,
and I am submitting this to Ken so that he can incorporate it into the
future Apache::SSI release.
I didn't make anything to handle the echo_... stuff printing the time --
it is currently unaffected by (To do that,
on
I think you can do better doing XML-oriented research here first before you dig
into apache/mod_perl if you don't find some quick solutions. Here are some
leads. I don't go deeper -- we're here for mod_perl, check out comp.text.sgml
and the SGML/XML home page at oasis.
http://www.oasis-open.org/co
