Linux 软件免费装
Banner图

LumenCache

开发者 nasruleam
celsiusanderson
更新时间 2026年9月15日 18:14
PHP版本: 8.1 及以上
WordPress版本: 7.1
版权: GPL-2.0-or-later
版权网址: 版权信息

标签

cache performance woocommerce page-speed full-page-cache

下载

1.6.34 1.6.23 1.6.24 1.6.25

详情介绍:

LumenCache implements a RAM-first full-page cache with a WordPress advanced-cache.php drop-in. On a cache HIT, the drop-in serves complete HTML before the normal WordPress bootstrap and database queries. This early-response path reduces application-layer work and keeps repeat page requests fast across Nginx, Apache, and LiteSpeed. The cache is designed to fail open when its storage layer is unavailable, so a cache connection problem does not take the WordPress site offline.

升级注意事项:

1.6.34 Comprehensive audit and hardening release across all 8 core caching pipelines, including early drop-in execution, selective bypass cookie router, Redis multi-driver resilience, contextual Admin Bar & WP-CLI invalidation, and Cloudflare edge synchronization. 1.6.27 Hardened early drop-in and Apache/LiteSpeed proxy feed/sitemap bypass parity and automated config snapshot compilation. 1.6.26 Recommended update for all Nginx, Plesk, and WooCommerce environments with official 502 Bad Gateway buffer resolution. 1.6.24 WordPress 7.1 compatibility release. Recommended update for all users.

常见问题:

Getting a 502 Bad Gateway on Nginx after activating or during WooCommerce use?

Nginx has a default fastcgi_buffer_size of only 4KB–8KB. When combining rich caching headers with WooCommerce session cookies, the upstream response header exceeds this limit. Nginx immediately terminates the connection with: upstream sent too big header while reading response header from upstream, resulting in an instant 502 Bad Gateway error. To resolve this, add the following FastCGI and proxy buffer directives to your Nginx configuration (within the http {}, server {}, or PHP location block): fastcgi_buffer_size 32k; fastcgi_buffers 16 16k; fastcgi_busy_buffers_size 32k; proxy_buffer_size 32k; proxy_buffers 16 16k; proxy_busy_buffers_size 32k; After adding these directives, test and reload Nginx: nginx -t && systemctl reload nginx

Why are 0 pages cached?

Two common causes:

  1. Nginx config not applied — visit Server Setup and paste the config blocks.
  2. WooCommerce session cookie — fixed in v1.1.0. Previous versions bypassed the cache for all visitors on WooCommerce sites due to the always-present wp_woocommerce_session_* cookie.

Why can key salting affect server-level caching?

When LUMENCACHE_CACHE_SALT is set, PHP stores keys as SHA-256 hashes. A server-level configuration must use the same key strategy or it will produce cache misses. Disable the salt for a plain-key configuration, or use the compatible hashed-key server template.

Does LumenCache work with LiteSpeed?

Yes. LiteSpeed supports Apache-compatible .htaccess rewrites. LumenCache uses the Apache proxy mode on LiteSpeed. For better performance, ask your host which in-memory cache acceleration options are available.

Can I still use wp-config.php constants?

Yes — constants always take precedence over admin settings. If you define a constant, the corresponding field in the Settings tab is shown locked (read-only).

更新日志:

1.6.34 (September 15, 2026) 1.6.33 (September 15, 2026) 1.6.32 (September 15, 2026) 1.6.31 (September 15, 2026) 1.6.30 (September 15, 2026) 1.6.29 (September 15, 2026) 1.6.28 (September 15, 2026) 1.6.27 (September 15, 2026) 1.6.26 (September 15, 2026) 1.6.25 (September 4, 2026) 1.6.24 (August 23, 2026) 1.6.23 (August 15, 2026) 1.6.22 (August 15, 2026) 1.6.21 (August 14, 2026) 1.6.20 (August 11, 2026) 1.6.19 (August 11, 2026) 1.6.18 (August 11, 2026) 1.6.17 (August 11, 2026) 1.6.16 (August 11, 2026) 1.6.15 (August 11, 2026) 1.6.14 (August 11, 2026) 1.6.13 (August 11, 2026) 1.6.12 (August 10, 2026) 1.6.11 (August 9, 2026) 1.6.10 (August 9, 2026) 1.6.9 (August 9, 2026) 1.6.8 (August 9, 2026) 1.6.7 (August 9, 2026) 1.6.6 (August 8, 2026) 1.6.5 (August 8, 2026) 1.6.4 (August 8, 2026) 1.6.3 (August 8, 2026) 1.6.2 1.6.1 1.6.0 1.5.1 1.5.0 1.4.0 1.3.0 1.2.9 1.2.8 1.2.7 1.2.6 1.2.5 1.2.4 1.2.3 1.2.2 1.2.1 1.2.0 1.1.1 1.1.0 1.0.3