Search results

Stupid question! Answer: To make it work. You advertise your custom solution as a working solution, but your solution doesn't work. Then why are you asking such a stupid question?!

I think you have the wrong idea about how to run a website. LiteSpeed is primarily a provider of an alternative web server. But running a website requires more than just a web server. You either have to add the necessary information manually or expand the settings of the server control panel you...

You should use LiteSpeed's cache plugin suppport at WordPress. Only there you will get qualified support for this issue because this forum doesn't support cache plugin for WordPress any longer. https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/...

Whitelisting a URL does not solve the problem and is not caused by RankMath. There must be deeper causes for overload. A 503 error code can also be caused by exceeding the max_execution_time. The relevant error logs should provide information about this. Without appropriate error logs it is...

This is ModSecurity, but not LiteSpeed related, so it is up to you to modify ModSecurity rules.

I am always shure! Who is the LiteSpeed expert? Answer: Not you! Just delete the _lscache_vary cookie and request a URL again with different User-Agent. The _lscache_vary cookie is not set again. Device Detection works at your page, but only if a page isn't cached yet. This means that your...

Again, your device detection doesn't work, because your PHP detection isn't completely sync with cache varies.

Nothing is perfect, because not OS version matters, but the Safari Version. Safari webp support starts with version > 13, so stop talking nonsense again.

FYI: Your webp detection doesn't work.

You can't think as far as I can. :) I don't have to do anything. I don't need any extra programming, no extra function, no device detection and no extra cache and I can still offer all image types from avif to webp to png. Native HTML does the trick.

You don't need any device detection if you use HTML picture tag. With picture tag the browser itself checks which image type he supports. At cachecrawler.com I use picture tag and can provide all image types without any detection or cache vary.

@AndreyPopov You don't need an extension for OC because everything you need is already on your server. You also don't need a device detection to identify avif or webp support and you don't need cache varies either. All you need is this: #!/bin/bash # Path to image directory...

There will not be a module for OC or Journal 3 because, on the one hand, an alternative cache plugin would be needed that would also overwrite the relevant functions in Journal. I can only imagine this as a custom solution.

1 example of several. https://www.wp.cachecrawler.com/ Free to download. https://www.cachecrawler.com/WP-Plugins/WP-Plugin-avif-webp-Replacement-for-LiteSpeed-LScache::6574.html

Of course! At least I developed a working solution.

$_SERVER['HTTP_ACCEPT']: image/webp is the same as $_SERVER['HTTP_ACCEPT']: */* That's why all method using this way of detection are faulty.

@barin691 This forum is for LiteSpeed Enterprise. For OLS please use OLS support forum. https://forum.openlitespeed.org/

@ricardomecca Would you provide us with a link to your page?

Please WordPress support forum for the LiteSpeed cache plugin. Only there you will get support. This forum doesn't support the cache plugin any longer.

If you know what ESI is and how ESI works then you have the answer for your question or have a look at this ESI example: https://www.dev.cachecrawler.com/esi/