httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@algroup.co.uk>
Subject Re: BIG filtering patch.
Date Sun, 09 Jul 2000 16:00:49 GMT
Rodent of Unusual Size wrote:
> 
> rbb@covalent.net wrote:
> >
> > Okay, so how does this work?  When does a module get to insert
> > it's filter onto the stack?
> 
> IMHO, it shouldn't.  Modules should *never* insert filters on
> their own; it should be completely under the control of the
> user.  I'd expect something like:
> 
> FilterSet setname1 ssi-parse digestify
> AddFilter .cgi setname1
> 
> or maybe
> 
> AddFilter .cgi ssi-parse digestify
> 
> meaning that the output from the content handler for .cgi
> would be run through the SSI parser, and the result of *that*
> would then be passed through the digestifier.
> 
> Which means the core builds the stack.

That would preclude modules inserting filters in order to do their
tricks (i.e. where a filter is used to honour some other directive). Or
at least complicate it. This is also why the idea of using hooks for
them makes sense to me.

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

Coming to ApacheCon Europe 2000? http://apachecon.com/

Mime
View raw message