OK, so I've done some more research and found it that it's not Tomcat
that's screwy on this one; it was Cocoon 2.1.7.
First, I have a Cocoon application that I'd deployed over a year
ago... it was running on MySQL 4.0, Tomcat 5.0.21 and Cocoon 2.1.5
for a little over a year.
Due to a catastrophic hardware failure, I had to get a new machine,
so I figured it was a good opportunity to upgrade to MySQL 4.1,
Tomcat 5.5, and Cocoon 2.1.7 ... i guess I decided I was getting
bored with stuff like a full night's sleep and breathing fresh air,
or something...
Essentially, it boils down to the fact that is seems Cocoon 2.1.7 now
defaults to pipelines being caching... Once I explicitly added
<map:pipeline type="noncaching"> to the pipeline handling the errant
request, everything went back to normal.
Which is good. :-)
Thanks again to all that threw in their advice!
jL
On Oct 12, 2005, at 5:00 PM, John Lianoglou wrote:
Hey all, thanks for everyone's responses... gave me lots of stuff
to link into... and rule out.
:-)
I've noticed this: only URLs ending in *.html seem to be suffering
from the caching issue... does that trigger any ideas? I'm thinking
this may be more of a Tomcat thing than a Cocoon one.
jL
On Oct 12, 2005, at 10:25 AM, Philippe Gassmann wrote:
Ard Schrijvers wrote:
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
Are you using this request-param in your pipeline ?
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
