Skip to Content
Browse documentation

OLS Cache Purge

Request OpenLiteSpeed cache invalidation for a URL, domain or the whole server, and verify its actual scope and result.

Open Web Servers → OpenLiteSpeed → OLS Cache Purge.

Use the smallest scope appropriate to the stale content. These controls target OpenLiteSpeed cache operations, not browser caches, external CDNs or application-specific caches.

Purge a URL

  1. Enter a complete http:// or https:// URL in the URL field.
  2. Click Purge URL.
  3. Read the result and request the page again to verify freshness.

The backend checks the host against known hosting domains, with a special case removing a leading www.. It sends a PURGE request using the configured OpenLiteSpeed HTTP or HTTPS port. Use an ordinary hosted-domain URL without embedded credentials or a manually appended port.

Purge a domain

The domain table shows the domain, owner, account status and purge action. Search or paginate to locate the intended row.

  1. Click Purge domain cache.
  2. Review the domain in the confirmation.
  3. Confirm Purge Cache.
  4. Verify the affected content.

Suspended rows have no domain-purge action. The helper sends PURGE requests to the domain root over HTTP and HTTPS using the configured ports. Do not assume that requesting the root guarantees removal of every cached path or variant; that depends on how the receiving cache handles the request.

Success is not a cache-content check

URL purge success is based on curl's process exit result, not a verified cache miss or successful HTTP status. The domain helper reports its final HTTP request result without incorporating the separate HTTPS result. Check the relevant HTTP and HTTPS content independently.

Purge all cache

Click Purge All Cache, read the confirmation and confirm Purge Cache. This starts the global purge task through taskd. A successful message means the task was accepted; inspect progress and logs before treating the purge as complete.

A broad purge can increase uncached requests. Use it deliberately rather than repeatedly clearing all cache for one stale page.

Requirements and troubleshooting

Demo sessions cannot purge. URL/domain operations require the curl executable and valid OpenLiteSpeed port configuration. The domain must be recognized in hosting metadata.

For Domain not found, verify the chosen hostname and domain ownership data. For curl errors, inspect connectivity, DNS, TLS and service-port configuration. A request can reach the wrong system if public DNS points elsewhere; a success message alone does not prove this server handled it.

If content remains stale, check whether OpenLiteSpeed caching is active, whether the application permits caching and whether another cache layer is involved. Purging does not enable LSCache or change the settings documented in OpenLiteSpeed Settings.