Hello!
On Fri, Oct 25, 2013 at 6:48 PM, Maxim Dounin wrote:
>
> Could you please elaborate how do you see the problem? In 1.5.6
> this probably can be triggered with incomplete upstream response,
> which intentionally results in no last buffer send, but with such
> responses nothing is guaranteed anyway. And I don't think there
> are any legitimate ways to trigger it in 1.4.3.
>
This is triggered by my own (3rd-party) module, ngx_lua. This module
provides a ngx.flush(true) API function that flushes out all pending
output data and *wait* (nonblockingly) until all outputs are *indeed*
flushed out (into the system socket send buffer):
https://github.com/chaoslawful/lua-nginx-module#ngxflush
Best regards,
-agentzh
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
