Hello there,
code snippet in the definition of ngx_chain_add_copy in ngx_buf.c:
ll = chain;
for (cl = *chain
Hi Maxim,
Now I'm sure that the 400-related logs in access log file are caused by bad
SSL connections, which either finish SSH handshakes and then sending no
data, or don't finish SSH handshake at at.
I'll be diving into it for more insights.
Thank you.
Maxim Dounin Wrote:
--
Thanks, Maxim.
By "Such lines in access log are caused by opening and closing a connection
without sending any data in it", you are meaning that a client opens a
connection and then closes the connection actively without sending any data,
or that a Nginx worker process accepts a connection and the
more additions:
some SSL related config in Nginx config file
ssl_protocols SSLv3 TLSv1;
ssl_ciphers RC4:AES128-SHA:3DES:!EXP:!aNULL:!kEDH:!ECDH;
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241435,241441#msg-241441
___
ngi
addtions:
no corresponding logs in error_log.
Nginx version: 1.2.4
OpenSSL version: OpenSSL 1.0.1e
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241435,241439#msg-241439
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mail
In access_log file, huge numbers of log entries like this:
115.85.238.34 1764839163 - 0.242 [01/Aug/2013:11:02:01 +0800] "foo.bar.com"
"-" 400 0 "-" "-" "-"
log_format defined in http conf block:
'$remote_addr $connection $remote_user $request_time [$time_local]
"$hostname" "$request" $status $
