I know, but of course, not all pipelines are cached within 1 single cache key. What I mean to say, is that for the "expires" pipelines, in the cache key the parameters are not represented. So URLs with different parameters, like ?page=1 and ?page=2 behind it, will be cached within the same key, and will thus return the same cached page.
So when I mentioned parameters, I am not talking about the <parameter name="cache-expires" value="180"/>, but parameters in the URL > -----Original Message----- > From: Philippe Gassmann [mailto:[EMAIL PROTECTED] > Posted At: woensdag 12 oktober 2005 14:22 > Posted To: Cocoon User List > Conversation: Unintentional Caching with Tomcat 5.5.x > Subject: Re: Unintentional Caching with Tomcat 5.5.x > > > Ard Schrijvers wrote: > > >I noticed the "expires" pipelines to ignore pararameters. > Just set your logging and look for the cache key generated > for the first request. If paramters are not represented in > the cache key, then for example > >http://........?page=1 > >http://........?page=2 > > > >will return the same cache key, and thus the same cached > page. I don't know the behavior for caching pipelines, but > for expires pipelines, the request paramater won't be > included in the key. > > > >AS > > > > > "expires" pipeline return the same caching key until it expires ;) > > This kind of pipeline is cached for a precise amount of time. > > You can configure in you sitemap it with : > > <map:pipe name="expires" > src="org.apache.cocoon.components.pipeline.impl.ExpiresCaching > ProcessingPipeline"> > <parameter name="cache-expires" value="180"/> <!-- Expires in > secondes --> > </map:pipe> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
