On Wed, Jan 05, 2022 at 10:53:24PM +0100, William Dauchy wrote:
> Avoid closing idle connections if a soft stop is in progress.
> 
> By default, idle connections will be closed during a soft stop. In some
> environments, a client talking to the proxy may have prepared some idle
> connections in order to send requests later. If there is no proper retry
> on write errors, this can result in errors while haproxy is reloading.
> Even though a proper implementation should retry on connection/write
> errors, this option was introduced to support back compat with haproxy <
> v2.4. Indeed before v2.4, we were waiting for a last request to be able
> to add a "connection: close" header and advice the client to close the
> connection.
(...)

Perfect, thank you William! I've just added a small paragraph to the
doc mentioning the impact of using this for those with long idle
connections, and pointers to the relevant options timeout client,
timeout http-request and hard-stop-after. I could also have added
timeout http-keep-alive by the way. Regardless all of them are
cross-references, that should be enough.

Now merged, thank you!

Willy

Reply via email to