REGTESTS: http-messaging: always send RFC8441 client settings to use ext connect

The tests were validating extended connect without sending the setting
in the client settings frame. It currently works due to a bug, so let's
fix the vtc first.
This commit is contained in:
Willy Tarreau 2026-05-05 13:24:50 +02:00
parent 166dfcbbee
commit 47bb725d88
2 changed files with 10 additions and 5 deletions

View File

@ -219,7 +219,8 @@ client c1_h1_h2 -connect ${hap_frt_h1_h2_sock} {
client c2_h2 -connect ${hap_frt_h2_sock} {
txpri
stream 0 {
txsettings
# manually send RFC8441 SETTINGS_ENABLE_CONNECT_PROTOCOL
sendhex "00 00 06 04 00 00 00 00 00 00 08 00 00 00 01"
rxsettings
txsettings -ack
rxsettings
@ -245,7 +246,8 @@ client c2_h2 -connect ${hap_frt_h2_sock} {
client c3_h2_h1 -connect ${hap_frt_h2_h1_sock} {
txpri
stream 0 {
txsettings
# manually send RFC8441 SETTINGS_ENABLE_CONNECT_PROTOCOL
sendhex "00 00 06 04 00 00 00 00 00 00 08 00 00 00 01"
rxsettings
txsettings -ack
rxsettings
@ -339,7 +341,8 @@ client c8_h2c -connect ${hap_frt_h1_h2c_sock} {
client c9_h2c -connect ${hap_frt_h2_h1_sock} {
txpri
stream 0 {
txsettings
# manually send RFC8441 SETTINGS_ENABLE_CONNECT_PROTOCOL
sendhex "00 00 06 04 00 00 00 00 00 00 08 00 00 00 01"
rxsettings
txsettings -ack
rxsettings

View File

@ -177,7 +177,8 @@ client c3 -connect ${hap_fe2_sock} {
client c4 -connect ${hap_fe3_sock} {
txpri
stream 0 {
txsettings
# manually send RFC8441 SETTINGS_ENABLE_CONNECT_PROTOCOL
sendhex "00 00 06 04 00 00 00 00 00 00 08 00 00 00 01"
rxsettings
txsettings -ack
rxsettings
@ -205,7 +206,8 @@ client c4 -connect ${hap_fe3_sock} {
client c5 -connect ${hap_fe4_sock} {
txpri
stream 0 {
txsettings
# manually send RFC8441 SETTINGS_ENABLE_CONNECT_PROTOCOL
sendhex "00 00 06 04 00 00 00 00 00 00 08 00 00 00 01"
rxsettings
txsettings -ack
rxsettings