MEDIUM: mux-h1: Use a h1c flag to block reads when splicing is in-progress
authorChristopher Faulet <cfaulet@haproxy.com>
Mon, 21 Sep 2020 09:47:16 +0000 (11:47 +0200)
committerChristopher Faulet <cfaulet@haproxy.com>
Fri, 4 Dec 2020 13:41:48 +0000 (14:41 +0100)
commitae635766f6947fe239b33a5b3b1641b697a6fccc
tree716cf73703dd9bfcc63df6dd63584e8fdaf13426
parent089acd5b0d0f735295289fc2479493c397471024
MEDIUM: mux-h1: Use a h1c flag to block reads when splicing is in-progress

Instead of using 2 flags on the H1 stream (H1S_F_BUF_FLUSH and
H1S_F_SPLICED_DATA), we now only use one flag on the H1 connection
(H1C_F_WANT_SPLICE) to notify we want to use splicing or we are using
splicing. This flag blocks the calls to rcv_buf() connection callback.

It is a bit easier to set the H1 connection capability to receive data in
its input buffer instead of relying on the H1 stream.
src/mux_h1.c