Re: FW: problem with AddOutputFilterByType directive

2002-02-20 Thread Ian Holsman
Justin Erenkrantz wrote: > On Tue, Feb 19, 2002 at 03:27:04PM -0800, Ryan Bloom wrote: > >>We have a function, ap_pass_brigade(), which is called by every content >>generator, by definition. Just put a hook into that function. >> > > And have that hook called every time data is sent through a >

Re: FW: problem with AddOutputFilterByType directive

2002-02-19 Thread Justin Erenkrantz
On Tue, Feb 19, 2002 at 03:27:04PM -0800, Ryan Bloom wrote: > We have a function, ap_pass_brigade(), which is called by every content > generator, by definition. Just put a hook into that function. And have that hook called every time data is sent through a filter (also output filters call ap_pa

FW: problem with AddOutputFilterByType directive

2002-02-19 Thread Ryan Bloom
> On Mon, Feb 18, 2002 at 09:17:19PM -0800, Ian Holsman wrote: > > it doesn't do what it is supposed to do ALL the time. > > > > for example.. take mod-status. > > > > inside the handler it decides what type of content-type > > the program will return. > > "bad module, fix module." That's bogus.

Re: problem with AddOutputFilterByType directive

2002-02-18 Thread Justin Erenkrantz
On Mon, Feb 18, 2002 at 09:17:19PM -0800, Ian Holsman wrote: > it doesn't do what it is supposed to do ALL the time. > > for example.. take mod-status. > > inside the handler it decides what type of content-type > the program will return. "bad module, fix module." > this filterconfig won't be

problem with AddOutputFilterByType directive

2002-02-18 Thread Ian Holsman
sorry.. my mailer is being a royal pain.. so I just noticed this commit. I've got a issue with this. it doesn't do what it is supposed to do ALL the time. for example.. take mod-status. inside the handler it decides what type of content-type the program will return. this filterconfig won't be