Wordpress LScache Plugin: Some htaccess rules and maintenance mode dont work anymore
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi im on wp 5.5.3 Some htaccess rules dont work anymore with cache ON as deny from all has no effect while deny from XX.X.XXX.XX (my ip) it works perfectly. Also when I try to switch the wordpress to maintenance mode manually with the .maintenance file containing the correct php inside the site is still online, if I switch CacheLookup on to off the maintenance mode appears well i also try to simply clear all cache but nothing work. This topic was modified 1 year, 11 months ago by JibsouX. This topic was modified 1 year, 11 months ago by JibsouX. Hi, Could you please provide the report number you can get it in toolbox -> report -> click send to LiteSpeed Best regards, Hi ! Sorry for the delay, there it is : Num?ro de rapport: JMDDVJZQ Date de rapport: 12/14/2020 16:49:32 Thanks in advance Hi, this is more like a server-side issue instead of plugin-side issue please create a ticket to LiteSpeed Tech by sending mail to support at litespeedtech.com Best regards, mhh in fact, it was a combination of 2 htacess rules for one part of the bug deni from not working : Require all Granted Require not env bad_bot SetEnvIfNoCase User-Agent ^$ keep_out SetEnvIfNoCase User-Agent (binlar|casper|cmsworldmap|comodo|diavol|dotbot|feedfinder|flicky|ia_archiver|jakarta|kmccrew|nutch|planetwork|purebot|pycurl|skygrid|sucker|turnit|vikspider|zmeu) keep_out Order Allow,Deny Allow from all Deny from env=keep_out ? For the other bug maintenance dont work , now it work for all pages except the home page it create cache, then after reload show home page not the default maintenances wordpress page.. for me the website is in a subdomain subdomain.domain. ?. my htaccess is : # BEGIN LSCACHE ## LITESPEED WP CACHE PLUGIN ? Do not edit the contents of this block! ## RewriteEngine on CacheLookup on RewriteRule . ? [E=Cache-Control:no-autoflush] ### marker CACHE RESOURCE start ### RewriteRule wp-content/. /[^/] (responsive|css|js|dynamic|loader|fonts) .php ? [E=cache-control:max-age=3600] ### marker CACHE RESOURCE end ### ### marker FAVICON start ### RewriteRule favicon .ico$ ? [E=cache-control:max-age=86400] ### marker FAVICON end ### ### marker DROPQS start ### CacheKeyModify -qs:fbclid CacheKeyModify -qs:gclid CacheKeyModify -qs:utm CacheKeyModify -qs:_ga ### marker DROPQS end ### ## LITESPEED WP CACHE PLUGIN ? Do not edit the contents of this block! ## # END LSCACHE # BEGIN NON_LSCACHE ## LITESPEED WP CACHE PLUGIN ? Do not edit the contents of this block! ## ## LITESPEED WP CACHE PLUGIN ? Do not edit the contents of this block! ## # END NON_LSCACHE # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index .php$ ? [L] RewriteCond % REQUEST_FILENAME !-f RewriteCond % REQUEST_FILENAME !-d RewriteRule . /index.php [L] # END WordPress # BEGIN LiteSpeed # Les directives (lignes) entre ??BEGIN LiteSpeed?? et ??END LiteSpeed?? sont g?n?r?es # dynamiquement, et doivent ?tre modifi?es uniquement via les filtres WordPress. # Toute modification des directives situ?es entre ces marqueurs sera surcharg?e. SetEnv noabort 1 # END LiteSpeed Thanks in advance ! Hi, yes , with this kind of rewrite rule issue , It is better to be handled by our server staffs instead of here with plugin staffs Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference