BUG/MINOR: stconn: Don't disable 0-copy FF if EOS was reported on consumer side
authorChristopher Faulet <cfaulet@haproxy.com>
Thu, 24 Oct 2024 09:53:10 +0000 (11:53 +0200)
committerChristopher Faulet <cfaulet@haproxy.com>
Thu, 24 Oct 2024 10:17:19 +0000 (12:17 +0200)
commitadceb4a595d9dedbcdc1bbf92b38ccc95c2b66ab
treece416ff467eb35f92706ab03dd73e8e0523fb212
parent04b5a16bc273bdcbce76a517ba79be8586c4ebb1
BUG/MINOR: stconn: Don't disable 0-copy FF if EOS was reported on consumer side

There is no reason to disable the 0-copy data forwarding if an end-of-stream
was reported on the consumer side. Indeed, the consumer will send data in
this case. So there is no reason to check the read side here.

This patch may be backported as far as 2.9.

(cherry picked from commit 362de90f3e4ddd0c15331c6b9cb48b671a6e2385)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
include/haproxy/stconn.h