On 24/06/10 09:59, Simon Ransome wrote:
Actually, that's such a reasonable idea and seemingly so trivial for Apache (or lighttpd, or a.n.other webserver) to implement it's a wonder that they don't already.
I joined the nginx mailing list and posed the question, and got this response:
Igor Sysoev wrote:
You can run "nginx -t" before applying configuration: it catches almost all possible errors except some fatal errors: no memory, files, etc. If you send -HUP signal to reconfigure and a new configuration is bad, then nginx continues to run with an old configuration, if no fatal errors will happen. SSL certificate without key case is not the fatal error.
I believe Igor is one who would know!
So, it sounds like nginx has a sensible default and has just jumped up the leaderboard quite significantly!