From: Christopher Faulet <cfaulet@haproxy.com>
Date: Thu, 7 May 2026 14:15:54 +0000 (+0200)
Subject: REGTESTS: Fix h1_to_h2_upgrade.vtc to force h2 on first bind line
X-Git-Tag: v3.4-dev11~11
X-Git-Url: http://www.kaiwu.me/postgresql/commit/static/gitweb.js?a=commitdiff_plain;h=972d0a41835700b89fe2eab60528756705361c37;p=haproxy.git

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.
---

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