Search results

Static Requests/Second 20 Dynamic Requests/Second 1 Connection Soft Limit 10 Connection Hard Limit 20 Grace Period (sec) 30 Banned Period (sec) 300 Request rate limit is only available in Enterprise edition.

Yes, it should, you need to use it together with iptables to block offending IPs. A user review http://www.webhostingtalk.com/showthread.php?t=616249

When properly configured, 3 machine cannot take down the server. For best DDoS protection, please apply a trial key of LSWS enterprise. Besides LSWS configuration, your linux kernel need to be configured properly as well.

Some features like request rate limits are only available for enterprise license.

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi

build php-5.2.5 through our web console. then change php handler from lsphp4 to lsphp5 external app.

Those should be added automatically when "Rails" Context are used. If you configure the rails application manually, you need to add those rewrite rules.

Both should work, with former, you may need to clear the extension_dir configuration in php.ini.

We never tried it. The way LiteSpeed integrated with control panel should work with any control panel uses Apache.

You should do it in your control panel when LiteSpeed used together with control panel.

No, LiteSpeed does not suffer from this problem. All pending requests should be finished by previous instance of lshttpd/lsphp.

check the configuration added to the "Using Apache configuration" table under "server"->"general" tab.

We will try.

Thanks, we aware of it. Low priority and won't really affect anything. ;)

Why you want to use Fast CGI PHP? OUr LSAPI PHP is better. Have you built the FastCGI PHP binary?

Thanks for the the feature requests. For 1), please check our Anti-DDoS feature: http://www.litespeedtech.com/how-tos.html#qa_dos Not exactly the same, but pretty useful as well. Some of them are only available to Enterprise. We will improve that. For 2), have no plan to implement this yet...

We are going to create the audit log as Apache's.

We have been tuning our setup to fend off a DoS attack since Netcraft mentioned LiteSpeed in its latest web server market share report. It is really a shame to the one who attacking us. they should try to improve the quality and performance of Apache, instead of trying to bring down our web site.

We failed to reproduce the 404 page problem. The server will send the hard coded 404 page when there is problem to serve the custom one. You can turn on the detail debug logging by changing "Debug Level" to "HIGH".

Maybe later today or tomorrow.