Purging and banning — Varnish version trunk documentation
One of the most effective way of increasing your hit ratio is to
increase the time-to-live (ttl) of your objects. But, as you're aware
of, in this twitterific day of age serving content that is outdated is
bad for business.
The solution is to notify Varnish when there is fresh content
available. This can be done through three mechanisms. HTTP purging,
banning and forced cache misses. First, let me explain the HTTP purges.
A purge is what happens when you pick out an object from the cache
and discard it along with its var
Additional text has been truncated due to copyright reasons. Things without URLs and private things don't get truncated.