The biggest problem is you cannot use `proxy_cache_purge` unless you pay for the commercial version/fork of nginx.
That means you can't expire the cached content by URL.
back
1 comments
Doesn't this open-source module do the same thing: http://labs.frickle.com/nginx_ngx_cache_purge/
It seems odd for nginx to try to commercialise such basic parts of the stack where 3rd parties can easily write such functionality.
A nice feature from the commercial nginx purge package is that it lets you purge by prefix. That's a feature that I've not seen in any of the open source purge modules.
If you are hosting data for several users on the same nginx cache and you want to purge only one of them, your only options are to scan the full cache on disk and delete the files that have a key with your prefix, or fork >$1K/year per nginx box for the commercial license.