Search results

"Reduce to the Max" ;)

Check "Wrst" column. There are many hosts with a high rate of data loss. Either your host company has bad peerings or your own network connect into the Internet is bad. To find out which one is bad this test must be done again, but from your server to your PC, but that needs access to CLI...

What is about Android devices? Or Opera Mini for mobile? and so on.... Forget it. That can't be solved, because there are 3 functions in your shop that try to detect devices.

You can test it. Download https://sourceforge.net/projects/winmtr/. Execute WinMTR.exe and enter domain name or IP of your server and let it run a few minutes. Stop it, export result and post it.

That is what I prophesied. 1 faked UA is enough to destroy the best solution, but it is not my fault. My test page works without errors, but also can be faked. This is inherent in the system without any alternative. You better should reduce the amount to transfered data, but not in better...

Yes, it's normal, but not only with LiteSpeed. This is a typical behavior with almost every kind of cache and CDN. If you you change something you must purge cache and CDN for each time you change something.

PageSpeed Insight uses this UA for Desktop: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3694.0 Safari/537.36 Chrome-Lighthouse This UA has no cache-control like every other non Mac and non Safari desktop device. This is a default setting in OpenCart with...

! must be between "!". Was wrong in last try. Bot for Google Mobile has no "Googlebot-Mobile" UA. That's why i marked the current cache-control define for mobile view should to be redefined The current UA for Google Mobile: Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P)...

Next try. :) For this next try I setuped a test page and it works with and without Lscache. If It doesn't work for you, it's not my fault. In this case either device detection in OpenCart/Journal3 or Webp plugin has a wrong detection. You can test it on this test page if you have a browser...

I can't promise, but I believe I have a solution, but must still test it.

Forget it! None of this code will work, because you have 3 functions that try to detect device: - LiteSpeed - Journal3 - and this plugin for webp Every function for device detection works independent from each other. No way to solve it!

There is a way to make it possible, but only with a very complex kind of chache-control definition. No. https://httpd.apache.org/docs/2.4/rewrite/flags.html Scroll down to: "NC|nocase

Use an alarm clock and set "wakeup time" to the defined time after you purged cache ;)

If you ask for an explanation about what you basically not understand how WP and LiteSpeed cache works, will force more questions. Believe me! So, the only answer I will give you, is that this configuration is static cache related and defines when cache of static sources will expire. End of...

I've tested it and can confirm your result. I overlooked that "Safari" is always part of every Mozilla based UA, so my code can't work and have no idea how to solve, sorry.

Yes, but your questions are mostly WP related and this forum doesn't support WP related issues! When will you respect this?! This is a WP related question.

You don't give up.....? ;) 3600 = 3600 seconds = 3600 / 60 = 60 minutes / 60 = 1 hour = cache will expire in 1 hour 86400 = calc by your own ;)

That's not completely right. LiteSpeed caches also static sources, if static sources like CSS are generated by PHP. Such static sources get cache header and can be found in /lscache directory. Cache plugin for WP has an own cache-control define for this.

Some hosts don't allow custom .htaccess and will be renamed if detected.....

LScache plugin for PrestaShop should have an editor mode like in cache plugin for Wordpress. If Presta plugin always overwrites custom settings you can't use the modified code.