Although caching proxies may handle invalidation differently, the effect is always the same: the next time a client requests the data, he or she gets a new version instead of the outdated one.
Cache invalidation gives you the best of both worlds: you can have very long TTLs, so when content changes little, it can be served from the cache because no requests to your application are required.
As an alternative, Oracle Web Cache provides mechanisms for explicitly invalidating content when an administrator or application knows that such content has become stale.
With invalidation, Oracle Web Cache marks objects as invalid.
We recommend this option if you don’t want to slow down the site.
The proxy can choose to either discard the content immediately, or do so when it is next requested.As described in Section 6.7, you create expiration policies and associate them with caching rules to refresh content from the origin server.Even with expiration policies, it is often difficult to predict when exactly content becomes stale.The wildcard invalidation works very similarly to other systems, giving you the ability to use the asterisk operator (*) to specify a file pattern to invalidate.For instance, to invalidate all images you might do something like this: For my purposes, I wanted to just invalidate the entire cache to be safe, since almost all pages use the same layout and styling.If you have many assets and lots of traffic, those requests could result in a substantial increase in requests to your origin and slow down your website.