tree c14a5a3cac3741ee6d75a78c4ddaf8661fb725c8
parent fac0f8f029cc16f7b12ea8035c2327ac194d40e7
author Christopher Faulet <cfaulet@haproxy.com> 1608300827 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1608300838 +0100

BUG/MEDIUM: mux-h1: Handle h1_process() failures on a pipelined request

On frontend side, when a conn-stream is detached from a H1 connection, the
H1 stream is destroyed and if we already have some data to parse (a
pipelined request), we process these data immedialtely calling
h1_process(). Then we adjust the H1 connection timeout. But h1_process() may
fail and release the H1 connection. For instance, a parsing error may be
reported. Thus, when that happens, we must not use anymore the H1 connection
and exit.

This patch must be backported as far as the 2.2. This bug can impact the 2.3
and the 2.2, in theory, if h1 stream creation fails. But, concretly, it only
fails on the 2.4 because the requests are now parsed at this step.