haproxy/reg-tests/connection/dispatch.vtc

varnishtest "Validate proper operation of the 'dispatch' mode"
feature ignore_unknown_macro

server s1 {
    rxreq
    txresp
} -start

server s2 {
    rxreq
    txresp
} -start

haproxy h1 -conf {
defaults
    log global
    timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
    timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
    timeout server "${HAPROXY_TEST_TIMEOUT-5s}"

listen fe_tcp
    bind "fd@${fe_tcp}"
    mode tcp
    dispatch ${s1_addr}:${s1_port}

listen fe_http
    bind "fd@${fe_http}"
    mode http
    dispatch ${s2_addr}:${s2_port}
} -start

client c1 -connect ${h1_fe_tcp_sock} {
    txreq -url "/"
    rxresp
    expect resp.status == 200
} -run

client c2 -connect ${h1_fe_http_sock} {
    txreq -url "/"
    rxresp
    expect resp.status == 200
} -run
REGTEST: add a test for connections to a "dispatch" address The test includes both TCP and HTTP modes. 2018-11-23 07:36:06 +00:00			`varnishtest "Validate proper operation of the 'dispatch' mode"`
			`feature ignore_unknown_macro`

			`server s1 {`
			`rxreq`
			`txresp`
			`} -start`

			`server s2 {`
			`rxreq`
			`txresp`
			`} -start`

			`haproxy h1 -conf {`
			`defaults`
			`log global`
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 a test for connections to a "dispatch" address The test includes both TCP and HTTP modes. 2018-11-23 07:36:06 +00:00
			`listen fe_tcp`
			`bind "fd@${fe_tcp}"`
			`mode tcp`
			`dispatch ${s1_addr}:${s1_port}`

			`listen fe_http`
			`bind "fd@${fe_http}"`
			`mode http`
			`dispatch ${s2_addr}:${s2_port}`
			`} -start`

			`client c1 -connect ${h1_fe_tcp_sock} {`
			`txreq -url "/"`
			`rxresp`
			`expect resp.status == 200`
			`} -run`

			`client c2 -connect ${h1_fe_http_sock} {`
			`txreq -url "/"`
			`rxresp`
			`expect resp.status == 200`
			`} -run`