Search results

If you don't have a control panel like cPanel/WHM or other supported control panel. If you have cPanel and ModSecurity nothing else has to be done.

Static sources like images can't be cached neither by LScache nor any other HTTP Cache. Static sources will automatically be cached by browser.

Try this https://docs.litespeedtech.com/lscache/lscwp/admin/#enabling-the-crawler

Control Panel?

Yes! It's the same like with Apache in .htaccess, but know only REQUEST source. Status code is not supported by Apache. SetEnvIf Request_URI "\.css$ " dontlog SetEnvIf Request_URI "\.js$ " dontlog .... https://httpd.apache.org/docs/2.0/mod/mod_setenvif.html

For Wordpress users: https://docs.litespeedtech.com/lscache/lscwp/ts-optimize/#disk-space-filling-fast

Maybe this could help you to understand why "Google Core Web Vitals" and not Pagespeed is important. Pagespeed is only a test tool. The right score will be generated by each user who has Chrome browser installed. Chrome generates "User Experience Report" and sends data to Google and only these...

Configuration has to be done in Apache style: /etc/apache2/conf.d/includes/pre_virtualhost_global.conf <IfModule LiteSpeed> VhostBandwidthLimit 1024000 </IfModule> For bandwith limit of 1000KB max.. Not tested, but should work.

Did you already check this: https://docs.litespeedtech.com/cp/cpanel/tunings/#virtual-host-level-limiting

Yes, it does. Why shouldn't it support .htaccess or what is not supported?! https://www.litespeedtech.com/products/litespeed-web-server/editions

I just did some further tests and you won't believe it... noconntimeout directive works. It was my fault. A typo in rewrite rule to limit noconnection timeout to the crawler has caused it, so I am very sorry! Ashes on my head! :(

Sorry, this is not great. Offering a CLI variant of crawler is an option, but not the one and only option. This option is intended to run in cronjob, but is only a small part of complex application with a lot of features and functions. This comment is like a knockout for LiteSpeed Enterprise...

For testing and debugging I have the crawler script extracted from main application to get it work in CLI. For this test there is no custom connection timeout in .htaccess defined. The crawler is running without interruption until script it is finished, but only in CLI! To me, it looks like...

Support for OpenLiteSpeed -> https://forum.openlitespeed.org/

Okay, but also need No CLI support.

Not yet, but is on to do list It won't bother? Can you explain that?

For testing crawler warmup the cache for other domain.

No. assets.php -> curl

FYI: QUIC is only supported by Chrome and Opera browser.

You are welcome :)