Search results

I didn't suggest this: RewriteCond %1 !=%{REMOTE_ADDR} LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't Start With Optimization

Server variables (%{REMOTE_ADDR}) cannot be used for "CondPattern" as Apache and LiteSpeed expect an expression for the CondPattern. For example, this would work: RewriteCond %{REMOTE_ADDR} !^127\.0\.0\.1$ If you really need to compare a cookie with the client’s IP, use the newer expression...

Try this code and use CIDR from googlebot.json but aware that Google changes this list almost daily. allow 66.249.0.0/16; allow 64.233.160.0/19; ... # more CIDRs deny all; LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't...

Your code has a serious errors.... RewriteCond %{REMOTE_ADDR} !^173\.245\. RewriteCond %{REMOTE_ADDR} !^103\.21\. RewriteCond %{REMOTE_ADDR} !^103\.22\. # Add more IPs RewriteRule .* - [F,L] Such IPs are not Google bot, but Google Cloud related, mostly bad bots RewriteCond %{REMOTE_ADDR}...

If you're only focused on PageSpeed, you don't need any training. Once the LiteSpeed web server is installed, install the LScache plugin for WordPress and select a preset. That's it. The presets work very well 9 out of 10 times. The cache function is set automatically by the cache plugin, so no...

Please post the code. LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't Start With Optimization

@LSWSEv634Noob You should not "abuse" the .htaccess if you want to block a huge list of IPs. Blocking by htaccess is not free and costs load. Better use WAF/Proxy or CDN. Blocking IPs by ranges (173.245.48.0/20) doesn't work in .htaccess, neither in LiteSpeed nor in Apache. Define a simple...

https://docs.litespeedtech.com/lsws/cp/cpanel/recaptcha/ LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't Start With Optimization

reCaptcha cannot be controlled cPanel account, but by WordPress installation or document_root. Documentation is your friend. ;) https://docs.litespeedtech.com/lsws/cp/cpanel/wp-protect/ https://docs.litespeedtech.com/lsws/cp/cpanel/recaptcha/ LiteCache Rush - WordPress Performance starts with...

If If access to guest.vary.php is blocked by the server, the issue must be solved by the server and not in cache plugin. LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't Start With Optimization

Basically this forum doesn't support the LiteSpeed cache plugin for WP any longer in this forum, because support for this plugin is only provided at the WP forum. Please read this: https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/ LiteCache Rush...

This is not a LiteSpeed related issue, so please ask the one for support who provides the access to Softaculous. LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't Start With Optimization

It doesn't matter if you use CF APO or not. CF CDN is a page cache like LS plugin and this conflicts. LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't Start With Optimization

You should read this: https://www.cachecrawler.com/Blog/Conflict-between-CloudFlare-APO-and-LiteSpeed::6595.html LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't Start With Optimization

Do you use LSWS or OLS? LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't Start With Optimization

The guest.vary.php file is not removed if the Guestmode is disabled and belongs to the LiteSpeed cache plugin. If you don't want this file from being accessed by anyone just add this single line of code to the root .htaccess outside of cache plugin markers. RewriteRule \guest\.vary\.php - [F,L]

If ESI is enabled in LiteSpeed cache plugin for WP, Brotli isn't supported for dynamic sources. LiteCache Rush - WordPress Performance starts with Prevention, not with optimization. Why WordPress Performance Doesn't Start With Optimization

CIDR-Notation doesn't work in modRewrite because CIDR-Ranges don't understand REMOTE_ADDR in modRewrite. Try this: RewriteCond %{REMOTE_ADDR} ^3\.(\d|[1-9]\d|1[01]\d|12[0-7])\. RewriteCond %{HTTP_USER_AGENT} Mozilla RewriteRule ^.* - [F] or if you don't need User-Agent: <RequireAll>...

The syntax error already starts in "Expected Code". The title tag must not be a part within <symbol></symbol> tag, so correct this code and the VPI function will work correctly again. If you have still questions please read this post before you ask...

Double post: https://wordpress.org/support/topic/remove-dummy-css/