开发者 | LiteSpeedTech |
---|---|
更新时间 | 2024年12月17日 04:14 |
PHP版本: | 4.9 及以上 |
WordPress版本: | 6.7 |
版权: | 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,这样缓存入口可以储存在服务器级别。
如果使用其它的负载均衡,缓存入口将被储存在后台节点,而不是负载均衡中。
清除将不能在不同节点同步,所以不推荐这样做。
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.
You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team help validate, triage and handle any security vulnerabilities. Report a security vulnerability.
mt_srand
function in random hash generation to slightly improve the hash result.AUTH_KEY
defined in wp-config.php
.wp-content/litespeed
directory is not writable, and debug option is ON./wp-content/litespeed/debug/
./litespeed/debug/
folder log files in .htaccess.LSCWP_DEBUG_PATH
support.debug.purge.log
to purge.log
.index.php
for debug folder.Log Cookies
option.WordPress Image Quality Control
setting from Image Optimization
menu to Page Optimization
menu.cache_nocacheable.txt
predefined settings.DONOTCACHEPAGE
.json_encode/json_decode
. (hosni/szepeviktor #693)data-settings
attribute when the WebP image is not yet ready. (kanten/cbwwebmaster/reedock #132840 #680939 #326525)wp litespeed-image batch_switch orig/optm
. (A2Hosting)Cache-Control: no-cache, no-store, must-revalidate, max-age=0
when page is not cacheable. (asafm7/Ruikai)X-Http-Method-Override
now. (George)X-Http-Method-Override: HEAD
. (George)noabort
to all async tasks to avoid image optimization timeout. (Peter Wells)Disable All Features
link for Multisite.litespeed_media_add_missing_sizes
filter to allow bypassing Media's "add missing sizes" option (for Guest Optimization and otherwise). (PR #564)litespeed_vary_cookies
for LSWS Enterprise.pagespeed ninja
to blocklist due to its bad behavior.