Inconsistent Caching in LiteSpeed Cache: Has Anyone Experienced This?
-
Hello everyone,
I can’t get LiteSpeed Cache to serve cached content for all my pages.
After setting up the LiteSpeed Cache crawlers, they run normally, but in the “Sitemap List” section, I see the crawler status for each URL in green, indicating a 201 response code. I understand that a 201 Created code indicates that a new resource has been created as a result of the request, and this resource is generally not directly cached. However, the response could contain information about the created resource, and if that resource is accessed later with a GET request, then the response for that new request could be cached.
When I load any URL on the website for the first time, I see Status Code: 200 OK and x-litespeed-cache: miss.
When I reload that URL, I then see x-litespeed-cache: hit.
Interestingly, when I load the URLs with the Brave browser, this doesn’t happen, and for all URLs, I can see x-litespeed-cache: hit.
This is a WordPress / WooCommerce installation on a server with elastic hosting and 6 CPU cores. In the .htaccess file, I have:
<IfModule LiteSpeed> CacheEngine on esi crawler </IfModule>But I’m not sure if something else is needed or if this setup is really correct.
Has anyone encountered a similar problem?
- You must be logged in to reply to this topic.
