4 ms·
Because until 0.7 nginx lacked a caching system, and so it made sense to use both. Now it doesn't.
by zepolen 16y ago
Because until 0.7 nginx lacked a caching system, and so it made sense to use both. Now it doesn't.
- bjpirt 16y agoAnd even now there's no way of manually expiring a cached page without using a third party unsupported plugin (IIRC) I still love Nginx though :-)
- piotrSikora 16y agoI'm the author of ngx_cache_purge [1]. Would you mind explaining why do you think that it's "unsupported"? This module is fully maintained, it works with every recent nginx release and supports purging content from cache of every upstream supported by nginx (FastCGI, proxy, SCGI, uWSGI). [1] http://labs.frickle.com/nginx_ngx_cache_purge/ http://labs.frickle.com/nginx_ngx_cache_purge/