Search results

The server cache doesn't matter for static sources, but the browser cache, so if you use a different browser always purge the browser cache and press Strg + F5 keys if you want to check it.

@craigward The issue could be caused by the loading="lazy" HTML attribut im <img> tag. Safari browser only supports this feature since version 16.4, or since 2023. This means that users with an older browser will not see any images. https://caniuse.com/?search=loading%3D%22lazy%22

In your first post there is a screenshot that displays CF cache rules for dynamic sources and this conflicts with LScache. FYI: It doesn't matter if you have the APO plugin installed or not. If you cache dynamic sources with CF this always conflicts with any page cache on the origin host. 1...

CacheLookup on RewriteEngine On # Redirect Trailing Slashes If Not A Folder... RewriteRule .* - [E=Cache-Vary:Authorization] </IfModule> Authorization for cache vary doesn't work that way. You should study LScache documentation how LScache works and how to use Cache-Vary. If a...

Please provide the complete .htacces code and check phpinfo() for $_SERVER['X-LSCACHE']

LScache is URL based and not browser based, so there must be any other reason that causes this issue. This must be set in LiteSpeed WebAdmin console and cannot defined in .htaccess CacheEngine on esi crawler You have defined private cache, but no configuration for public cache...

You cannot use 2 page cache types at the same time. This especially true with CloudFlare Cache and LScache. CF and LS cache are incompatible. If you have WordPress and the LScache plugin for WP you can use only LScache. BTW. Read this why you cannot use CF and LScache...

Keep all LSWS settings in Web Admin as they are and don't change any settings if you don't know what you are doing!!! For optimization of LScache settings for the cache plugin there is no universal configuration because configuration depends on the theme and installed plugins. If you don't have...

Nobody wants you to be confused. Just follow the provided sources....

This report number doesn't matter in this forum since this forum doesn't support the LiteSpeed cache plugin for WordPress any longer (and since many years), so please use the LiteSpeed plugin support at WordPress and read this post...

No, but something prevents caching by quic.cloud. Independently from this I can't see what the issue could cause. Do you have cache for private user enabled? If yes, do you check changes as logged in Admin?

I am just checking, please be patient.

A link to your host can help a lot to identify the issue. If you don't want to plublish a URL send a PM.

Right!

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

You cannot use 2 plugins for optimizing and caching.

Disable WP_DEBUG or/and change error logging level to: error_reporting = E_ALL & ~E_WARNING & ~E_NOTICE in php.ini

Did you enable imagick in cPanel configuration (PHP extensions)?

If you have cPanel ask cPanel support how to uninstall and install the correct version for each PHP version, because there is a mismatch between the version of ImageMagick installed and the version that Imagick compiles with. Is this error only generated if you run a specific script?

All LiteSpeed plugins and crawler scripts uses lscache_runner or lscache_walker User-Agent, but there is no documentation about these 2 User-Agents. The last information I got (from @Lauren) many years ago was, that lscache_runner extends the cache lifetime by the set TTL value if the cache is...