Server-side caching layer on asquaresolution.com (WordPress). LiteSpeed Cache operates at the server level and caches full HTML responses. Client-sent Cache-Control: no-cache headers are ignored for cache bypass decisions — they only control browser cache behavior. After any WordPress PHP filter or WPCode snippet deployment, LiteSpeed → Purge All must be run before verification. This behavior is a documented operational failure pattern.
Operational records — 3 total
Complete visual evidence archive for the A Square Solutions Phase 2 WordPress ecosystem rollout (2026-05-20). Schema deployment, homepage sections, footer widget, About page, internal links, and LiteSpeed cache purge — every step captured with production screenshots and operational commentary.
Deployed a WPCode PHP filter to fix HFE wpautop injection. curl verification with Cache-Control: no-cache still returned stale cached HTML. Fix appeared not to work — it had worked. LiteSpeed had already cached the old output.