httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Plüm, Rüdiger, VF-Group" <>
Subject RE: HTTPD upgraded on eos -> 2.3.8
Date Wed, 25 Aug 2010 08:05:01 GMT

> -----Original Message-----
> From: Nick Kew [] 
> Sent: Mittwoch, 25. August 2010 09:02
> To:
> Subject: Re: HTTPD upgraded on eos -> 2.3.8
> On 25 Aug 2010, at 07:41, Paul Querna wrote:
> > Grump old man mode, this seems moderately disturbing.
> > 
> > Previously it was single hash table look up on the 
> content-type, which
> > contained a list of all filters to apply.
> With lots of brokenness, discussed quite a few times over the years.
> This was a long-overdue round tuit.  PR 33499 isn't the best 
> reference,
> but is the first one to come up on a bugzilla search.
> > It has been replaced with iterating all possible filters 
> and executing
> > an the expression parser for each possible filter.
> You make that sound a lot.  How many lookups can you envisage
> in any case that *would work at all under the old implementation*?
> > Is anyone else surprised at this change?  I did a quick search on
> > dev@, and I couldn't find any previous discussion of this change....
> IIRC it was first suggested as an alternative to removing
> AddOutputFilterByType altogether from 2.1/2.2, over five years ago.

I remember these discussions as well (sorry no detailed pointers) that
AddOutputFilterByType was broken and that it should be removed or fixed.
It is even marked a deprecated in the Apache 2.2 documentation for 2.2
This is an approach to get it fixed. And currently I think it is a
good approach

1. Since it allows the continued use of AddOutputFilterByType just by
   loading mod_filter.
2. It is easier to configure then to use native mod_filter syntax.

But yeah, there might be implementations that work and that have less
overhead. But so far nobody felt an urge to implement them.



View raw message