Hi Serpentdriver,
Thanks a lot for your very well argued answer.
I know there are “multiple version” of what Litespeed cache can deliver. Here, no guestmode, no mobile cache, etc, just webp and Not webp.
But there is definitely something I don’t understand.
Crawler tells me that my 460 pages are “already in cache” (green status in crawler), but when I visit a random page at 00:20:30, I found in body:
<!– Page optimized by LiteSpeed Cache @2022-10-04 00:20:31 –>
<!– Page generated by LiteSpeed Cache 5.2.1 on 2022-10-04 00:20:30 –>
<!– X-LiteSpeed-Cache-Control: public,max-age=604800 –>
<!– X-LiteSpeed-Tag: 219_HTTP.200,219_product,219_URL./produit/collier-co025-apatites-sainte-lucie-naturelles/,219_Po.12441,219_ –>
<!– Object Cache [total] 25399 [hit_incall] 24681 [hit] 488 [miss_incall] 199 [miss] 31 [set] 18 –>
The second line tells me that Litespeed has just generated this page, at this instant, not before. which means that this page had not been seen before.
Am I wrong ?
And for this page, Response Headers tells me:
x-litespeed-cache-control: public,max-age=604800
x-litespeed-tag: 219_HTTP.200,219_product,219_URL./produit/collier-co025-apatites-sainte-lucie-naturelles/,219_Po.12441,219_
x-lsadc-cache: miss
which means that this page wasn’t in cache.
A second visit tells me
x-lsadc-cache: hit
So something is not logical: if the crawler did its job then the 460 pages should be HIT, I should not find any page as MISS.
That’s why I was wondering if the crawler was telling me the truth !
Perhaps I don’t understand something.
Thanks again for your time.
Best regards