內容簡介
Brightery Cache King 是一款獨立的全頁快取外掛，專為公共 WordPress 內容設計。它將完成的匿名 HTML 回應儲存為檔案，並在後續訪問中重複使用，提升網站效能。
【主要功能】
• 靜態 HTML 快取公共頁面、文章及產品
• 支援 Apache 和 LiteSpeed 伺服器的直接靜態交付
• 自動快取失效管理，確保內容更新
• 手動首頁建構器及全站快取建構器
• Gzip 預壓縮及 ETag 支援
• 獨立快取目錄管理
外掛標籤
開發者團隊
原文外掛簡介
Brightery Cache King is a standalone full-page cache for public WordPress content. It stores completed anonymous HTML responses as files and reuses them on later visits.
The plugin does not require an account, external service, CDN, Composer package, PHP extension, or another caching plugin.
Main features
Static HTML cache for public pages, posts, archives, products, and public custom post types.
Direct static delivery on compatible Apache and LiteSpeed servers.
Early advanced-cache.php delivery when direct web-server delivery is unavailable.
Generated Nginx configuration guidance for direct static delivery.
Manual homepage builder and background full-site cache builder.
Automatic cache invalidation after content and public site structure changes.
Gzip precompression, ETag, Last-Modified, HEAD, and conditional-request support.
Separate cache directories per host.
Integration health checks and repair controls.
Safe by default
Cache King bypasses logged-in sessions, WordPress Admin, login, REST API requests, XML-RPC, Ajax, cron, previews, searches, password-protected content, errors, feeds, authenticated requests, and responses marked private.
WooCommerce cart, checkout, account URLs, and customer-session cookies are excluded by default. Public product and category pages can still be cached.
No off-site data transfer
Cache King stores only HTML already generated for public visitors. It makes local loopback requests to the same WordPress site when you build static pages. It does not send site or visitor data to Brightery or any third party.
Security and privacy
Administrative actions require the manage_options capability and WordPress nonces.
Cache writes use temporary files and the WordPress filesystem API.
Cache paths and hosts are validated before filesystem use.
Cache cleanup remains inside the plugin-owned cache directory and does not follow symbolic links.
Generated configuration and temporary files are blocked from direct Apache access.
No analytics, tracking, telemetry, account registration, or off-site API is included.
