MEDIUM: mux-quic: Don't expect data from server as long as request is unfinished
As for the H1 and H2 stream, the QUIC stream now states it does not expect
data from the server as long as the request is unfinished. The aim is the
same. We must be sure to not trigger a read timeout on server side if the
client is still uploading data.
From the moment the end of the request is received and forwarded to upper
layer, the QUIC stream reports it expects to receive data from the opposite
endpoint. This re-enables read timeout on the server side.
diff --git a/include/haproxy/mux_quic.h b/include/haproxy/mux_quic.h
index 1d5b962..4486231 100644
--- a/include/haproxy/mux_quic.h
+++ b/include/haproxy/mux_quic.h
@@ -98,6 +98,7 @@
qcs->sd->se = qcs;
qcs->sd->conn = qcc->conn;
se_fl_set(qcs->sd, SE_FL_T_MUX | SE_FL_ORPHAN | SE_FL_NOT_FIRST);
+ se_expect_no_data(qcs->sd);
/* TODO duplicated from mux_h2 */
sess->t_idle = tv_ms_elapsed(&sess->tv_accept, &now) - sess->t_handshake;
diff --git a/src/mux_quic.c b/src/mux_quic.c
index a78f8d4..a1cb667 100644
--- a/src/mux_quic.c
+++ b/src/mux_quic.c
@@ -2423,9 +2423,15 @@
se_fl_set(qcs->sd, SE_FL_ERROR);
/* Set end-of-input if FIN received and all data extracted. */
- if (fin)
+ if (fin) {
se_fl_set(qcs->sd, SE_FL_EOI);
+ /* If request EOM is reported to the upper layer, it means the
+ * QCS now expects data from the opposite side.
+ */
+ se_expect_data(qcs->sd);
+ }
+
if (b_size(&qcs->rx.app_buf)) {
b_free(&qcs->rx.app_buf);
offer_buffers(NULL, 1);