Forum: NGINX Mark HTTP chunk terminator to be flushed

D7ae0b9a7a7dac25f83121ff45877be7?d=identicon&s=25 John Watson (Guest)
on 2013-11-20 09:50
(Received via mailing list)
Attachment: flush_chunk_terminator.patch (555 Bytes)
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.
A8108a0961c6087c43cda32c8616dcba?d=identicon&s=25 Maxim Dounin (Guest)
on 2013-11-20 11:41
(Received via mailing list)
Hello!

On Wed, Nov 20, 2013 at 12:50:00AM -0800, John Watson 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 Dounin
http://nginx.org/en/donation.html
Please log in before posting. Registration is free and takes only a minute.
Existing account

NEW: Do you have a Google/GoogleMail, Yahoo or Facebook account? No registration required!
Log in with Google account | Log in with Yahoo account | Log in with Facebook account
No account? Register here.