Hi all,
I'm happy member of LiteSpeed standard edition since few years, however now I'm facing some configuration issues.
Does dynamic requests throttling per second work in Standard edition? I didn't find any information that it shouldn't, however - it doesn't seem to.
I'm hosting a website with really heavy and unoptimized SQL queries to big database. Noone optimizes them, because the new website is being created. However we're facing at the moment some easy DoS attack. Attacker sends several (!) GET requests to /index.php per second and this way access for other users is being successfully cut by hanging MySQL connection with waiting or (being executed) queries.
I've set dynamic requests limit to 1/sec on vhost level (on server level it is set to 2), but looks like LS doesn't apply that limit. I cannot block it with iptables, because there is static content (images/css) served as well.
How should I solve the problem? Is it a bug, or just disabled feature which isn't just described as disabled in std version?
Here's a short piece of access.log:
LS version: 4.1.8 std
Thank you for your help!
I'm happy member of LiteSpeed standard edition since few years, however now I'm facing some configuration issues.
Does dynamic requests throttling per second work in Standard edition? I didn't find any information that it shouldn't, however - it doesn't seem to.
I'm hosting a website with really heavy and unoptimized SQL queries to big database. Noone optimizes them, because the new website is being created. However we're facing at the moment some easy DoS attack. Attacker sends several (!) GET requests to /index.php per second and this way access for other users is being successfully cut by hanging MySQL connection with waiting or (being executed) queries.
I've set dynamic requests limit to 1/sec on vhost level (on server level it is set to 2), but looks like LS doesn't apply that limit. I cannot block it with iptables, because there is static content (images/css) served as well.
How should I solve the problem? Is it a bug, or just disabled feature which isn't just described as disabled in std version?
Here's a short piece of access.log:
Code:
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
X.X.X.X - - [23/Jan/2012:14:34:51 +0100] "GET / HTTP/1.0" 200 - "-" "-" "www.mydomain.com"
Thank you for your help!
Last edited: