still 400 response code, but so weird this time

Maxim Dounin mdounin at
Thu Aug 1 12:02:11 UTC 2013


On Thu, Aug 01, 2013 at 06:13:00AM -0400, microwish 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 then closes it
> actively without sending any data to the client?

A client opens a connection, and then closes the connection.

> 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?

First of all, you should check if it's the case.  If it is, you 
should investigate further why the browser rejects the cert - 
there are plenty of possible reasons.

Maxim Dounin

More information about the nginx mailing list