| 开发者 | LiteSpeedTech |
|---|---|
| 更新时间 | 2026年4月2日 00:54 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 6.9 |
| 版权: | 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.
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.
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)litespeed_conf_load_option_{$option} to allow modifying configuration values.O_MEDIA_PRELOAD_FEATURED option.allowed_redirect_hosts filter to prevent unexpected errors. (PR#933 #6972377)Purge All - VPI to the Purge menu. (PR#898)Drop Query String setting was not saved when in network mode. (Jory Hogeveen PR#910)Object Cache Method is changed.conf::val() function.Optimize Image Sizes to allow user to choose which image sizes to include in optimization request.advanced-cache.php support since WP v5.3+ doesn't need it, and LiteSpeed requires WP v5.3+.Cache-Control header. (asafm7)LITESPEED_BYPASS_OPTM.LITESPEED_DEV constant to allow switching to a development environment._) for private functions and variables in format checker.sanitize_file_name usage to prevent template failure when 3rd party plugins manipulate that filter.<title> tags. (idatahuy)wp litespeed-database database optimization command.option command failure handler.Plain. (#934261 PR#860)litespeed_purge_tags filter to allow manipulation of purge tags.litespeed_ui_events via window property. (Zsombor Franczia PR#865)litespeed_vpi_should_queue filter to allow control over appending to the VPI queue. (tompalmer #855, Viktor Szépe PR#856)async attribute was replaced even when it contained a value, e.g. async=true. (@macorak)opcache.restrict_api setting to prevent PHP warning in purge. (ookris #9496550 PR#812)site_url instead of home_url to fix the content folder parsing and QUIC.cloud calls.Cache PHP Resources option.litespeed_next_gen_format to manipulate the value of next gen format. (Zsombor Franczia #853)Purge All On Upgrade now defaults to OFF.Disable all features message on all WP-Admin pages for Admin-level users when enabled.SHOW TABLES with DESCRIBE to prevent database halt in very large WP Multisite installations. (Boone Gorges PR#834, PR#850)litespeed_save_conf to provide a trigger for configuration updates.Log View tab.const.default.json instead of const.default.ini for better compatibility in case parse_ini_file() is disabled.Domain Key. Now using sodium encryption for authentication and validation.list_preferred in online service node detection.LITESPEED_DISABLE_ALL will now check the value to determine whether it's been applied.wp litespeed-online cdn_init --ssl-cert=xxx.pem --ssl-key=xxx -method=cname|ns|cfi.wp litespeed-online link --email=xxx@example.com --api-key=xxxx.wp litespeed-online cdn_status.--force argument for QUIC.cloud CLI command wp litespeed-online ping.Auto Pull Cron setting. Added PHP const LITESPEED_IMG_OPTM_PULL_CRON support.LITESPEED_IMG_OPTM_PULL_THREADS to adjust the threads to avoid PHP max connection limits.LITESPEED_FORCE_WP_REMOTE_GET to force using wp_remote_get() to pull images.litespeed_img_optm_options_per_image.LSWCP_EMPTYCACHE to be defined as false to disable the ability to Purge all sites.PURGESINGLE and PURGE query string purge tag bug.PURGE will purge the single URL only like PURGESINGLE.Login Cookie was set.after_setup_theme hook, now happens later in the init hook.Role Simulator w/ IP limited to 127.0.0.1 only. Use LITESPEED_CRAWLER_LOCAL_PORT to use 80 if original server does not support 443.Run Duration maximum to 900 seconds and dropped the setting.Delay setting. Added PHP const LITESPEED_CRAWLER_USLEEP support.Timeout setting. Added PHP const LITESPEED_CRAWLER_TIMEOUT support.Threads setting. Added PHP const LITESPEED_CRAWLER_THREADS support.Interval Between Runs setting. Added PHP const LITESPEED_CRAWLER_RUN_INTERVAL support.Sitemap Timeout setting. Added PHP const LITESPEED_CRAWLER_MAP_TIMEOUT support.Drop Domain from Sitemap setting. Added PHP const LITESPEED_CRAWLER_DROP_DOMAIN support.LITESPEED_NO_OPTM constant definition. (Roy Orbitson PR#796)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.