haproxy/reg-tests/stick-table/src_conn_rate.vtc
Willy Tarreau f673923629 REGTESTS: extend the default I/O timeouts and make them overridable
With the CI occasionally slowing down, we're starting to see again some
spurious failures despite the long 1-second timeouts. This reports false
positives that are disturbing and doesn't provide as much value as this
could. However at this delay it already becomes a pain for developers
to wait for the tests to complete.

This commit adds support for the new environment variable
HAPROXY_TEST_TIMEOUT that will allow anyone to modify the connect,
client and server timeouts. It was set to 5 seconds by default, which
should be plenty for quite some time in the CI. All relevant values
that were 200ms or above were replaced by this one. A few larger
values were left as they are special. One test for the set-timeout
action that used to rely on a fixed 1-sec value was extended to a
fixed 5-sec, as the timeout is normally not reached, but it needs
to be known to compare the old and new values.
2021-11-18 17:57:11 +01:00

44 lines
937 B
Plaintext

varnishtest "stick table: src_conn_rate"
feature ignore_unknown_macro
haproxy h0 -conf {
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
listen li
bind "fd@${fe1}"
http-request track-sc0 src table conn_rate_table
http-request deny if { src_conn_rate(conn_rate_table) gt 3 }
http-request return status 200
backend conn_rate_table
stick-table type ip size 1m expire 1m store conn_rate(1m)
} -start
client c0 -connect ${h0_fe1_addr}:${h0_fe1_port} {
txreq
rxresp
expect resp.status == 200
} -run
client c1 -connect ${h0_fe1_addr}:${h0_fe1_port} {
txreq
rxresp
expect resp.status == 200
} -run
client c2 -connect ${h0_fe1_addr}:${h0_fe1_port} {
txreq
rxresp
expect resp.status == 200
} -run
client c3 -connect ${h0_fe1_addr}:${h0_fe1_port} {
txreq
rxresp
expect resp.status == 403
} -run