[Grok-dev] Strange session / security problem with Grok 0.14

Ivo van der Wijk vladdrac at gmail.com
Fri Jan 16 12:50:00 EST 2009

2009/1/16 Martijn Faassen <faassen at startifact.com>:

>> If you every run into a similar issue, make sure you're not using
>> mod_cache. Heck, make sure you're not using mod_cache at all :)
> Is that conclusion because of mod_cache's seemingly rather bad
> misbehavior or are there yet more reasons not to use mod_cache? :)

I remember from the early days of apache 2.0 that mod_cache was
experimental (but supposed to be better than the caching mess in 1.x).
I haven't played with it since - Squid has always been way better, but
now that I've put some more research into mod_cache I've heard it just
doesn't do its job very well. It lacks fine grained configuration,
caches too agressively, etc.

Perhaps there are setups where mod_cache makes sense but I don't think
apache in front of Zope / Zope3 is one.

And its current behaviour in this setup confirms this.



Drs. I.R. van der Wijk / m3r Consultancy B.V.
Linux/Python/Zope/Plone and Open Source solutions
PO-box 51091, 1007 EB Amsterdam, The Netherlands
Email: ivo <at> m3r.nl Web: http://m3r.eu/

More information about the Grok-dev mailing list