Home » High Performance, Security, Operations
Lighttpd DoS Tool
Posted on February 1st, 2005 2 Comments »
After seeing lighttpd grow to hundreds of megabytes I couldn’t sleep. It was like tiny chicken has grown into huge monster. After some experimenting I managed to grow monsters myself:
Basically the source of the problem is that lighttpd ignores max request size setting and reads data until it becomes huge and eats all available memory.
Return to Apache? No way. Lighttpd problems are usually solved lightning fast – so a little bit of patience and the cure will be ready.


2 Responses
Maybe the comment a way too late.. but server.max-request-size is/was implemented
Lighttpd bug resolution is quite slow, just take a look at some bugreports to get convinced.