Is there nothing we can help Andreas to do to purge the caches when he does a release so Michael doesn't have to deal with everyone who gets the insufficient priveleges message? I wonder how many people are actually turning away from Zope due to the shocking state of Zope.org? cheers,
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: Tres Seaver wrote: I would bet we have cache poisoning at work here. Likely we need to get a pool of the zope-web folks who can run 'squidclient -m PURGE' to clean them out. Do you know what machine this needs to be done
This would solve which problems? Andreas --On 19. Oktober 2005 14:04:23 -0400 Jim Fulton [EMAIL PROTECTED] wrote: I'm inclined to make the Zope 2, Zope 3, and possibly the ZODB release areas totally static. This would mean that making a new release would require using the ZMI to create a
We think we understand the problem now. It is cache related. We've changed the caching policy so that the pages in question aren't cached. The problem ocurred because: - The product product has the *insane* policy that if any files aren't published, the entire product is inaccessible.
Andreas Jung wrote: This would solve which problems? We were in a state in which no one could download 2.8.3 using the widely available URLs. This is something we wrestled with when we made the 3.0 release and I was sick of it. We appear now to have this somewhat under control now. Jim
Andrew Sawyers wrote: Ok guys. I'm willing to eat a little crow on this one. I blame it on being on a lap top on prone to mucho interruptions (excuse mode off). The condition for this was actually more then the response I originally thought. When a unauthorized page is accessed on
Sidnei da Silva wrote: On Wed, Oct 19, 2005 at 03:25:11PM -0400, Jim Fulton wrote: | - The product product has the *insane* policy that if any files aren't | published, the entire product is inaccessible. | | Does anyone know how to fix this? Is there a knob for this somewhere in | CMF?