rukbat

Hpatoio

Each time an element of your blog is modified (post, page, media, custom post) its cached version, and of all the related elements (categories, archives and custom taxonomies) are deleted.
In this way your cache has always the latest version of the page.
Extra :
<ul>
<li>Two extra HTTP header are added to the response so that you can see if the page you are viewing is cached and when it was cached.</li>
<li>A logging system allow you to see which page were cached and when.</li>
<li>You can add personal URLs to be purged when the post is modified</li>
<li>Purge of future posts is handled with an external script.</li>
<li>Integration with NextGEN Gallery plugin.</li>
</ul>
Credits :
<ul>
<li>This plugin is based on the structure of famous NextGEN Gallery plugin.</li>
</ul>

NGINX Manager

Easily purge Nginx cache. Each time a post is modified clear the cached version of the page and of all the related page.

myros

One common method of caching content for websites is via the use of reverse proxy caching. Common examples of this are <a href="https://www.varnish-cache.org/" rel="nofollow ugc">Varnish</a> and <a href="https://www.nginx.com/" rel="nofollow ugc">Nginx</a>. These systems allow a website to update content and have the visitor’s experience cached without the need for complex plugins storing the files locally and using up a user’s disk space.
The Remote Cache Purger plugin sends a request to delete (aka flush) the cached data of a page or post to remote server(s).
<h4>How It Works</h4>
Manually

Remote Cache Purger

Plugin will empty remote server's cache content (only NGINX at this moment). Plugin Features Purge cache on multiple NGINX servers Cache can b …

NGINX Manager vs Remote Cache Purger