Hi Maxim, I get it now. Thanks a lot for your help!by gunblad3 - Nginx Mailing List - English
Hi guys, Would like to clarify on what client_header_timeout means exactly. http://wiki.nginx.org/NginxHttpCoreModule#client_header_timeout Using the default setting of 60 seconds, does it mean that the server times out the request: 1) if no additional request headers are received in 60 sec since the last one or 2) if the request (headers) should have completed within 60 sec of the startby gunblad3 - Nginx Mailing List - English
Thanks a lot Maxim!by gunblad3 - Nginx Mailing List - English
Thanks Maxim, that's the most informative info on this I've seen so far :) What I meant by my third question was: where/how does nginx cache incomplete requests that are "still being sent" from the client(, if it does so in the first place)? In memory?by gunblad3 - Nginx Mailing List - English
Sorry for the late reply, was flooded with other things ;) I tried by adding worker_rlimit_nofile 10240; instead and it worked with 10000 connections. Have a few questions: 1) Is there a implicit default max number of file descriptors set for worker_rlimit_nofile? 2) How does worker_rlimit_nofile and ulimit affect the actual max number of file descriptors? 3) How does nginx handle uby gunblad3 - Nginx Mailing List - English
I'm looking to test out nginx with the Slowloris tool (http://ha.ckers.org/slowloris/), and I noticed that the following error appears a LOT in the error logs at one point: accept() failed (24: Too many open files) while accepting new connection This is what happens: 1) started nginx on a Debian machine, and the Slowloris tool on another using default parameters (1000 connections, 100 sec timby gunblad3 - Nginx Mailing List - English
try this: - root /home/me/www/public; + alias /home/me/www/public;by gunblad3 - Nginx Mailing List - English