Wordpress LScache Plugin: my posts do not update on visitor side
Last Updated on: Wed, 15 Apr 2026 00:00:02 hello we have a problem we have a news website when we publish a post it appears correctly in login users ( uploaders side ) but on visitors side post page does not appears post image ( feature image) and I have to clear LiteSpeed cache manually for post page to appear correctly or after a long time from user side I have to clear browser cache to appear post correctly with the latest update I am sure there is something that should configure well in the cache would you help me please The page I need help with: https://www.alborsaanews.com/2022/11/14/1597506 you have cache-control: max-age=3600 this will tell browser to cache page for 1 hour , where wordpress default value is no-cache, max-age=0, must-revalidate where it always asks browser to fetch again from server you have also CF-Cache-status: HIT , cloudflare is caching your page please disable these two things first this is all htaccess file could you tell me what is the reason i change cloudflare setting into respect exist header # BEGIN LSCACHE ## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ## RewriteEngine on CacheLookup on RewriteRule . - [E=Cache-Control:no-autoflush] RewriteRule .litespeed_conf .dat - [F,L] ### marker CACHE RESOURCE start ### RewriteRule app/. /[^/] (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 WEBP start ### RewriteCond % HTTP_ACCEPT image/webp RewriteRule . - [E=Cache-Control:vary=% ENV:LSCACHE_VARY_VALUE +webp] RewriteCond % HTTP_USER_AGENT iPhone. Version/( d 2 ). Safari RewriteCond %1 >13 RewriteRule . - [E=Cache-Control:vary=% ENV:LSCACHE_VARY_VALUE +webp] ### marker WEBP end ### ### marker DROPQS start ### CacheKeyModify -qs:fbclid CacheKeyModify -qs:gclid CacheKeyModify -qs:utm CacheKeyModify -qs:_ga ### marker DROPQS end ### Expand if you set CF to respect existing header, then its something else from your site/server sending out that cache-control header , for CF-cache , it should be coming from CF page cache or CF APO plugin
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference