On Tue, Nov 1, 2011 at 9:56 AM, Maxim Dounin <mdounin@mdounin.ru> wrote:
> Here 16384 bytes has been read from client, and one byte remains
> ("rest 1").  OpenSSL doesn't provide any more bytes and claims it
> needs more network input (2, SSL_ERROR_WANT_READ).
>
> 2011/11/01 12:44:24 [debug] 13689#0: *129 event timer del: 12: 1596563798
> 2011/11/01 12:44:24 [debug] 13689#0: *129 event timer add: 12: 60000:1596564354
> 2011/11/01 12:45:24 [debug] 13689#0: *129 event timer del: 12: 1596564354
> 2011/11/01 12:45:24 [debug] 13689#0: *129 http run request: "/organizations/opscode-btm/nodes/broken?"
> 2011/11/01 12:45:24 [debug] 13689#0: *129 http finalize request: 408, "/organizations/opscode-btm/nodes/broken?" a:1, c:1
>
> Though client fails to provide one more byte.
>
> For me, it looks like problem in client.  It's either calculate
> content length incorrectly or fails to properly flush ssl buffers
> on it's side.

Thanks! I confirmed that it was likely on the client side SSL by
creating a duplicate nginx configuration that lacked SSL, which did
not present the symptoms.

I then narrowed it down to Ruby's SSL implementation and found a
recent bug fix that resolves the issue.

http://redmine.ruby-lang.org/issues/5233

Bryan

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx