oschaaf

This plugin is the control panel for ModPageSpeed — a web server optimization module for nginx and Apache. ModPageSpeed must be installed and running on your server for this plugin to function. It is not a standalone caching plugin.
The plugin does three things:
<ol>
<li>Enables full-page caching — adds <code>Cache-Control: public, max-age=N</code> to anonymous page responses (WordPress does not send this by default), with explicit bypasses for logged-in users, WooCommerce cart/checkout/account pages, search, feeds, and 404s.</li>
<li>Keeps the cache fresh — calls the ModPageSpeed purge API when you publish, update, or delete content, when comments change, when stock levels change, and when terms or theme settings change.</li>
<li>Gives you control in WP Admin and WP-CLI — per-post-type TTLs, cookie bypass list, excluded URL patterns, a first-run setup wizard, and <code>wp pagespeed flush|status|test-connection</code> commands.</li>
</ol>
Works with both ModPageSpeed product lines (auto-detected), with one important difference:
<ul>
<li>ModPageSpeed 2.0 caches full HTML pages itself — the plugin’s headers and purge calls drive the module’s page cache directly.</li>
<li>mod_pagespeed / ngx_pagespeed 1.1 does not cache HTML (it is a streaming rewriter; its in-place optimization caches only images, CSS, and JS). Full-page caching on 1.1 requires an external cache layer in front (nginx <code>proxy_cache</code>, Varnish, or a CDN) plus <code>ModifyCachingHeaders off</code> or <code>DownstreamCachePurgeLocationPrefix</code> — with 1.1’s default <code>ModifyCachingHeaders on</code>, the module replaces this plugin’s Cache-Control header on rewritten HTML. On 1.1, the plugin’s purge calls evict optimized sub-resources and metadata, not HTML pages.</li>
</ul>
<h4>Server requirements</h4>
<ul>
<li>ModPageSpeed 1.1 (v1.15.0+r3 or later) or ModPageSpeed 2.0 (v2.0.0 or later) installed on your web server.</li>
<li>For 2.0: the worker admin API enabled (<code>--api-port</code>).</li>
<li>For full logged-in-user correctness an nginx cookie-bypass map block is required — the setup wizard provides a copy-paste snippet and verifies it.</li>
</ul>
<h4>WP-CLI</h4>
<ul>
<li><code>wp pagespeed flush [--url=<url>]</code> — purge the home page (and posts page), or one specific URL on this site.</li>
<li><code>wp pagespeed status</code> — detected product, version, license tier, purge prerequisites, and last-purge status.</li>
<li><code>wp pagespeed test-connection</code> — verify the admin API is reachable and correctly configured (read-only, never purges).</li>
</ul>
<h4>License</h4>
This plugin is free software, licensed under the GNU General Public License v2.0 or later. The full GPL-2.0 license text is bundled with the plugin in the LICENSE file.
<h3>Third Party Services</h3>
This plugin makes HTTP requests to the operator-configured ModPageSpeed admin API URL. Data sent includes page URLs (for cache purging) and an API key (for authentication). No data is sent to We-Amp or any third party.

WeAmp Cache Control for ModPageSpeed

Full-page caching control panel for the ModPageSpeed server module: cache headers, purge-on-publish, per-post-type TTLs.

Brendigo

BrenWP Cache speeds up WordPress by serving cached HTML pages to anonymous visitors. On a cache miss, WordPress renders the page normally; BrenWP Cache captures the final HTML output and stores it as a file. On subsequent requests, the cached HTML is served early, reducing server load and improving response times.
This plugin is intentionally minimal, transparent, and WordPress.org-friendly: 
* No telemetry, no tracking, no “phone home” 
* No external services or dependencies 
* Admin UI assets are strictly scoped to this plugin’s pages
<h3>Key features</h3>
Full-page file cache for anonymous visitors 
* Caches full HTML documents for GET requests only. 
* Designed for the common “public pages” scenario where most traffic is anonymous. 
* Avoids caching in common non-cacheable contexts such as admin, AJAX, REST, feeds, previews, searches, and similar endpoints.
Rules to prevent caching personalized or dynamic content 
* Exclude logged-in users (recommended; enabled by default). 
* Exclude URLs (one per line): 
 – Prefix rules (e.g. <code>/checkout</code>) 
 – Wildcards (e.g. <code>/cart*</code>) 
* Exclude by cookies (useful for ecommerce/session cookies). 
* Exclude by user agent (bots, scanners, special clients). 
* Bypass query parameter: when present (e.g. <code>?nocache=1</code>) caching is bypassed for that request. 
* Optional 404 caching (disabled by default; enable only if your 404 output is safe and static).
Tools and automation 
* One-click Purge cache tool in WP Admin. 
* Optional auto-purge when posts are updated (useful for content sites that publish/edit frequently).
Security and WordPress.org compliance 
BrenWP Cache is built to meet WordPress.org review expectations: 
* Capability checks + nonces for state-changing admin actions 
* Strict sanitization/validation of input and late escaping for output 
* Cache directory is constrained under <code>wp-content/cache/brenwp-cache</code> with path safety guards 
* Cached HTML is served as a full document (not escaped) and is integrity-verified with an HMAC signature; unsigned/invalid cache is treated as a miss 
* No obfuscation, no remote calls, no dangerous execution patterns
<h3>Recommended usage (important)</h3>
A full-page cache should never store private/personalized output. For best results: 
* Keep “Exclude logged-in users” enabled. 
* Add exclusions for dynamic endpoints such as: 
 – <code>/checkout</code>, <code>/cart</code>, <code>/my-account</code> (WooCommerce) 
 – Any pages that show user-specific data, pricing, currency switching, or session-based content 
* If a page sets cookies or sends <code>Cache-Control: private/no-store/no-cache</code>, it will not be cached.
Developed by Brendigo LTD.
<h3>Privacy</h3>
BrenWP Cache does not collect personal data and does not send telemetry. Optional Preload requests only your own site URLs. 
Caching is file-based on your server, stored under your WordPress content directory, and controlled by your configuration.

BrenWP Cache

Lightweight, privacy-friendly file-based page caching with a modern, strictly scoped WP Admin UI.

WeAmp Cache Control for ModPageSpeed vs BrenWP Cache