內容簡介
總結：BrenWP Cache通過向匿名訪客提供緩存的HTML頁面來加快WordPress的速度。當緩存未命中時，WordPress會正常呈現頁面；BrenWP Cache捕獲最終的HTML輸出並將其存儲為文件。在後續的請求中，緩存的HTML會被提早提供，減少了伺服器負載並改善了響應時間。
HTML項目清單:
- 這個外掛有意地保持簡約、透明、並且友好於WordPress.org：
* 無遙測、無追踪、無“向外部發送數據”
* 沒有外部服務或依賴
* 管理員UI資源只限於這個外掛的頁面
問與答：
1. BrenWP Cache 是通過什麼方式來加快WordPress的速度？
- BrenWP Cache會向匿名訪客提供緩存的HTML頁面。
2. 在什麼情況下，WordPress會正常呈現頁面而不使用緩存？
- 當緩存未命中時，WordPress會正常渲染頁面。
3. 根據文章，BrenWP Cache如何處理緩存的HTML輸出？
- BrenWP Cache捕獲最終的HTML輸出並將其存儲為文件，下次可以提早提供緩存的HTML，以減少伺服器負載並改善響應時間。
外掛標籤
開發者團隊
原文外掛簡介
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
Key features
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. /checkout)
– Wildcards (e.g. /cart*)
* Exclude by cookies (useful for ecommerce/session cookies).
* Exclude by user agent (bots, scanners, special clients).
* Bypass query parameter: when present (e.g. ?nocache=1) 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 wp-content/cache/brenwp-cache 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
Recommended usage (important)
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:
– /checkout, /cart, /my-account (WooCommerce)
– Any pages that show user-specific data, pricing, currency switching, or session-based content
* If a page sets cookies or sends Cache-Control: private/no-store/no-cache, it will not be cached.
Developed by Brendigo LTD.
Privacy
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.
