litespeed/update-cache-settings changes the general cache settings and the ESI (Edge Side Includes) behaviour.
The master on/off switch is not here — that is litespeed/set-cache-state, which confirms before disabling.
At a glance
| Ability | litespeed/update-cache-settings |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Page Cache |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
The write is a patch, not a replacement. Send one key and one key changes; everything else in the area is left alone. The response names the keys that actually moved, so a payload that matched the existing values comes back with an empty list rather than a misleading success.
ESI is the interesting part of this area. It lets LiteSpeed cache a page while leaving holes — a cart total, a “logged in as” greeting — that are filled per request. That is what makes caching a logged-in page viable at all, and it is also the feature most likely to be configured optimistically and then quietly not work, because it requires server support that not every LiteSpeed installation has.
Splitting the master switch out into its own ability is deliberate. Turning caching off is a change with no visible symptom — the site keeps working, just slowly — so it gets a confirmation, while adjusting an ESI option does not need one.
Idempotent. Sending values that are already set reports an empty updated list.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
settings | object | Yes | A map of setting key to new value. Keys outside this area are refused, and the refusal lists what the area accepts. |
What comes back
| Name | Type | What it is |
|---|---|---|
updated | array | The keys that actually changed. An empty array means every value you sent was already set. |
settings | array | Every setting in the area after the write, in the read shape. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Turn on ESI for this site.
It resolves to one call:
{
"ability": "litespeed/update-cache-settings",
"parameters": {
"settings": { "esi-enabled": true }
}
}Worth knowing
- The master switch lives in
litespeed/set-cache-state. - ESI needs server support. Enabling it in the settings does not guarantee it works.
- A patch — unsent keys are untouched.
- Purge afterwards; existing cached pages were built under the old settings.
Related abilities
- Turn Caching On Or Off — the master switch
- Get Cache Settings — read before writing
- Purge Cache — rebuild under the new settings
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category