RepoMirrors
/
haproxy
mirror of http://git.haproxy.org/git/haproxy.git/
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
haproxy/reg-tests/stream/unique-id.vtc

50 lines
1.1 KiB
Plaintext
Raw Normal View History

REGTEST: Add unique-id reg-test This reg-test verifies the following behavior: 1. That unique IDs are stable (i.e. the bug fixed in 530408f976e5fe2f2f2b4b733b39da36770b566f) 2. That unique IDs can use values from the HTTP request (see https://www.mail-archive.com/haproxy@formilux.org/msg36436.html)
2020-02-28 14:13:32 +00:00
varnishtest "unique-id test"
REGTEST: make the unique-id test depend on version 2.0 Regtest unique-id.vtc was added by commit 5fcec84c58 ("REGTEST: Add unique-id reg-test") but it relies on the "uuid" sample fetch which is only available in version 2.0 and above. Let's reflect that in the REQUIRE_VERSION tag.
2020-04-01 14:08:43 +00:00
#REQUIRE_VERSION=2.0
REGTEST: Add unique-id reg-test This reg-test verifies the following behavior: 1. That unique IDs are stable (i.e. the bug fixed in 530408f976e5fe2f2f2b4b733b39da36770b566f) 2. That unique IDs can use values from the HTTP request (see https://www.mail-archive.com/haproxy@formilux.org/msg36436.html)
2020-02-28 14:13:32 +00:00
feature ignore_unknown_macro
server s1 {
rxreq
txresp
} -repeat 2 -start
haproxy h1 -conf {
defaults
mode http
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 16:46:22 +00:00
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
REGTEST: Add unique-id reg-test This reg-test verifies the following behavior: 1. That unique IDs are stable (i.e. the bug fixed in 530408f976e5fe2f2f2b4b733b39da36770b566f) 2. That unique IDs can use values from the HTTP request (see https://www.mail-archive.com/haproxy@formilux.org/msg36436.html)
2020-02-28 14:13:32 +00:00
frontend stable
bind "fd@${fe1}"
unique-id-format TEST-%[uuid]
http-response set-header A %[unique-id]
http-response set-header B %[unique-id]
default_backend be
frontend request_data
bind "fd@${fe2}"
unique-id-format TEST-%[req.hdr(in)]
http-response set-header out %[unique-id]
default_backend be
backend be
server srv1 ${s1_addr}:${s1_port}
} -start
client c1 -connect ${h1_fe1_sock} {
txreq -url "/"
rxresp
expect resp.status == 200
expect resp.http.a == resp.http.b
} -run
client c2 -connect ${h1_fe2_sock} {
txreq -url "/" \
-hdr "in: 12345678"
rxresp
expect resp.status == 200
expect resp.http.out == "TEST-12345678"
} -run