Mohammad2306
I've looked into "x-litespeed-cache hit" that you mentioned and here's what I've done:
- I've examined my server headers using multiple tools, including browser developer tools and online header checkers.
- I've updated my .htaccess file and removed any LiteSpeed Cache-related directives.
- I cleared all caching from Leap Cache section (pubdash.ezoic.com/leap/caching) multiple times.
My findings consistently show that the "x-litespeed-cache" header is no longer present in the responses.
My current server response headers include:
- server: LiteSpeed
- x-turbo-charged-by: LiteSpeed
- cache-control: private, max-age=0, must-revalidate, no-cache, no-store.
These headers indicate that while my server is running LiteSpeed, active caching through LiteSpeed Cache IS NOT OCCURING. The cache-control header is set to prevent caching, which should ensure fresh content delivery.
I believe these changes have addressed the caching issue you identified. Could you please recheck my site to confirm that the "x-litespeed-cache hit" is no longer present? If you're still seeing this header, could you provide more details about how you're detecting it, as I'm unable to replicate this on my end?