Install
Works with Drupal: ^10.3 || ^11Using Composer to manage Drupal site dependencies
Alternative installation files
Release notes
Beta1 of the 1.2.x track. Same code as 1.2.0-alpha3 (commit 9cf2d33); the version bump signals API freeze for the 1.2.x track and asks operators to soak the module on production-shape installs ahead of rc1.
What 1.2 ships. An ESI render element lscache_esi that emits <esi:include> tags for per-user fragments, plus the fragment route, HMAC-SHA256 token signer keyed on the site's hash salt, and an lscache_esi cache tag for site-wide invalidation. Builds on 1.1's private-cache machinery — the surrounding response stays in shared public cache while LSCache holds each per-user fragment in its private cache.
Field-test history through alpha cycle. Adopter-side testing on a real-traffic Drupal 11 + LSWS install across alpha2 and alpha3:
- One bug found and fixed in alpha3: ESI fragments produced no output in alpha2 because Drupal's renderer stripped the
<esi:include>tag viaXss::filterAdmin(). Fix: wrap the emitted markup in\Drupal\Core\Render\Markupso the renderer treats it as already-trusted output. - Token-tampering rejection clean across four variants (mutated args, mutated signature, swapped callback, garbage token). All return HTTP 403.
- Cache-tag invalidation refreshes ESI fragments correctly when the underlying content changes.
- No regressions on the inherited 1.1.x admin-route skip and cache-poisoning canary checks.
Stability commitment. The lscache_esi render element shape, the fragment-route URL pattern (/lscache-fragment/{token}), the token format, and the LscacheTokenSigner service are stable from this release forward. Subsequent 1.2.x releases on the path to 1.2.0 stable will be bug-fix only.
Cumulative with 1.1.x. 1.2.x's branch contains all of 1.1.x's private-cache work plus the ESI additions. Installing 1.2.0-beta1 gives you both feature surfaces.
Upgrading from 1.2.0-alpha3. composer require drupal/lscache:1.2.0-beta1. No code changes; no database updates; no configuration changes; no .htaccess changes.
Production soak invitation. Same as 1.1's beta1: if you have a Drupal site running behind LiteSpeed Web Server with at least one ESI-fragment use case (cart count, welcome banner, notification badge), this is the release that benefits most from broader field signal.
Reporting issues. Use the issue queue, tagged against version 1.2.x-dev. Suspected security issues should go to security@drupal.org rather than a public issue.