How to delete cache based on expires headers?

Indo Php iptablez at yahoo.com
Mon Dec 30 04:27:57 UTC 2013


Hi

Is that means that nginx will put the files based on the upstream expire headers? After that nginx will delete the cache files?





On Tuesday, December 24, 2013 10:28 PM, António P. P. Almeida <appa at perusio.net> wrote:
 
Why you want to do this? nginx can manage expiration/cache-control headers all by itself.

As soon as the defined max-age is set it returns a upstream status of EXPIRED until it fetches a fresh
page from upstream.

Deleting won't buy you anything in terms of content freshness.






----appa




On Tue, Dec 24, 2013 at 3:57 AM, Indo Php <iptablez at yahoo.com> wrote:

Hello..
>
>
>Can somebody help me on this?
>
>
>Thank you before
>
>
>
>On Thursday, December 19, 2013 11:21 AM, Indo Php <iptablez at yahoo.com> wrote:
> 
>Hi
>
>
>I'm using proxy_cache to mirror my files with the configuration below
>
>
>proxy_cache_path  /var/cache/nginx/image levels=1:2 keys_zone=one:10m inactive=7d     max_size=100g;
>
>
>Our backend server has the expires header set to 600secs
>
>
>Is that posibble for us to also delete the cache files located at /var/cache/nginx/image depends on the backend expire header?
>
>
>_______________________________________________
>nginx mailing list
>nginx at nginx.org
>http://mailman.nginx.org/mailman/listinfo/nginx
>
>
>_______________________________________________
>nginx mailing list
>nginx at nginx.org
>http://mailman.nginx.org/mailman/listinfo/nginx
>


_______________________________________________
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/20131229/4c8013cf/attachment.html>


More information about the nginx mailing list