I think it is only problem with content filters (as mod_deflate filter), not with request filters.
Regards Yehezkel -----Original Message----- From: Ruediger Pluem [mailto:[email protected]] Sent: Tuesday, May 24, 2011 9:09 AM To: [email protected] Subject: Re: svn commit: r1103315 - /httpd/httpd/trunk/modules/filters/mod_deflate.c On 05/23/2011 06:11 PM, Justin Erenkrantz wrote: > On Mon, May 23, 2011 at 6:00 AM, Graham Leggett <[email protected]> wrote: >> On 23 May 2011, at 5:57 PM, Justin Erenkrantz wrote: >> >>> mod_dav uses r->output_filters - but, the pointer never gets updated >>> when it is the first one in the chain. Hence, we call mod_deflate all >>> the time even on a request that can't support it - so we have to avoid >>> repeated memory allocations in that case. -- justin >> This sounds like a general problem though, are other modules potentially >> affected? > > Yes - this why I said in my earlier post that we'd likely need to > re-architect filters to deal with it. -- justin > > Indeed this sounds like a general problem, but ap_remove_output_filter does adjust r->output_filters if f->r is set and the filter is the first one in the chain. Which responses exactly suffer from this behaviour? Regards Rüdiger
