Forgot your password?
New user?
Document Actions
#5: Purge action for cached urls
- Contents
We should have a link somewhere on each page which allows its' cache to be forcibly purged / refreshed.
- Proposed by
- Justin Ryan
- Seconded by
- Geoff Davis
- Proposal type
- Architecture
- Repository branch
- trunk
- State
- being-discussed
Motivation
Sometimes the cache gets out of sync, for various reasons, possibly even bugs at times, and content managers and/or site visitors need a way to force updated content into the cache.
Assumptions
I assume that it is still possible to purge in real-time, as I recall Geoff explaining to me some time ago that Sidnei da Silva rewrote the purge code to be asynchronous.
Proposal
A link for purging a given url needs to be placed somewhere nonchalant on the page - possibly in the footer?
Implementation
Not exactly sure yet. ;)Deliverables
- A simple modification to, say, the footer to link with a GET argument against the current url.
- A hook for CMFSquidTool to directly purge any url which receives
this GET argument and matches a given security role or permission.
Risks
It could open a site to attacks, both by emptying cache and by overloading zope with purge requests, and should be optional behaviour which can be access-controlled using zope security.
Progress log
I think this is a Good Idea(tm), Geoff agrees. Here we are.
Participants
Justin Ryan (bitmonk/justizin)
