Files
haproxy/reg-tests/checks/http-monitor-uri.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

61 lines
1.4 KiB
Plaintext

varnishtest "Test the HTTP directive monitor-uri"
# This config tests the HTTP directive monitor-uri. Especially the path matching
# when an absolute-form uri is received from the client. But also the
# case-sensitivity of the matching.
feature ignore_unknown_macro
haproxy h1 -conf {
global
.if feature(THREAD)
thread-groups 1
.endif
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
frontend fe1
bind "fd@${fe1}"
monitor-uri /health
frontend fe2
bind "fd@${fe2}"
monitor-uri http://www.haproxy.org/health
} -start
client c1 -connect ${h1_fe1_sock} {
txreq -req GET -url /health
rxresp
expect resp.status == 200
} -run
client c2 -connect ${h1_fe1_sock} {
txreq -req GET -url http://www.haproxy.org/health \
-hdr "Host: www.haproxy.org"
rxresp
expect resp.status == 200
} -run
client c3 -connect ${h1_fe1_sock} {
txreq -req GET -url /hEAlth
rxresp
expect resp.status == 503
} -run
client c4 -connect ${h1_fe2_sock} {
txreq -req GET -url http://www.haproxy.org/health \
-hdr "Host: www.haproxy.org"
rxresp
expect resp.status == 200
} -run
client c5 -connect ${h1_fe2_sock} {
txreq -req GET -url /health
rxresp
expect resp.status == 503
} -run