Hi Willy, thank you for the very detailed information.
On Wed, Apr 22, 2015 at 8:57 AM, Willy Tarreau <[email protected]> wrote: > That's normal, this is httpterm and it doesn't monitor the connection while > it's waiting. But in your case it should definitely work. Or it means that > your server ignores the client abort. It would be nice if you could double- > check this. > This could very well be the case. I will check and let you know. If your server does indeed not support client-abort, then there's a > workaround. Haproxy 1.5 supports half-closed timeouts. You can simply > add a directive "timeout server-fin 1s" and it will automatically close > the server connection 1 second after sending it the close if the server > doesn't respond (and then report a server error) : > My server is nginx, I will see if I can configure it to "abortonclose" as well. Otherwise the server-fin option looks viable. I suspect it could match your needs if the normal solution doesn't work. > This *does* require abortonclose since you want the shutdown() to have been > done first. Please keep us updated. > I will let you know, thanks again! Ludovico
