Takayuki Miyauchi

AMIMOTO

wokamoto

emaildano

<p>This plugin provides some functions of controlling Nginx proxy server cache.</p>
<h4>Security</h4>
<ul>
<li>Making comment authors’ information ajaxed to prevent the information from caching.</li>
<li>Send no-cache header on password protected posts to prevent the posts from caching.</li>
<li>When a scheduled post is published, it will delete the cache through Ajax.</li>
</ul>
<h4>Controlling cache</h4>
<ul>
<li>Sending X-ACCEL-EXPIRES, you can specify the available period of the cache.</li>
<li>When you save your post and someone post comments, the cache is deleted automatically.</li>
<li>Add a menu on the admin bar to delete the cache.</li>
</ul>
<h4>Memo</h4>
<ul>
<li>Gets comment poster’s IP address by HTTP_X_FORWARDED_FOR header.</li>
<li>Fixes the issue that the permanent link setting includes index.php.</li>
<li>When the cache’s expiration period is more than 86400 sec, change the value of wp_verify_nonce() same as the period.</li>
</ul>
<h4>WP-CLI Support</h4>
<p>Flush all proxy caches.<br />
    wp nginx flush</p>
<p>Show list of all proxy caches.<br />
    wp nginx list –format=csv</p>
<pre><code>wp nginx list --format=json
</code></pre>
<p>See help.<br />
    wp help nginx</p>
<h4>Languages</h4>
<ul>
<li>English(en) – <a href="http://tekapo.com/" rel="nofollow ugc">JOTAKI Taisuke</a></li>
<li>Japanese(Ja) – <a href="http://tekapo.com/" rel="nofollow ugc">JOTAKI Taisuke</a></li>
<li>Vietnamese(vi) – <a href="http://bizover.net/" rel="nofollow ugc">Trong</a></li>
</ul>
<h4>Contributor</h4>
<ul>
<li><a href="http://ninjax.cc/" rel="nofollow ugc">Ninjax Team</a></li>
<li><a href="https://profiles.wordpress.org/miyauchi/" rel="nofollow ugc">miyauchi</a></li>
<li><a href="https://profiles.wordpress.org/wokamoto/" rel="nofollow ugc">wokamoto</a></li>
<li><a href="https://profiles.wordpress.org/gatespace/" rel="nofollow ugc">gatespace</a></li>
</ul>
<h3>Credits</h3>
<p>This plug-in is not guaranteed though the user of WordPress can freely use this plug-in free of charge regardless of the purpose.<br />
The author must acknowledge the thing that the operation guarantee and the support in this plug-in use are not done at all beforehand.</p>
<h3>Contact</h3>
<ul>
<li>https://github.com/miya0001/nginx-champuru</li>
</ul>


Nginx Cache Controller

It is great to be attentive the cache control.
Thanks.



Nice plugin

nice plugin

Provides some functions of controlling Nginx proxy server cache.

Managedserver.it

