Hello! What are you referring too, Node.js commit log? There was indeed a problem with http layer there, but I am not sure, how this could happen on libuv layer.
Cheers, Fedor. On Tue, Mar 25, 2014 at 5:58 AM, Ashish <[email protected]> wrote: > > LIBUV based servers are event based hence they are vulnerable to denial of > service attacks. > > In other words, "sending a large number of pipelined requests without > reading the response" results in generating so huge number of 'read' events > that event loop never triggers any other events. Eventually the server ends > up running out of resources. > > I was just wondering how this can be handled? > > Tnx, > Ashish > > -- > You received this message because you are subscribed to the Google Groups > "libuv" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/libuv. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
