On Tue, Nov 1, 2011 at 9:56 AM, Maxim D. [email protected] wrote:
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.