Skip to content
Documentation

Your EMCP guide

Answers from our docs

YOUR CHAT, YOUR CHOICE

Before we chat

MSR Builds processes your question and up to four recent messages on our server to answer from the EMCP docs. AI is optional and needs your separate permission.

The chat is kept in this page's memory, not saved as a conversation in our database or browser storage. Our hosting and security services process connection information, such as your IP address, to prevent abuse.

Cloudflare Turnstile checks your browser and connection to prevent automated abuse when you send a question. No login is required.

Please leave out personal, sensitive or confidential information, passwords and API keys.

You can withdraw consent and clear this page's chat at any time. This cannot undo a request already sent or erase provider/security records.

Chat privacy, retention & your rights ↗ · Privacy contact

Starting chat consents to this processing. You can browse our docs without using the chat.

LiteSpeed Cache

New in 3.21.1 (free), and in EMCP Lite 1.0.5 on WordPress.org. Two dispatcher tools work with LiteSpeed Cache 7.9.2:

ToolDefaultPurpose
litespeed-readOnCache settings and server support (1 operation)
litespeed-writeOffPurge one path or the whole page cache (2 operations)

Enable the write tool under Tools > Plugins > LiteSpeed Cache.

Requirements

Section titled “Requirements”
  • LiteSpeed Cache 7.9.2 exactly, on a single site. Another version answers unsupported_version; multisite answers unsupported_environment.
  • An administrator (manage_options).
  • For purges: an HTTP connection (OAuth or an application password, not WP-CLI) to a site served by OpenLiteSpeed, LiteSpeed Enterprise or LiteSpeed ADC, with LiteSpeed Cache allowed and the page cache on.

Operations

Section titled “Operations”
OperationToolWhat it does
statusreadVersion, server type, transport, server_supported, purge_supported, and settings: page cache, CSS, JavaScript and HTML minification, public, private and front page lifetimes
purge-pathwritePurge one path and its query variants
purge-page-cachewritePurge the whole page cache

Both writes need confirm: true; dry_run: true checks support and the path without purging.

Purge rules

Section titled “Purge rules”
  • path is one absolute path on this site, starting with /, up to 2,048 characters. An origin, query string, fragment, backslash, control character, encoded separator or ./.. segment answers invalid_path.
  • On Apache, Nginx, over WP-CLI, with the cache off or after headers were sent, a purge answers unsupported_environment. LiteSpeed Cache purges by sending instructions to the LiteSpeed server in response headers; without such a server a purge would only look successful.
  • A successful purge answers purge_requested. EMCP cannot see the server’s cache, so confirm with the next response: LiteSpeed’s cache header shows a miss, then a hit with the new content.
  • One purge runs at a time (cache_busy).

History

Section titled “History”

Each purge is recorded in History before it runs, as irreversible: cached copies cannot be put back. If History cannot be saved, nothing is purged (history_failed).

Limits

Section titled “Limits”

No settings changes, image or page optimization, CDN, database cleanup, cloud services or .htaccess edits.