httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Holsman <i...@cnet.com>
Subject Re: cvs commit: httpd-2.0/modules/experimental mod_cache.c
Date Fri, 31 Aug 2001 21:36:56 GMT
On Fri, 2001-08-31 at 14:17, Bill Stoddard wrote:
> > > >
> > > > My own opinion is that the cache should be the last content filter run.
 Basically,
> > > > it should probably be specified as the first HTTP_HEADER filter type.
> >
> > not necessarily.
> > we have a situation where we need to uniquly modify outgoing HTML to
> > insert ads and tracking things into the HTML (which is different for
> > each user)
> > we would mod_cache in the middle of the content chain.
> > (ie cache the result from the CGI/proxy call) and then run a mod-include
> > filter on top of that (possibly pushing the result through gzip)
> >
> 
> Yep, you definitely need CACHE_OUT to be a CONTENT filter in this case since INCLUDES
is a
> CONTENT filter and you need INCLUDES to be run after CACHE_OUT. CACHE_OUT needs to be
the
> first CONTENT filter run (or alternately, just move the CACHE_OUT function directly into
> the handler).
> 
> When you mention inserting ads into an HTML stream, I am trying to understand how this
> works.  All the output from a page constructed with INCLUDES must be the same mime type
> (text/html, whatever). That would seem to be a considerable limitation to using SSI (or
> custom tags) to assemble pages.
we do it via custom SSI tags. 
the actual HTML image reference changes 
<!--#ad parm=.... -->

% curl www.cnet.com >a
% curl www.cnet.com >b
% diff a b
and you'll notice that HTML is slightly different in each case.
> 
> Bill
> 
> 
> 
> 
> 
> 
-- 
Ian Holsman          IanH@cnet.com
Performance Measurement & Analysis
CNET Networks   -   (415) 364-8608


Mime
View raw message