Search results

LiteSpeed is Apache compatible and use same rewrite rules like Apache. If you need support for redirections follow Apache documentation. https://httpd.apache.org/docs/2.4/rewrite/

... but only "iphone|ipad" && "Safari" is Safari without webp support, so you don't need to define extra rewrite rules for other UA and you only have to exlude other UA within the same rule. That is what I already tried to explain x-times, but you don't listen!? Device detection in Journal is...

It is already finished, but wait for version 6 of LSWS, because version 6 has some improvements that phpBB will get benefits that are not possible in current version. phpbb is tricky to use with HTTP cache, because of a strange architecture philosophy from previews versions that is still...

A known fact of OLS, but not a hidden secret and can be found in documentation. Use LiteSpeed Enterprise for unrestricted usage. Your rewrite rules don't follow a strict logic to identify/seperate a specific device from others to make webp only available for devices that support webp image...

@merino88 Do you understand why counter doesn't count if a page is cached?

I've just checked current version in plugin code. It seems LiteSpeed removed this setting, but language files still contains it. Wait for LiteSpeed staff or open a support ticket to ask why this setting has been removed.

@lureze Check General tab. It should be in 4th row of settings.

These rewrite rules can't work. They have a lot of logic failures that have nothing to do with reality. They cause conflicts with effects on page load time. You loose more as you believe to win. If each rule would work, every page of your shop would get as much versions of cached page as you...

Support for LSCache plugin for Wordpress: https://wordpress.org/support/plugin/litespeed-cache/ Support for OpenLiteSpeed: https://forum.openlitespeed.org/ LiteSpeed and CyberPanel related support check CyberPanel support forum This forum is for LiteSpeed Enterprise customers.

This test page is not a OpenCart installation and have developed an own plugin (hardcoded), but it doesn't matter if it is custom. The way how LScache works is always the same, but if there is a mobile view some different vary cache conditions and tags are needed. That's why I noticed cache...

@cafemasasandalye I already posted the link to a test page above. This test page simulates device detection to detect if - Mobile or Desktop device if Desktop - is it a windows desktop or Apple if Mac - is Safari or other browser if mobile - is it Android or Apple if Apple - is Safari or...

This can't be fixed with cache rules/settings. There are too much different functions that try to detect what device is used and every function for device detection works different. To get this webp function work with LScache webp plugin must be re-developed to use Client-Side-Includes instead...

Cache for URLs that should not be cached should already be excluded from being cached within cache plugin. If you have pages in checkout that are cached, something is wrong. I am not the developer of this plugin and can't know what is wrong. Open a support ticket to get more qualified support...

If you don't use LScache this is not a LiteSpeed issue. Ask the one who has build the plugin for webp or the one who build this template/theme.

Describe "same problem" Btw: NEVER publish server info. Now everybody knows what software and versions you are running and is able to use leaks to hack your server. Protect infophp from public access!

You can find cache directory for each users home directory. For example: /home/account_name/lscache/* remove all subdirectories within /lscache/* Navigate to home directory of affected account. This will remove all subdirectories and files within /lscache. Do it at your own risk! rm -rf...

If you don't know such simple information you better shouldn't access to cli. It's the "heart" of your server. Find someone who can teach you, so you can learn what to do.

1.) Purge entire Cache 2.) Request a page in shop that is not exluded from being cached. 3.) Check cache header like before 4.) If cache header is miss, everything is okay. 5.) If cache header is hit, wait a few seconds and request same page again. If cache header ist still hit, something is...

hit == cached miss == not cached

Check for "X-LiteSpeed-Cache"response header in browser developer console. hit vs. miss