On Tue, 3 Apr 2001, Michael Nachbaur wrote:
> I'm having a problem with Apache::Filter (and Apache::OutputChain) which I
> don't think is related to Apache::Filter itself, but I can't seem to track
> the problem down.
>
> I wrote a content handler which outputs XML, which I want to then be
> processed by AxKit. So, I did:
>
> SetHandler perl-script
> PerlSetVar Filter On
> PerlHandler HTTPFilter AxKit
>
> The output that I get is the combination of HTTPFilter's output, and AxKit's
> output (one right before the other). So, it seems that HTTPFilter's output
> is successfully making it into AxKit (otherwise it wouldn't process its
> output correctly), but is still making its way to the browser.
>
> Any ideas?
It could be the bug in AxKit, which is fixed by 1.3_90 (and _91).
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\
