Search results

It seems you have any additional plugin installed that controlls the behaviour of the images and this conflicts with lazy load feature. If case this is a WooCommerce based page you get support for cache plugin only at Wordpress support page for cache plugin. This forum doesn't support LiteSpeed...

@mistwang Why don't you read previous same posts? This is nginx spam?

ngnix spam!

This feature already exists: https://docs.litespeedtech.com/lscache/lscwp/cache/#purge-all-on-upgrade

Don't think complicate, use it and enjoy to save data that has not to be unnecessary downloaded. All, but not LScache extension for OC use this method.

To purge the entire cache you can also use alternative ways and for this you don't have to use curl. Generate a blank PHP page and paste the code below to this file: header("X-LiteSpeed-Purge:*");

Again yes, but this is why request method has explicit to set to override HEAD requuest to GET method.

The next possible reason is that your licence has expired. If you have LiteSpeed web server running and there is no valid license every request will result in a 403 or LiteSpeed web server is switching to Apache.

.... and that's why request method GET has explicit to be set.

Again, request method has nothing to do with "CURLOPT_NOBODY". This curl option has affect on returning message body and depending on the value for this option the ouput of the request will be returned or not. For caching a page you don't need the return and that's why it is better to set value...

This is not a HEAD request. HEAD means only HTTP Header and no message body, but message body is not HTML body. That is a big difference. A only HEAD request prevents to cache a page.

You seem to talk about cache plugin settings of Wordpress? If so, you should know that these forum doesn't support cache plugins, even they are made by LiteSpeed itself. To get support for your issue please check this...

Your issue will be solved here: https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

Maybe I am wrong, but I got an email notification from Google user group that a new version has been released, but I just checked it. I am wrong. This notification is about a user who writes a post about version 1.4, so sorry! :(

Today a new version has been released.

Of course it is matters for both. Unsufficient cache rules causes wrong cached pages. I checked your page today and found some wrongly defined cache rules regarding apple devices.

Yes, but UA is always not really safe and can easily be modifed.

No, I use completely different data. User Agent is yesterday, I use "client hints" https://web.dev/i18n/en/user-agent-client-hints/ https://developer.mozilla.org/en-US/docs/Web/API/User-Agent_Client_Hints_API https://developer.mozilla.org/en-US/docs/Web/HTTP/Client_hints

Yes, for Multithreading Magic Crawler. :) I don't really need these cookies, but they make it easier to define safe cache rules. The current are not really good.

Already all settings tried, but without success...