Search results

@Majorlabel 1. Do not use curl without additional parameters to verify if caching works. This is especially true as you have the Guestmode fetaure enabled that needs Javascript enabled to set the _lscache_vary Cookie for the Guestmode. 2. Disable the Guestmode feature for time being as this...

@neikoloves I've created a special FAQ for you so you can get an idea of what LiteCache Rush is and what it's good for. If you have any further questions, please be patient for a few more days until Rush is available. What is Rush? Rush is a plugin-loading controller for WordPress. It does not...

Open your mind. ;) The internet provides other indicators to distinguish between good and bad guys. Using IP addresses for filtering is not only insecure, but actually outdated.

LiteCache is a registered trademark, and most LiteCache solutions are either based on or designed exclusively for LiteSpeed. LiteCache for Enterprise CMS is a replacement for LiteSpeed LiteMage.

It's not a question of trust. You're trying to protect yourself, and that's fine, but the method you're using to protect yourself is wrong. If you want to stick with this method, then by all means, continue to feel safe. But be aware that server security isn't based on outdated client-side...

I wish you the best of luck in your search for alternatives. However, you probably won't have any luck, because the WordPress community still hasn't grasped the root cause of the problem. So don't waste any more time, disable ESET and learn how to truly solve WordPress performance issues.

While concealing your identity through various means might enhance your safety, it also increases the risk of being identified as a "bad guy" and consequently blocked incorrectly. Traditional methods may work to disguise your identity, but they rely on flawed and outdated criteria. ESET is good...

The country doesn't matter in your case, so again, request cachecrawler.com host and tell me your IP address.

The last block with rayID 9a8b0552c8be97ed was detected by an user that has Chrome version 109. This version in combination with other conditions leads to the block. However, request cachecrawler.com again and tell me the IP address.

The reason you are being blocked: You are using a Chrome browser version that has been considered outdated since 2023.

I'm sorry again if you're still blocked. We don't use CF filter rules, but rather custom rules that have proven effective for 20 years. To determine the reason for your block, please send me your IP address via private message.

Sorry for the block. Unfortunately, you're using an access provider that many "bad guys" use, but you should now have unrestricted access. LiteCache Rush is finished, but it's currently undergoing practical testing with selected users, so you'll likely have to wait until the end of December...

Would you please tell me which country you are from?

@neikoloves Before we talk about your post, we need to clarify what you are referring to, because the topic of this thread is something completely different.

LSAPI_MAX_PROCESS_TIME This variable must be set and changed in web server configuration and cannot be defined in .htaccess. Just read the documentation (for LSWS) as already posted in...

LiteSpeed Enterprise (LSWS) uses LSAPI_MAX_PROCESS_TIME Environment Variable https://docs.litespeedtech.com/lsws/cp/cpanel/long-run-script/#set-lsapi_max_process_time-environment-variable But don't know if OLS supports it. If not, run the script in console.

Caching isn't the problem—quite the opposite. You need the cache so the page doesn't have to be optimized again every time you visit it. Optimization for Nothing and the Speed (Not) for free

@drstranger If you really need a load balancer, then use this: https://www.litespeedtech.com/products/litespeed-web-adc

Thank you - that’s kind of you to say. Rush is still in active development and not publicly available yet. It’s not meant to be a WordPress core feature, but a standalone solution for those who need very fine-grained control over what loads where. It’s almost ready to release, but it will still...

This is not a OLS related issue, but an issue of every modern CMS that uses a PHP framework. Every kind of requested source (also CSS, JS and so on) goes through the index.php and it doesn't matter if a source exists or not. For WP a 404 is the same as status 200. You can free static sources...