Wordpress LScache Plugin: missing htaccess data
Last Updated on: Wed, 15 Apr 2026 00:00:02 hello and thanks for such a good plugin. i had wp-rocket plugin (which i know is a paid plugin and im neither comparing plugins nor disrespect your efforts). later i purchased a host with litespeed, and deleted the wp-rocket. but as i checked today, wp-rocket left its code in .htaccess file. i compared those codes. and noticed that wp-rocket code has more codes and seemed to be more detailed. now my question is should i keep the wp-rocket codes in htaccess? or should i delete them? will it cause any harm to my speed? please check and see if itll cause any confliction with your codes or not. the code is : # BEGIN WP-Rocket # Use UTF-8 encoding for anything served text/plain or text/html AddDefaultCharset UTF-8 # Force UTF-8 for a number of file formats AddCharset UTF-8 .atom .css .js .json .rss .vtt .xml # FileETag None is not enough for every server. Header unset ETag # Since were sending far-future expires, we dont need ETags for static content. # developer.yahoo.com/performance/rules.html#etags FileETag None Header set X-Powered-By WP-Rocket Header unset Pragma Header append Cache-Control public Header unset Last-Modified Header unset Pragma Header append Cache-Control public # Expires headers (for better cache control) ExpiresActive on ExpiresDefault access plus 1 month # cache.appcache needs re-requests in FF 3.6 (thanks Remy Introducing HTML5) ExpiresByType text/cache-manifest access plus 0 seconds # Your document html ExpiresByType text/html access plus 0 seconds # Data ExpiresByType text/xml access plus 0 seconds ExpiresByType application/xml access plus 0 seconds ExpiresByType application/json access plus 0 seconds # Feed ExpiresByType application/rss+xml access plus 1 hour ExpiresByType application/atom+xml access plus 1 hour # HTC files (css3pie) ExpiresByType text/x-component access plus 1 month # Gzip compression # Active compression SetOutputFilter DEFLATE # Force deflate for mangled headers SetEnvIfNoCase ^(Accept-EncodXng|X-cept-Encoding|X 15 | 15 |- 15 )$ ^((gzip|deflate) s ,? s )+|[X-] 4,13 $ HAVE_Accept-Encoding RequestHeader append Accept-Encoding gzip,deflate env=HAVE_Accept-Encoding # Dont compress images and other uncompressible content SetEnvIfNoCase Request_URI .(?:gif|jpe?g|png|rar|zip|exe|flv|mov|wma|mp3|avi|swf|mp?g|mp4|webm|webp|pdf)$ no-gzip dont-vary # Compress all output labeled with one of the following MIME-types AddOutputFilterByType DEFLATE application/atom+xml application/javascript application/json application/rss+xml application/vnd.ms-fontobject application/x-font-ttf application/xhtml+xml application/xml font/opentype image/svg+xml image/x-icon text/css text/html text/plain text/x-component text/xml Header append Vary: Accept-Encoding # END WP-RocketExpand thanks a lot. Hi, Id definitely get rid of them since youre not using WP Rocket anymore, but if youre not sure, you can take a backup of them before you delete them so that you can always restore them if necessary. Regards. hi @tenkstars. thanks for the help. im not a pro. but from what i understood by looking at the wp-rocket original code was i looked at similarities, and deleted them. so the above code is not being produced in lightspeed cache and somehow is missing i guess. and if another cache plugin is producing these codes, maybe they are good? or maybe lightspeed has not developed their plugin to this extent yet. like the Pre-Load Fonts feature, that wp-rocket has and is such a good option to save site loading time by pre-loading them from the server and also suggested by SEO, but lightspeed cache is starting to think of implementing it. thats why i came here to ask for the plugin author/support opinion on this code to see if its truly harmful? or is it something that is good to be there? Those codes are not shared. They are plugin specific. They would not be used by LSCache plugin. Hi, the code generated by LiteSpeed Cache plugin should be wrapped by # BEGIN LSCACHE and # END LSCACHE Best regards, @tenkstars understood. thank you for the help ^_^ @CacheCrawler thank you for the info.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference