Cache Manager
Cache Manager enables and verifies SHM's automatic server response cache for each domain while keeping private, authenticated, cart, checkout, session, and unsafe request traffic out of shared cache.
Where to find it: Open the account, choose Web Manager, then open Cache Manager.
Available to: The account user for their own account, plus root or the owning reseller when working inside that account. The item may be hidden when its feature profile or required service is disabled.
What this page does
Use it to enable or disable caching, review inherited and domain-specific policy, manage exclusions, inspect cache statistics, clear stored responses, and run a live test that reports results such as MISS, HIT, BYPASS, or STALE.
Before you start
Start with a working uncached website and a current backup or recovery path. Test login, account, cart, checkout, API, form, and other personalized flows before leaving cache enabled. Cache makes a healthy public page faster; it cannot negotiate peace with a broken application.
Automatic safety
When enabled, SHM applies native cache analysis, invalidation, and warmup behavior without requiring Redis or an application plugin. Requests with unsafe methods, authenticated/session context, private response directives, or protected application patterns are bypassed rather than shared.
Main controls
| Control | What it does |
|---|---|
| Automatic Server Cache | Turns caching on or off for the selected domain. |
| TTL and inherited defaults | Controls how long eligible public responses remain reusable; a domain override wins over the root default. |
| Exclusions | Adds exact supported paths or patterns that must bypass cache. |
| Clear cache | Invalidates stored responses for the selected scope after a deploy or content problem. |
| Live test | Sends controlled requests and reports the observed cache state for each tested URL. |
| Statistics | Shows cache activity and outcomes available for the selected domain. |
Understanding test results
| Result | Meaning |
|---|---|
| MISS | The request was eligible, but no reusable response existed yet; the response may populate cache. |
| HIT | A reusable cached response served the request. |
| BYPASS | Safety or policy deliberately sent the request to the application. |
| STALE | An older cached response participated in the supported stale/revalidation behavior. |
How to use it
- Select one domain and record an uncached application baseline.
- Enable Automatic Server Cache and save.
- Run the live test twice on representative public URLs.
- Confirm expected MISS then HIT behavior and deliberate BYPASS on private flows.
- Add only necessary exclusions, retest, and monitor application behavior.
Result and next check
Eligible public requests show repeatable cache behavior, private or unsafe traffic remains bypassed, and the site still works for anonymous and authenticated customers. If those conditions are not met, disable the domain cache while investigating.
Theme color