Search results

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...

@thomaslower Welcome to OpenLiteSpeed ;) What else do you want to tell us?

RewriteCond %{HTTP_COOKIE} font [NC,OR] RewriteCond %{HTTP_COOKIE} theme [NC] RewriteRule .* - [E=Cache-Control:vary=font_or_theme]

@stevieosaurus Please check PHP settings for output_buffering. This should be 4096.

WordPress - Why Performance Doesn't Start With Optimization Most performance issues in WordPress don’t come from poor optimization — they come from WordPress doing too much by default. This post breaks down the hidden mechanics behind slow sites, misunderstood tools like PageSpeed, and why...

Every http request creates a cache copy, but the correct cache copy for the relevant CMS needs more than a User-Agent. You're still a long way from being able to provide a working solution. You know how to use curl and how to parse a sitemap file, but nothing more.

As already said, you know nothing about how LScache works. This code is for universal use, but doesn't work for LScache.

@gospodinov You don't understand how LiteSpeed LScache works. Please invest some hours and learn before you post unqualified stuff.