WeAmp Cache Control for ModPageSpeed
| 开发者 | oschaaf |
|---|---|
| 更新时间 | 2026年6月18日 14:55 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
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:
- Enables full-page caching — adds
Cache-Control: public, max-age=Nto 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. - 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.
- 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
wp pagespeed flush|status|test-connectioncommands.
- ModPageSpeed 2.0 caches full HTML pages itself — the plugin's headers and purge calls drive the module's page cache directly.
- 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
proxy_cache, Varnish, or a CDN) plusModifyCachingHeaders offorDownstreamCachePurgeLocationPrefix— with 1.1's defaultModifyCachingHeaders on, 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.
- ModPageSpeed 1.1 (v1.15.0+r3 or later) or ModPageSpeed 2.0 (v2.0.0 or later) installed on your web server.
- For 2.0: the worker admin API enabled (
--api-port). - 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.
wp pagespeed flush [--url=<url>]— purge the home page (and posts page), or one specific URL on this site.wp pagespeed status— detected product, version, license tier, purge prerequisites, and last-purge status.wp pagespeed test-connection— verify the admin API is reachable and correctly configured (read-only, never purges).
安装:
- Install ModPageSpeed on your server (see https://modpagespeed.com/).
- Install and activate this plugin.
- Follow the setup wizard under Settings > ModPageSpeed: detect your server, enter the admin API URL, test the connection, apply the nginx.conf snippet, enable caching, and run a test purge.
屏幕截图:
常见问题:
Does this plugin cache pages itself?
No. Caching happens server-side: in the ModPageSpeed 2.0 module itself, or — on 1.1 — in your front cache (proxy_cache, Varnish, or CDN; the 1.1 module does not cache HTML, see the Description). The plugin only sets cache headers and sends purge requests — the same architecture as other server-layer cache plugins.
I run mod_pagespeed / ngx_pagespeed 1.1 — do I get full-page caching?
Not from the module alone. 1.1 never caches HTML; put an external cache (nginx proxy_cache, Varnish, or a CDN) in front of it and set ModifyCachingHeaders off (or use DownstreamCachePurgeLocationPrefix) so this plugin's Cache-Control headers reach that cache. The plugin's purge calls on 1.1 evict optimized sub-resources and metadata.
Does it work without ModPageSpeed installed?
No. The setup wizard will guide you to the server module installation docs if no server is detected.
更新日志:
0.1.0
- Initial release: Cache-Control headers for anonymous pages, purge on publish/update/delete/comment/stock changes, ModPageSpeed 1.1 and 2.0 support with auto-detection, setup wizard, WP-CLI commands.