On Thu, 29 Nov 2007 11:05:27 -0500 "Adam Woodworth" <mirkperl@xxxxxxxxx> wrote: > In summary (taking from the above posting), here's a simple flow of > what we have happening: > > 1 - mod_cache [..got valid content in cache? If so, go to 4; if not, > go to 2] 2 - mod_proxy [fetch content from origin web] > 3 - mod_cache [content cacheable? If so, cache it locally] > 4 - *MY FILTER* > 5 - deflate That makes sense if and only if you want to repeat your-filter and DEFLATE on every request rather than cache the ready-processed contents. In principle, mod_filter enables you to control the ordering of output filters, so you could just configure the above with a FilterChain directive. The problem with that is that mod_cache does its own thing. I suspect the easiest solution may be to use mod_cache's filters but without using mod_cache's handler. I'm not sure how much work that'll involve: presumably mod_cache can largely be cloned, except for the insert-filters bit. Doing it in Perl with mod_perl should be an option. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/ --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|