Search results

ESI doesn't help in this case, especially since ESI actually worsens performance. Furthermore, in your case there is no function for which ESI could be used. If you have further questions, please use Cache Plugin Support in the Wordpress Forum. This forum no longer provides support for the...

Day 1: No explanation from @blowhard aka @AndreyPopov how to warmup the cache for ESI holes

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

4 hours later. No explanation from @blowhard aka @AndreyPopov how to warmup the cache for ESI holes

Forum Troll

@mkaaaay Does your problem occur with cached URLs?

I changed your nickname from. From now on your name is no longer @AndreyPopov, but @blowhard. Hello @blowhard, how are you doing with your new nickname?

Yes, really. Do you think I tell fairy tales like you?

Dream on... Your cheap excuses confirm once again that you have no idea about a lot of things, especially about ESI.

I am still waiting!

Bulls***! WordPress default session lifetime is 48h.

Okay, teach me how to do, please....

This is ESI. Warmup the cache, please. https://www.dev.cachecrawler.com/esi/

Custom PHP code for session.gc_maxlifetime? Custom lifetime for session cookie? Browser settings?

The problem is the lack of synchronization between the origin host and the CDN node, or the availability of Cache Vary. Quic.cloud was developed specifically for the LiteSpeed Cache Plugin and LScache, but QC does not (yet) support custom cache vary. Also, you can't warm up the cache with QC...

Do you use any plugin for the IP-dependent display of the respective prices?

If you temporarily deactivate quic.cloud and the custom cache vary works, then you know that quic.cloud cannot be used for your needs. The probability is about 100% that QC does not support your cache vary.

If you temporarily deactivate quic.cloud, you will most likely be able to identify the cause.

As long as you just shout, no one will talk to you. The const.default.ini can be changed, but it will be overwritten with the next plugin update. So what are you giving advice that doesn't help anyone. Especially since it is not a good idea to change the TTL for ESI cache because it leads to...

Because you are giving wrong information! Why should I read this? And please don't always yell at me.