Invalidate just one page under a location directive.

[Quintin Par]

Invalidate a cache page using the bypass mechanism proxy_cache_bypass, not
expiration

To put it simply, Invalidate cache for  a particular key entry but not all
of the cache

e.g for

location = /vehicles {

proxy_cache_key         $request_uri;

}

Hashtable for cache:

[

http://jj.com/vehicles/cars => cached page for cars

http://jj.com/vehicles/bus => cached page for bus

http://jj.com/vehicles/bike=> cached page for bike
+ 10,000 key, values
]

I should be able to invalidate just "cars" because my page for cars have
changed but not others. Say a person added a comment in the cars page.
Another analogy is to invalidate cache for a single blog post when all the
blog posts have been cached under a single location directive.
-Quintin

On Wed, Feb 8, 2012 at 9:45 PM, António P. P. Almeida <appa at perusio.net>wrote:

> On 8 Fev 2012 15h59 WET, quintinpar at gmail.com wrote:
>
> > Can someone help? My small site on a tiny VM is being bombarded and
> > the cache invalidation is clearing up everything. Which means
> > warming up the caching takes a lot of expensive queries.
>
> What cache invalidation? What caching strategy are you using?
> Are working with a content based expiration logic or from a
> microcaching perspective?
>
> You can inspect the cache using a small shell script:
>
> https://github.com/perusio/nginx-cache-inspector
>
> --- appa
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120208/c71997c2/attachment.html>