Response Headers: cache-control: no-store, no-cache, must-revalidate




Wordpress LScache Plugin: Response Headers: cache-control: no-store, no-cache, must-revalidate

Last Updated on: Wed, 15 Apr 2026 00:00:02
Hi there, I have been trying to verify if my page is being served from LSCWP, and apparently it is not. I get this information in the Response Headers: cache-control: no-store, no-cache, must-revalidate The folders and cache files are in place, so what is causing this, and how do I solve it? Thanks Hi, Thats default wordpress behavior, you dont need to solve it , as it is not exactly an issue. Best regards, Thanks, of course this is good to know, but how does this match up with your own description of testing if a page is cached, this example is also a WordPress page, but with a totally different test result, so how can this be default wordpress behavior? https://imgur.com/XPsmgTt Opposite to this, no-store, no-cache, must-revalidate seem wrong, can you clarify on this? The case is that no pages seems to be cached at all. Regards Hi, No , they are 2 different things. x-litespeed-cache header is what we need , and it indicates the LiteSpeed cache , which works on server level. and cache-control header is to instruct browser to cache the page or not , and as a dynamic CMS like WordPress, browser should not cache page at all. Best regards, Thanks for clarifying this useful information Best Regards



LiteCache Rush: Speed comes from using less, not from doing it faster



Reference