# Ngx\_cache\_purge-2.1

**URL:** <https://www.ruby-forum.com/t/ngx-cache-purge-2-1/227567>\
**Category:** NGINX\
**Created:** [March 19, 2013, 6:14pm UTC](https://www.ruby-forum.com/t/ngx-cache-purge-2-1/227567 "2013-03-19T18:14:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![piotrs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/ee59a6/32.png) [@piotrs](https://www.ruby-forum.com/u/piotrs)\
**Post date:** [March 19, 2013, 6:14pm UTC](https://www.ruby-forum.com/t/ngx-cache-purge-2-1/227567/1 "2013-03-19T18:14:25Z")

</div>

Version 2.1 is now available at:  
[http://labs.frickle.com/nginx\_ngx\_cache\_purge/](http://labs.frickle.com/nginx_ngx_cache_purge/)

GitHub repository is available at:

> **[GitHub - FRiCKLE/ngx\_cache\_purge: nginx module which adds ability to purge...](https://github.com/FRiCKLE/ngx_cache_purge/)**
>
> nginx module which adds ability to purge content from FastCGI, proxy, SCGI and uWSGI caches. - GitHub - FRiCKLE/ngx\_cache\_purge: nginx module which adds ability to purge content from FastCGI, proxy...

Changes:  
2013-03-19 VERSION 2.1  
\* When enabled, cache purge will now catch all requests with  
PURGE (or specified) method, even if cache isn’t configured.  
Previously, it would pass such requests to the upstream.

Best regards,  
Piotr S. \< removed\_email\_address@domain.invalid \>