Issues with LiteSpeed ??Cache

x-litespeed-cache header exists, but if quic.cloud is used this headers name is x-qc-cache: https://i.postimg.cc/N0CtxLbM/cache.png

So if so, yes and I activate LiteSpeed ????Cache Crawler, why does it not work properly and it makes me a Cache Miss cache and the web stops being displayed once the cron Crawler process is finished, showing the web header then being well displayed and cached successfully in LiteSpeed ??Cache Crawler.

There is no real reason why the crawler shouldn’t work. The crawler only simulates URL requests, which is the same as a normal user would visit a page. Unfortunately, your information is not very meaningful, so that one can recognize from it what the problem is. It might help if you take a screenshot of the page after the crawler is finished.

I attach URL of the screenshot to better see the problem that I mentioned.
https://drive.google.com/file/d/1ROZKxpeEPnDu0xXT8zlnhPo9JN9NFB41/view?usp=sharing

Did you install any Service-Worker plugin?

Not to my knowledge, but I don’t know if it could be the next plugin that affects the cache, the “Progressive Web App”.

I have the Offline browsing function of Progressive Web App disabled because there is no incompatibility with LITESPEED.

I have the Offline browsing function of Progressive Web App disabled because there is no incompatibility with LITESPEED.

Who did that say?

Anyway, lscache plugin works. If it doesn’t the reason for malfunctions is mostly caused by users they don’t really know what they are doing. I respect it when users make an effort to optimize their page, but you have to be careful with it. Any changes involve the risk of malfunctions. This applies equally and especially to plugins. In any case, your problem is self-inflicted. Therefore, it’s your job to find out which setting or plugin is causing this problem.

Your page uses server worker and this could be the reason for your issue!

• This reply was modified 2 years, 2 months ago by serpentdriver.
• This reply was modified 2 years, 2 months ago by serpentdriver.

Could it be that PWA v0.7.1 is causing the problem when using “wp_front_service_worker” from the “wp.serviceworker” file

Could it be that PWA v0.7.1 is causing the problem when using “wp_front_service_worker” from the “wp.serviceworker” file

Disable this functions and see what happens. I am very sure that this is the cause.

• This reply was modified 2 years, 2 months ago by serpentdriver.

Deactivate the PWA v0.7.1 as you can see on the web, but the same thing happens with the web, once the process in LiteSpeed ??Cache Crawler is finished and forced to cache those non-cached webs, the web continues to look the same and has not been solved the problem.

I close as a result because with the support technician I solved the problem

The support technician is: Ruikai Wang at LiteSpeed ??(@qtwrk)

The solution was to disable multiPHP compression and disable zlib.output_compression, as LiteSpeed ??server has its own compression enabled by default, and also remove from wp-config.php the parameters I added for compression.