Search results

LiteSpeed LScache is a server based cache for dynamically generated sources like PHP. Static sources like css, js or any other static sources are not cached by LScache as such sources are cached by the browser. If you want to set browser caching for static sources you must set either by...

Almost everything is possible, but if you have custom conditions, you need custom configurations of LScache that are not supported by the LScache plugin for WordPress. So please explain what you need. The better your explanation the better the solution can be provided!

https://wordpress.org/support/topic/lscache-plugin-issue/ https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

and reads the restrictions at https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

and read the restrictions at https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

As long as the Drupal cache hasn't been disabled, there's no point in looking for other causes. Currently, the Drupal cache is still active. http://your-domain-name.org/?check-drupal-cache=true

FYI: miss doesn't mean no-cache. If the cache is miss it means that the current cache status is miss, but is currently cached. A URL must be requested to get the hit status displayed with the next request of the same URL. This is how every kind of cache works.

Use the built-in crawler (it's faulty) of the LiteSpeed cache plugin for WordPress to warmup the cache or use the much more faster and smart cache warmup crawler for WordPress and LiteSpeed: https://www.cachecrawler.com/Download/Cache-Warmup-Crawler-LiteSpeed-LScache-Wordpress-Plugin::113.html...

Drupal cache is still running. Check the response header. If you already have disabled Drupal cache you must purge LiteSpeed cache as well.

Please read this before you post: https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

Neither the LiteSpeed LScache Engine nor any LiteSpeed Cache plugin prevents caching with a referrer from Google or any other referrer. However, you should first specify that requests with these referrers will not be cached. Is the x-litespeed-cache-control header miss or no-cache? If you want...

MISS doesn't mean no-cache and Drupal caches the ESI whole. All in all, disable Drupal caching. 1 cache plus 1 cache is not 2 caches.

The Expire header is an outdated method to control the cache behaviour of static sources since it is more likely used as a fallback for older or outdated browsers. Also, the Expire header controls the cache or the TTL by the date create time of a source. Cache-control controls the TTL by access...

Yes. Press the F12 key and select the network tab in browser dev console.

You have a additional cache layer running. This might be the reason for the reported issue. x-drupal-cache

It depends on if you need ESI for PS. ESI is (was in the past) a good idea, but ESI causes other issues you don't want. The best solution would be using PS without ESI and using client side scripting instead, but for this better solution PrestaShop has to be changed to make it more page cache...

LiteSpeed Enterprise is the web server, so it doesn't matter if you use LSWS or OLS. The problem is ESI if ESI is used with Prestashop as this CMS isn't really cache friendly.

It seems that LiteSpeed has disabled ESI for Prestashop as ESI causes issues with the current PS version.

Read this before posting an issue: https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

Disable the PS developer mode, purge the cache and try again. .