Web Cache Settings

Web Cache Settings is the detailed policy reference behind a domain's Automatic Server Cache entry in Cache Manager.

Where to find it: Open the account, choose Web Manager, then open Web Cache Settings.

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 understand inherited TTL, domain overrides, exclusions, invalidation, warmup, and the safety reasons that make a request bypass shared cache. The active user workflow remains Account > Cache Manager.

Before you start

Do not force a request to cache merely because it is slow. Personalized responses, cookies, authorization, private headers, unsafe methods, login routes, and transactional paths should normally reach the application.

Policy order

1. Root Configuration > Cache supplies global defaults.
2. The domain's Cache Manager settings override supported defaults.
3. Built-in safety analysis and explicit exclusions decide whether an individual request is eligible.
4. Application response headers can require a bypass.
5. Invalidation removes affected entries after supported changes.

TTL guidance

Use shorter TTLs for frequently changing public content and longer values for stable assets or pages. A longer TTL reduces origin work but extends the time an eligible cached response may be reused; clearing the cache remains an operational action, not a publishing strategy.

Exclusion guidance

Add the narrowest path required and test it. Broad exclusions reduce cache value, while missing exclusions can expose stale or inappropriate shared content. Built-in safety bypasses should remain the first line of protection.

How to use it

1. Review the global default and current domain override.
2. List public paths that benefit from caching and private flows that must bypass it.
3. Enable the domain in Cache Manager.
4. Run repeated public and private live tests.
5. Adjust TTL or exclusions only from observed behavior, then retest.

Result and next check

The domain uses a documented TTL and exclusion policy, eligible public URLs reach HIT after warmup, and private flows consistently report BYPASS.