From 972d0a41835700b89fe2eab60528756705361c37 Mon Sep 17 00:00:00 2001 From: Christopher Faulet Date: Thu, 7 May 2026 16:15:54 +0200 Subject: [PATCH] REGTESTS: Fix h1_to_h2_upgrade.vtc to force h2 on first bind line With VTEST, It seems possible to receive the H2 preface in 2 packets. So the preface cannot be matched and the H1 to H2 upgrade is not performed as expected. The script was fixed by forcing the H2 proto on the first bind line. The problem with the preface matching will be reviewed later. --- reg-tests/http-messaging/h1_to_h2_upgrade.vtc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reg-tests/http-messaging/h1_to_h2_upgrade.vtc b/reg-tests/http-messaging/h1_to_h2_upgrade.vtc index 30f668fe3..e5d76da4c 100644 --- a/reg-tests/http-messaging/h1_to_h2_upgrade.vtc +++ b/reg-tests/http-messaging/h1_to_h2_upgrade.vtc @@ -28,7 +28,7 @@ haproxy h1 -conf { timeout server "${HAPROXY_TEST_TIMEOUT-5s}" listen feh1 - bind "fd@${feh1}" + bind "fd@${feh1}" proto h2 bind "fd@${feh2}" proto h1 server s1 ${s1_addr}:${s1_port} } -start