| 开发者 | LiteSpeedTech |
|---|---|
| 更新时间 | 2026年10月21日 02:08 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
ON.--wordpresspath parameter.本插件与您的 LiteSpeed Web Server 及其内置的页面缓存(LSCache)通信,为您的 WordPress 站点带来卓越的性能。插件的缓存功能会告知服务器某个页面是否可缓存以及可缓存多长时间,或者使用标签让特定的已缓存页面失效。 LSCache is a server-level cache, so it's faster than PHP-level caches. Compare with other PHP-based caches. A page cache allows the server to bypass PHP and database queries altogether. LSCache, in particular, because of its close relationship with the server, can remember things about the cache entries that other plugins cannot, and it can analyze dependencies. It can utilize tags to manage the smart purging of the cache, and it can use vary cookies to serve multiple versions of cached content based on things like mobile vs. desktop, geographic location, and currencies. See our Caching 101 blog series. If all of that sounds complicated, no need to worry. LSCWP works right out of the box with default settings that are appropriate for most sites. See the Beginner's Guide. Don't have a LiteSpeed server? Try our QUIC.cloud CDN service. It allows sites on any server (NGINX and Apache included) to experience the power of LiteSpeed caching! Click here to learn more or to give QUIC.cloud a try.
LSCWP 还包含其他优化功能,例如数据库优化、CSS 和 JS 文件的压缩与合并、HTTP/2 推送、CDN 支持、浏览器缓存、对象缓存、图片延迟加载以及图片优化!这些功能无需使用 LiteSpeed Web 服务器。
Yes, LSCWP will always be free and open source. That said, a LiteSpeed server is required for the cache features, and there are fees associated with some LiteSpeed server editions. Some of the premium online services provided through QUIC.cloud (CDN Service, Image Optimization, Critical CSS, Low-Quality Image Placeholder, etc.) require payment at certain usage levels. You can learn more about what these services cost, and what levels of service are free, on your QUIC.cloud dashboard.
A LiteSpeed solution is required in order to use the LiteSpeed Exclusive features of this plugin. Any one of the following will work:
缓存条目存储在 LiteSpeed 服务器层级。最简单的解决方案是使用 LiteSpeed WebADC,这样缓存条目就会存储在 WebADC 这一层级。
如果使用其他负载均衡器,缓存条目将只存储在后端节点上,而不会存储在负载均衡器上。
清除操作也不会在各节点之间同步,因此不建议这样做。
If a customized solution is required, please contact LiteSpeed Technologies at info@litespeedtech.com
注意:此插件创建的重写规则必须复制到负载均衡器上。
实际的缓存页面由 LiteSpeed 服务器存储和管理。 WordPress 文件结构中不会存储任何缓存内容。
Yes it can work well with OpenLiteSpeed, although some features may not be supported. See Plugin Features above for details. Any setting changes that require modifying the .htaccess file will require a server restart.
In short, yes. However, for some WooCommerce themes, the cart may not be updated correctly. Please visit our blog for a quick tutorial on how to detect this problem and fix it if necessary.
Images are not optimized automatically unless you set LiteSpeed Cache > Image Optimization > Image Optimization Settings > Auto Request Cron to ON. You may also optimize your images manually. Learn more.
Our API includes a function that uses ESI to "punch a hole" in a cached page for a nonce. This allows the nonce to be cached separately, regardless of the TTL of the page it is on. Learn more in the API documentation. We also welcome contributions to our predefined list of known third party plugin nonces that users can optionally include via the plugin's ESI settings.
爬虫默认处于停用状态,必须先由服务器管理员启用。
Once the crawler is enabled on the server side, navigate to LiteSpeed Cache > Crawler > General Settings and set Crawler to ON.
For more detailed information about crawler setup, please see the Crawler documentation.
您可以通过以下任一渠道报告疑似漏洞:
support@litespeedtech.com, or open a private ticket from the LiteSpeed Client Area.security.md in the plugin folder.
Do Not Cache URIs now ignore a leading or trailing *, so /wp-json/mcp/* matches the same as /wp-json/mcp/. (#1040)check_img diagnostic endpoint.litespeed_is_from_cloud filter. Each callback is now authorized by its own signature instead of by a request-wide flag.litespeed_static_dir_htaccess filter so hosts can remove unsupported directives from the generated static-directory protection file. (vvvllll #1043)_hash validation. (Robert Staddon PR#1008)fetchpriority=high to VPI preload links. (Maciej Mroziński PR#993)Store Transients option. Transients now always use Object Cache when available, preventing potential database bloat from expired transients not being cleared. (ravanh)null instead of false on failure, matching WordPress Object Cache API convention.(jkolodziej)