Wordpress LScache Plugin: Private ESI widget, 0 TTL does not work
Last Updated on: Wed, 15 Apr 2026 00:00:02 I am attempting to use ESI on a recently viewed products woocommerce widget, which is unique per-user. I have enabled ESI and applied the private ESI setting to the widget, with 0 TTL as it should not be cached. The widget does not function correctly even with these settings applied, how can I fix this? I have attempted reinstall of LScache, reset of LSCache settings but nothing has worked yet. Environment report ? YEUZLWIF Hi, how exactly does the widget not functioning ? like the content is still cached or something ? best regards, Its an incredibly strange issue. I have a staging environment (Identical clone to my production), and the widget works fine there. Working fine at staging.merchmeta.com But in production it will not function properly. See merchmeta.com (I sent my environment report from here) Watch how the widget behaves 1. in product catalog sidebar 2. and at bottom of single product page Could this be something to do with the backend setup? Happy to give access to my plesk / production site if required. Thanks Ive realised its because of the quic cloud CDN being used on the production site. When I bypass the CDN on production the widget works as expected. Is there any way of using the recently viewed widget whilst serving the site via the quic cloud CDN? Because it doesnt seem to work when using the CDN I understand this may be a configuration error on my part. I just cant figure the correct settings on both sides (CDN / Lscache) to serve a per-user ESI widget without errors. Similar to this guy ? https://wordpress.org/support/topic/quic-cloud-and-esi/ Hi, this sounds weird Are you running Plesk with LiteSpeed enterprise ? and also please try to grab the debug log it generates with and without QC , specially the part about the ESI block Best regards, Hi, its been confirmed as a Quic CDN issue. Ive been speaking to Kevin from litespeed in slack and he is working on a fix
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference