haproxy/reg-tests/connection/proxy_protocol_send_unique_id_alpn.vtc
Willy Tarreau 48d5ef363d REGTESTS: restrict execution to a single thread group
When threads are enabled and running on a machine with multiple CCX
or multiple nodes, thread groups are now enabled since 3.3-dev2, causing
load-balancing algorithms to randomly fail due to incoming connections
spreading over multiple groups and using different load balancing indexes.

Let's just force "thread-groups 1" into all configs when threads are
enabled to avoid this.
2025-06-30 18:54:35 +02:00

41 lines
1.0 KiB
Plaintext

varnishtest "Check that the unique ID TLV is properly sent for servers with ALPN option"
#REQUIRE_OPTIONS=OPENSSL
feature ignore_unknown_macro
haproxy h1 -conf {
global
.if feature(THREAD)
thread-groups 1
.endif
defaults
timeout client 30s
timeout server 30s
timeout connect 30s
mode http
log global
unique-id-format %{+X}o\ TEST-%[req.hdr(in)]
listen sender
bind "fd@${feS}"
server example ${h1_feR_addr}:${h1_feR_port} send-proxy-v2 proxy-v2-options unique-id ssl alpn XXX verify none
listen receiver
bind "fd@${feR}" ssl crt ${testdir}/common.pem accept-proxy
http-request set-var(txn.proxy_unique_id) fc_pp_unique_id
http-after-response set-header proxy_unique_id %[var(txn.proxy_unique_id)]
http-request return status 200
} -start
# Validate that a correct header passes
client c1 -connect ${h1_feS_sock} {
txreq -url "/" \
-hdr "in: foo"
rxresp
expect resp.http.proxy_unique_id == "TEST-foo"
} -run