Re: Allowing modules to add input filters is broken

[Graham Leggett]

Greg Stein wrote:

> The output filters should *always* run, if at least to send an EOS bucket.
> That EOS is actually what triggers the delivery of the headers to the
> network (or at least to the CORE filter for output buffering into the next
> request).
> 
> So if you're not seeing output filters run, then a bug exists.
> 
> (IOW: theory says you're doing the right thing)

Hmmm - it looks like the bug is with proxy... if there is a 304
response, proxy simply exits the content handler without passing
anything up the stack. As a result, none of the filters run - will fix.

Regards,
Graham
-- 
-----------------------------------------
[EMAIL PROTECTED]                "There's a moon
                                        over Bourbon Street
                                                tonight..."

S/MIME Cryptographic Signature