Re: DoS issue

Robert Jordan <[email protected]>
Newsgroups gmane.comp.web.fastcgi.devel,gmane.spam.detected
Message-ID <[email protected]>
Arvid Picciani wrote:
> On Wednesday, 15. August 2007 15:04:01 Étienne KASPERCZYK wrote:
>> By "server side busy flag" you mean : an appropriate error code displayed
>> to the end user (which is : the web browser) ?
> no. a flag within the load balancer indicating... load.
>> I've never seen/read anything like this in lighty, but AFAIK there's a
>> "load" integer for each process, and until it doesn't have reached the
>> maximum, it'll just wait. So i guess you'll need to reach the ((max_process
>> * max_load) + 1)th connection to see an error appear.
> nah i don't want any error. even if it would display an error that's even more 
> a DoS.
> the problem is that any aditional requests are ignored instead of starting 
> another instance that can answer those

I know nothing about "lighty", but every other HTTP server I'm aware
of has a configurable request limit. This limit is intended to protect
against a DoS, because w/out such a limit you'd theoretically need
unlimited CPU & memory resources. Very unlikely to have them, no?


Robert

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.