Support

The reason you get a warning in the .htaccess Maker is that .htaccess files only work with Apache and partially with Litespeed (some features are not implemented by Litespeed).

Repair and Optimise tables has nothing to do with .htaccess files. It only works with your database. MariaDB 10.3 is compatible with it just fine.

I do not currently have a Litespeed server to test so I can't tell you within any degree of certainty what works and what doesn't. Litespeed is paid web server software only available to large customers (hosting companies). We cannot obtain a copy of it.

While Rochen, our host, does offer the option to use Litespeed I asked them to use Apache for our virtual server because a. I know how Apache works and this is reflected on our .htaccess Maker and b. our site is behind CloudFlare CDN meaning that we would get no performance benefits from using Litespeed. As a result my last first hand interaction with a Litespeed server has been nearly 10 years ago.

Please do follow the instructions we have on the .htaccess Maker documentation. Start with all options disabled and start enabling them one by one to see what works on your server. Even with Apache, some features may be incompatible with the server depending on how the host has configured Apache. I don't know if Litespeed gives the host this kind of latitude in server configuration but I suppose it does. So it really all depends on the server configuration.

No, you misunderstood.

The reason for using Litespeed is that Litespeed is usually faster than Apache serving static files (and only in this case). First of all, this is not 100% accurate. I know how to configure Apache to be just as fast or faster than stock Litespeed. But that's besides the point here.

Our site is already behind CloudFlare CDN. This means that the static files are not served by our server, they are served by CloudFlare CDN. That's the entire reason for using CloudFlare. It caches the static files and delivers them to our clients from edge nodes which are closer to our clients and which respond much faster than our web server could possibly do.

Our web server only serves dynamic content (PHP). The speed of PHP execution depends only on PHP, the script and the database server. It does NOT depend on the web server at all.

As a result we have no reason to use Litespeed over Apache.