# SOLVED: Timeout when sending over 16k of data with UTF-8 characters

**URL:** <https://www.ruby-forum.com/t/solved-timeout-when-sending-over-16k-of-data-with-utf-8-characters/213690>\
**Category:** NGINX\
**Created:** [November 9, 2011, 2:31am UTC](https://www.ruby-forum.com/t/solved-timeout-when-sending-over-16k-of-data-with-utf-8-characters/213690 "2011-11-09T02:31:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [November 9, 2011, 2:31am UTC](https://www.ruby-forum.com/t/solved-timeout-when-sending-over-16k-of-data-with-utf-8-characters/213690/1 "2011-11-09T02:31:38Z")

</div>

On Tue, Nov 1, 2011 at 9:56 AM, Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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.

> **[Backport #5233: OpenSSL::SSL::SSLSocket has problems with encodings other...](https://redmine.ruby-lang.org/issues/5233)**
>
> Redmine

Bryan