tree c163a09df6b62d7a5664d2c5222ec9e676a7562a
parent 39eb766825d8aad09946dfc284d4a73f610ebd64
author Christopher Faulet <cfaulet@haproxy.com> 1595601074 +0200
committer Christopher Faulet <cfaulet@haproxy.com> 1595836946 +0200

BUG/MEDIUM: mux-h1: Wakeup the H1C in h1_rcv_buf() if more data are expected

After the input processing, in h1_rcv_buf(), if more data are expected and the
H1C is not subscribed on receives, we now wake up the H1C to try to read more
data ASAP. This reverts commit a1dde23e. Depending on how data are received,
subscribing on receives at this stage may freeze the H1 connection because a
read event is missing.

This bug seems to no exist in the 2.2 because of changes on the connection
subscriptions. But we must be careful because I don't really know why the read
event is missed.

Moreover, the bug fixed by the commit a1dde23e will be fixed another way in
the next commit.

This patch should fix the issue #774. It must be backported to 2.0.

(cherry picked from commit 7da9bcc55dd23f155aad4f1376977c5d3f944d7d)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>