# Mark HTTP chunk terminator to be flushed

**URL:** <https://www.ruby-forum.com/t/mark-http-chunk-terminator-to-be-flushed/237587>\
**Category:** NGINX\
**Created:** [November 20, 2013, 9:50am UTC](https://www.ruby-forum.com/t/mark-http-chunk-terminator-to-be-flushed/237587 "2013-11-20T09:50:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [November 20, 2013, 9:50am UTC](https://www.ruby-forum.com/t/mark-http-chunk-terminator-to-be-flushed/237587/1 "2013-11-20T09:50:50Z")

</div>

This really only affects SSL connections, where if the buffer with  
chunk terminator is copied into the SSL buffer by itself. Since the  
new SSL buffer has not reached 16k, it’s not flushed thus causing a  
delay in the client seeing it.

---

<div class="post-metadata">

**Author:** ![princenamor](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/c0e974/32.png) [@princenamor](https://www.ruby-forum.com/u/princenamor)\
**Post date:** [November 20, 2013, 11:41am UTC](https://www.ruby-forum.com/t/mark-http-chunk-terminator-to-be-flushed/237587/2 "2013-11-20T11:41:14Z")

</div>

Hello!

On Wed, Nov 20, 2013 at 12:50:00AM -0800, John W. wrote:

> This really only affects SSL connections, where if the buffer with  
> chunk terminator is copied into the SSL buffer by itself. Since the  
> new SSL buffer has not reached 16k, it’s not flushed thus causing a  
> delay in the client seeing it.

I don’t think that unconditionally setting flush flag is a good  
idea, it will cause unneeded work if a flush isn’t needed.

It may make sense to set it (or move?) if previous buffer has it  
set though.

–  
Maxim D.  
[http://nginx.org/en/donation.html](http://nginx.org/en/donation.html)