I don cache anything because Im afraid of end users getting out-of-date content. How can I prevent this using CacheRight?
The fear of over-aggressive caching is an understandable one, given how difficult it usually is to control how the different parts of a Web site will be cached. Faced with one-size-fits-all cache control that risks saddling users with old or wrong content, it’s hardly surprising that Web developers throw up their hands. This explains why the vast majority of objects on the Web lack basic cache control. However, ignoring the role of caches (and thus surrendering the benefits of caching) is no way to solve the problem of over-aggressive or unwanted caching. Instead, objects that shouldn’t be cached need to have cache-control headers and directives specifying immediate expiration. This doesn’t guarantee that some piece of software, somewhere, won’t try to cache them — but objects that lack the appropriate headers and directives don’t even stand a chance of being cached correctly. A better solution than giving up on cache control is to use a tool that makes it easy to implement and manage
