On Fri, 2 May 2008 02:41:11 -0700, Ricardo Newbery [EMAIL PROTECTED] said:
The problem with the example zope-plone.vcl is that it excludes ALL
cookie-authenticated responses -- even those inline images, css, and
javascript files that otherwise would be cacheable in downstream
caches -- making
Stig Sandbeck Mathisen wrote:
Are there any good reasons not to run Plone with the CacheFu (or
CacheSetup) product installed? Would a non-CacheFu example be of any
use?
CacheSetup monkeypatches a fair amount of things, which breaks some innocent
third party products. In general my advise
Stig Sandbeck Mathisen wrote:
On Thu, 1 May 2008 23:22:17 +0200, Wichert Akkerman [EMAIL PROTECTED] said:
I have some improvements pending for that one as well: a few
cleanups and switching to url_purge.
Would it make sense, in vcl_recv, to put the PURGE check inside the
not GET and not
On May 5, 2008, at 6:02 AM, Wichert Akkerman wrote:
Stig Sandbeck Mathisen wrote:
Are there any good reasons not to run Plone with the CacheFu (or
CacheSetup) product installed? Would a non-CacheFu example be of any
use?
CacheSetup monkeypatches a fair amount of things, which breaks some
Ricardo Newbery wrote:
On May 1, 2008, at 2:21 PM, Wichert Akkerman wrote:
Previously Ricardo Newbery wrote:
Just poking around the tracker and I noticed some activity on the
example plone vcl. http://varnish.projects.linpro.no/changeset/2634
Just thought I would chime in that the example
downstream (in my opinion, this is a bug). And if
you can't exclude it from downstream shared caches, it's rather
pointless to exclude it from the reverse proxy cache.
The problem with the example zope-plone.vcl is that it excludes ALL
cookie-authenticated responses -- even those inline images
