{% extends "baseTemplate/index.html" %} {% load static %} {% comment %} /cache/lscache — the LiteSpeed full-page cache for one website. The website list is rendered from `domains`, which ACLManager.findAllSites already narrowed to the caller. Picking one posts to /cache/fetchCacheStatus, which re-resolves ownership server side; nothing on this page is trusted because it came from this select. {% endcomment %} {% block title %}LiteSpeed page cache{% endblock %} {% block styles %} {% include "cacheManager/_styles.html" %} {% endblock %} {% block content %}
{{ domains|json_script:"cpCacheDomains" }} {{ selectedDomain|json_script:"cpCacheSelected" }}

LiteSpeed page cache

Full-page caching inside OpenLiteSpeed, configured per website.

All caches

Page cache for

When this is on, OpenLiteSpeed stores cacheable responses on disk and serves repeat visitors without starting PHP at all.

WordPress integration

This site is not a WordPress installation. There is no wp-config.php in . The page cache above still works — it is a web server feature and caches any public, cacheable response. What is not available is the plugin-driven part: automatic purging when content changes, per-page cache rules and ESI. Your application can drive those itself by sending X-LiteSpeed-Cache-Control and X-LiteSpeed-Purge response headers.

The LiteSpeed Cache plugin lets WordPress purge exactly the pages it changed instead of waiting for the TTL to expire.

This website has no system user recorded, so wp-cli cannot run for it.

Cache behaviour

How long an anonymous visitor's page stays cached.
Applies to logged-in visitors, per session.
How long an expired copy may still be served while it refreshes.
Responses larger than this are never cached.

Purge the cache

Deletes every cached page for this site. The next visitor to each page pays for regenerating it, so expect a brief slowdown rather than an outage.

Storage path

Choose a website to see its page cache settings.

{% endblock %} {% block scripts %} {% endblock %}