Welcome! Log In Create A New Profile

Advanced

Re: still 400 response code, but so weird this time

August 01, 2013 06:13AM
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 then closes it actively without sending any data to the client?

In any case, is the TCP handshake completed?

I guess that SSL handshakes are already in process, because CPU resource is consumed much.

Just as you said, if the browser rejected my SSL cert, what could I do to solve this issue?

Thanks again.
SubjectAuthorPosted

still 400 response code, but so weird this time

microwishAugust 01, 2013 03:10AM

Re: still 400 response code, but so weird this time

microwishAugust 01, 2013 03:28AM

Re: still 400 response code, but so weird this time

microwishAugust 01, 2013 03:37AM

Re: still 400 response code, but so weird this time

Maxim DouninAugust 01, 2013 05:38AM

Re: still 400 response code, but so weird this time

microwishAugust 01, 2013 06:13AM

Re: still 400 response code, but so weird this time

Maxim DouninAugust 01, 2013 08:04AM

Re: still 400 response code, but so weird this time

microwishAugust 05, 2013 06:14AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 99
Record Number of Users: 7 on March 06, 2014
Record Number of Guests: 165 on April 21, 2014
Powered by nginx    Powered by FreeBSD    PHP Powered    Powered by Percona     ipv6 ready