litespeed/get-cache-vary reads the vary configuration: the cookies and groups that decide when LiteSpeed keeps a separate cached copy of a page.
Read it before changing anything about it.
At a glance
| Ability | litespeed/get-cache-vary |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Page Cache |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
A cache key is normally just the URL. Vary rules add to it: with a rule on a cookie, two visitors whose cookie values differ get two different cached copies of the same URL.
That is the entire mechanism by which a cached site can show different things to different people. Logged-in caching, per-currency pricing, a language switcher — all of them are vary rules underneath.
A vary rule decides when LiteSpeed keeps a separate cached copy of a page. Get it wrong and one visitor’s page is served to another — a logged-in user’s dashboard to a stranger, one customer’s cart to the next. That failure does not announce itself; it shows up as a support message from somebody who saw a name that was not theirs.
Which is why this read exists separately and why the write points back at it. The rules are short, obscure, and consequential out of all proportion to their length.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | array | One row per setting: its key, its current value, its type, and whether this suite can write it. |
count | integer | How many settings the area holds. |
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:
What makes LiteSpeed cache a separate copy of a page here?
It resolves to one call:
{
"ability": "litespeed/get-cache-vary",
"parameters": {}
}Worth knowing
- Vary rules are what make logged-in caching safe. Read them before widening cache scope.
- A missing rule shows as one visitor seeing another’s page.
- Short list, large consequences.
Related abilities
- Update Cache Vary Rules — change them, one at a time
- Update Cache Scope — the setting these protect
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category