<p><strong>MSCache Varnish Purge</strong> helps WordPress administrators purge the Varnish cache for sites running behind a Varnish HTTP reverse proxy. It is developed by <a href="https://managedserver.it" rel="nofollow ugc">Managed Server S.r.l.</a> and provides settings for configuring the Varnish connection, automatic cache invalidation when content changes, and manual purge tools available from the WordPress admin area.</p>
<p>This plugin is useful when your WordPress site sits behind Varnish and you need cached pages to be invalidated after content is published or updated, or on demand. It requires a reachable Varnish instance whose VCL is configured to accept PURGE requests from the WordPress server (see the FAQ for a reference VCL).</p>
<p>The settings page is available at <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> MSCache Varnish Purge</strong>. On WordPress Multisite, shared connection settings are configured at <strong>Network Admin <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> MSCache Network</strong>, while each site keeps its own purge options.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Asynchronous raw socket PURGE</strong> — sends PURGE requests via a direct TCP socket (fsockopen) without waiting for the Varnish response, so the purge request does not block the WordPress request.</li>
<li><strong>Automatic purge on content changes</strong> — when a post, page, or custom post type is published, updated, trashed, or deleted, the plugin automatically purges the affected URLs including the post itself, home page, categories, tags, author archives, and date archives.</li>
<li><strong>Full cache purge</strong> — supports multiple methods for purging the entire cache: PURGE wildcard, PURGE custom path, or BAN with configurable header.</li>
<li><strong>Additional URLs</strong> — define a list of extra paths to purge alongside content changes or on demand.</li>
<li><strong>Exclusion patterns</strong> — define glob or regex patterns for URLs that should be excluded from caching. Matching requests receive the <code>ms-cache: excluded</code> HTTP header, which can be used by Varnish to skip caching.</li>
<li><strong>Admin bar integration</strong> — quick-access purge buttons in the WordPress admin bar: Purge All, Purge Home, Purge Current Page.</li>
<li><strong>Bulk and row actions</strong> — purge cache for selected posts/pages directly from the list table.</li>
<li><strong>Debug logging</strong> — optional logging of all purge operations to a protected log directory.</li>
<li><strong>PHP 7 and PHP 8 compatible</strong> — works on PHP 7.0 through PHP 8.x without deprecation warnings.</li>
</ul>
<h4>How It Works</h4>
<p>The plugin opens a raw TCP socket to your Varnish server and sends an HTTP PURGE request with the appropriate Host header. The socket is closed immediately after writing the request — the plugin does <strong>not</strong> wait for Varnish to respond. This “fire and forget” approach is designed to avoid blocking the WordPress request while the purge is processed.</p>
<h4>External Services</h4>
<p>This plugin optionally connects to the following external services when configured by the administrator:</p>
<p><strong>Cloudflare API</strong> — When the Cloudflare integration is enabled, the plugin sends cache purge requests to the Cloudflare API v4 (<code>https://api.cloudflare.com/client/v4/</code>) to synchronize Varnish cache invalidation with Cloudflare CDN edge cache. This requires a Cloudflare account, a Zone ID, and an API Token with “Zone.Cache Purge” permission. No personal data or visitor information is transmitted — only URL paths and authentication credentials are sent.</p>
<ul>
<li><a href="https://www.cloudflare.com/terms/" rel="nofollow ugc">Cloudflare Terms of Service</a></li>
<li><a href="https://www.cloudflare.com/privacypolicy/" rel="nofollow ugc">Cloudflare Privacy Policy</a></li>
</ul>
<p><strong>Varnish Cache</strong> — The plugin opens raw TCP socket connections to a Varnish server at a user-configured IP address and port (default: 127.0.0.1:80). This is typically a localhost connection to infrastructure managed by the site administrator. No external third-party service is contacted for this functionality.</p>
<h4>Data Handling & Logging</h4>
<p>When debug mode is enabled by the administrator, the plugin logs technical data (URL paths, timestamps, socket connection status, purge results) to files in <code>wp-content/uploads/mscache-logs/</code>. Log files are protected with <code>.htaccess</code> rules, obfuscated filenames, and an <code>index.php</code> guard. No personally identifiable information (PII) or visitor data is collected, stored, or transmitted. Purge statistics (success/failure counts, recent activity) are stored in the WordPress options table and are visible only to administrators.</p>
<h3>Configuration</h3>
<h4>General Settings</h4>
<ul>
<li><strong>Enable Plugin</strong> — master switch for all purge functionality.</li>
<li><strong>Varnish IP</strong> — the IP address of your Varnish server (default: 127.0.0.1).</li>
<li><strong>Varnish Port</strong> — the port Varnish listens on (default: 80).</li>
<li><strong>Custom Host Header</strong> — override the Host header sent with purge requests. Leave empty to use your WordPress site URL.</li>
<li><strong>Socket Timeout</strong> — connection timeout in seconds (default: 5).</li>
</ul>
<h4>Automatic Purge</h4>
<p>Choose which content changes trigger automatic cache purge:</p>
<ul>
<li>Posts, Pages, Custom Post Types</li>
<li>Home page</li>
<li>Category, tag, author, and date archives</li>
</ul>
<h4>Full Cache Purge</h4>
<p>Three methods are available:</p>
<ul>
<li><strong>PURGE /.*</strong> — sends a PURGE request with a wildcard path. Requires Varnish VCL to handle regex/wildcard PURGE.</li>
<li><strong>PURGE custom path</strong> — sends PURGE to a specific path (e.g., <code>/purge-all</code>). Useful when your VCL maps a special path to a full ban.</li>
<li><strong>BAN with custom header</strong> — sends a BAN request with a configurable header name and value. The most flexible option but requires matching VCL configuration.</li>
</ul>
<p><strong>Important:</strong> The actual behavior of a full purge depends entirely on your Varnish VCL configuration. The plugin only sends the request — it is your VCL that decides what gets purged.</p>
<h4>Additional URLs</h4>
<p>Enter one URL per line (absolute or relative paths). These URLs can be purged:</p>
<ul>
<li>Automatically alongside post/page saves (if the option is enabled)</li>
<li>Manually via the “Purge Additional URLs” button</li>
</ul>
<h4>Exclusions</h4>
<p>Define patterns (one per line) for URLs that should be excluded from caching. Two matching modes:</p>
<ul>
<li><strong>Glob</strong> (default) — supports <code>*</code> (any characters) and <code>?</code> (single character). Example: <code>/wp-admin/*</code>, <code>/cart*</code>, <code>*.xml</code></li>
<li><strong>Regex</strong> (advanced) — full regular expression support. Use with caution.</li>
</ul>
<p>When a frontend request matches an exclusion pattern, the plugin sends the HTTP header <code>ms-cache: excluded</code>. Your Varnish VCL can check for this header and bypass caching accordingly.</p>
<p>Lines starting with <code>#</code> are treated as comments and ignored.</p>
<p>Matching is performed on the request path only, ignoring the query string.</p>
<h3>Disclaimer</h3>
<p>This plugin is provided “as is” under the terms of the GNU General Public License v2 or later. MANAGED SERVER S.R.L. does not warrant that the plugin will function correctly on hosting environments, servers, or Varnish configurations not directly managed by the company. The plugin has been tested and validated exclusively on the Managed Server hosting infrastructure. Use on third-party environments is at the user’s sole risk and responsibility. In no event shall MANAGED SERVER S.R.L. be liable for any direct, indirect, incidental, or consequential damages arising from the use of this plugin outside of the Managed Server infrastructure.</p>


MSCache Varnish Purge

Purge Varnish cache from the WordPress admin: automatic purge on content changes, exclusions, manual tools and full cache purge.

Nginx Cache Controller vs MSCache Varnish Purge