site.ini [CacheUntilSettings]
The block [CacheUntilSettings] of settings/site.ini, with 1 setting(s).
Never edit settings/site.ini itself: an update replaces it. Put the settings you change in an override, which wins over the shipped file:
settings/override/site.ini.append.phpfor every siteaccess,settings/siteaccess/<siteaccess>/site.ini.append.phpfor one siteaccess,extension/<extension>/settings/site.ini.append.phpin an extension (read when the extension is active).
LiteSpeedMaxAge
The template operator cache_until() sets when a page stops being true ({cache_until( 'tomorrow' )},
{cache_until( $event_start )}, {cache_until( 0 )}). Every cache honours it without a setting: the view cache,
the template-block cache, the HTTP cache (httpcache.ini), Velocity's response cache, and the max-age, s-maxage
and Expires of the response. Time strings are read in [TimeZoneSettings] TimeZone.
Guide: doc/eng-us/guides/caching-time-dependent-content.mdA page that must not be kept (cache_until( 0 )) always gets "X-LiteSpeed-Cache-Control: no-cache", which only
ever keeps a page out of LiteSpeed's page cache. enabled: an anonymous visitor's page with an expiry also gets
"X-LiteSpeed-Cache-Control: max-age=<seconds left>", so LiteSpeed keeps it no longer than the expiry even when
it ignores the response's Cache-Control. LiteSpeed reads that header on every response, also one its rewrite
rules do not cache: enable it only when the pages that call cache_until() are pages your LiteSpeed block caches
(doc/eng-us/guides/litespeed-page-cache.md).
Default: disabled.
# settings/override/site.ini.append.php
[CacheUntilSettings]
LiteSpeedMaxAge=disabled
*/ ?>Related
Generated by ./console exp:help:examples from settings/site.ini. Do not edit this page: change the source and generate again (how). Free documentation: GFDL 1.3 or later.