Invalidating the HTTP Cache on read only front servers
Posted
by Microserf
on Stack Overflow
See other posts from Stack Overflow
or by Microserf
Published on 2010-03-24T07:18:27Z
Indexed on
2010/03/24
7:23 UTC
Read the original article
Hit count: 302
We have a CMS system and in the production mode a number of servers only have read-only access to the content (with a few exceptions) and the editors for the site work on the content on servers behind it (which are not available to the public).
We're caching the content quite a long time on the front servers, but sometimes we want the content the editors publish to be available for visitors instantly. What would the best way be to invalidate the cache in this situation, should we trigger it from our code?
© Stack Overflow or respective owner