FRiCKLE/ngx_cache_purge
Freenginx module which adds ability to purge content from FastCGI, proxy, SCGI and uWSGI caches.
FreeFree tier
About FRiCKLE/ngx_cache_purge
ngx_cache_purge is an nginx module that enables purging of cached content from FastCGI, proxy, SCGI, and uWSGI caches. It supports both same-location and separate-location syntax for flexible configuration, and allows IP-based access control to restrict purge requests. The module is production-ready and comes with a complete test suite based on Test::Nginx. Licensed under a BSD-like license, it was originally funded by yo.se.
Key Features
Purge content from FastCGI, proxy, SCGI, and uWSGI caches
Same-location and separate-location configuration syntax
IP-based access control for purge requests (from specific IPs or all)
Method-based purge activation (e.g., PURGE method)
Production-ready status with complete test suite
Supports cache key specification in separate-location mode
Integration with standard nginx cache directives (proxy_cache_path, etc.)
Pros & Cons
Pros
- Production-ready and stable module
- Supports multiple cache backends (FastCGI, proxy, SCGI, uWSGI)
- Flexible configuration with both same-location and separate-location syntax
- IP-based access control enhances security for purge requests
- Complete test suite ensures reliability
- Open source with permissive license
Cons
- Requires compilation as an nginx dynamic module or static build
- Only works with nginx web server
- No built-in web interface for cache management
- Limited to the supported cache backends (no memcached, Redis, etc.)
- Documentation is primarily the README and code comments
Best For
Cache invalidation for dynamic web content served by nginxPurge specific pages or resources after content updatesAdmin cache management for web applicationsIntegration with content management systems for immediate cache clearing
FAQ
Is ngx_cache_purge production-ready?
Yes, the module is marked as production-ready on its GitHub repository.
What cache backends does ngx_cache_purge support?
It supports FastCGI, proxy, SCGI, and uWSGI caches.