开发者 | LiteSpeedTech |
---|---|
更新时间 | 2024年4月26日 04:11 |
PHP版本: | 4.0 及以上 |
WordPress版本: | 6.5.2 |
版权: | GPLv3 |
版权网址: | 版权信息 |
ON
.--wordpresspath
parameter.This plugin communicates with your LiteSpeed Web Server and its built-in page cache (LSCache) to deliver superior performance to your WordPress site. The plugin’s cache features indicate to the server that a page is cacheable and for how long, or they invalidate particular cached pages using tags. 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 includes additional optimization features, such as Database Optimization, Minification and Combination of CSS and JS files, HTTP/2 Push, CDN Support, Browser Cache, Object Cache, Lazy Load for Images, and Image Optimization! These features do not require the use of a LiteSpeed web server.
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:
The cache entries are stored at the LiteSpeed server level. The simplest solution is to use LiteSpeed WebADC, as the cache entries will be stored at that level.
If using another load balancer, the cache entries will only be stored at the backend nodes, not at the load balancer.
The purges will also not be synchronized across the nodes, so this is not recommended.
If a customized solution is required, please contact LiteSpeed Technologies at info@litespeedtech.com
NOTICE: The rewrite rules created by this plugin must be copied to the Load Balancer.
The actual cached pages are stored and managed by LiteSpeed Servers. Nothing is stored within the WordPress file structure.
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.
The crawler is disabled by default, and must be enabled by the server admin first.
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.
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 bahavior.