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/balance/balance-uri-path-only.vtc

98 lines
1.9 KiB
Plaintext
Raw Permalink Normal View History

REGTESTS: add a few load balancing tests This adds "balance-rr" to test round robin, "balance-uri" to test the default balance-uri method, and "balance-uri-path-only" which mixes H1 and H2 through "balance uri path-only" and verifies that they reach the same server. Note that for the latter, "proto h2" explicitly had to be placed on the listening socket otherwise it would timeout. This may indicate an issue in the H1->H2 upgrade depending how the H2 preface is sent maybe.
2020-09-23 07:02:13 +00:00
vtest "Test for balance URI"
feature ignore_unknown_macro
#REQUIRE_VERSION=2.3
server s1 {
rxreq
txresp -hdr "Server: s1" -body "s1"
} -repeat 5 -start
server s2 {
rxreq
txresp -hdr "Server: s2" -body "s2"
} -repeat 5 -start
server s3 {
rxreq
txresp -hdr "Server: s3" -body "s3"
} -repeat 5 -start
server s4 {
rxreq
txresp -hdr "Server: s4" -body "s4"
} -repeat 5 -start
haproxy h1 -arg "-L A" -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 server "${HAPROXY_TEST_TIMEOUT-5s}"
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
REGTESTS: add a few load balancing tests This adds "balance-rr" to test round robin, "balance-uri" to test the default balance-uri method, and "balance-uri-path-only" which mixes H1 and H2 through "balance uri path-only" and verifies that they reach the same server. Note that for the latter, "proto h2" explicitly had to be placed on the listening socket otherwise it would timeout. This may indicate an issue in the H1->H2 upgrade depending how the H2 preface is sent maybe.
2020-09-23 07:02:13 +00:00
listen px
bind "fd@${px}"
bind "fd@${pxh2}" proto h2
balance uri path-only
server srv1 ${s1_addr}:${s1_port}
server srv2 ${s2_addr}:${s2_port}
server srv3 ${s3_addr}:${s3_port}
server srv4 ${s4_addr}:${s4_port}
} -start
client c1 -connect ${h1_px_sock} {
REGTEST: fix host part in balance-uri-path-only.vtc We used to set it to ${h1_px_addr} but it randomly fails on certain hosts (FreeBSD and OSX) where the address is surprisingly set to "::1" while the Host field contains 127.0.0.1 (hence two different address families). While this is likely a minor issue in vtest, we don't need to depend on this and can easily hard-code 127.0.0.1 which is already used in other tests.
2020-09-29 07:58:23 +00:00
txreq -url "http://127.0.0.1/url1"
REGTESTS: add a few load balancing tests This adds "balance-rr" to test round robin, "balance-uri" to test the default balance-uri method, and "balance-uri-path-only" which mixes H1 and H2 through "balance uri path-only" and verifies that they reach the same server. Note that for the latter, "proto h2" explicitly had to be placed on the listening socket otherwise it would timeout. This may indicate an issue in the H1->H2 upgrade depending how the H2 preface is sent maybe.
2020-09-23 07:02:13 +00:00
rxresp
expect resp.status == 200
expect resp.http.Server ~ s2
} -run
client c2 -connect ${h1_px_sock} {
txreq -url "/url1?ignore=this-arg"
rxresp
expect resp.status == 200
expect resp.http.Server ~ s2
} -run
client c3 -connect ${h1_px_sock} {
REGTEST: fix host part in balance-uri-path-only.vtc We used to set it to ${h1_px_addr} but it randomly fails on certain hosts (FreeBSD and OSX) where the address is surprisingly set to "::1" while the Host field contains 127.0.0.1 (hence two different address families). While this is likely a minor issue in vtest, we don't need to depend on this and can easily hard-code 127.0.0.1 which is already used in other tests.
2020-09-29 07:58:23 +00:00
txreq -url "http://127.0.0.1/url2"
REGTESTS: add a few load balancing tests This adds "balance-rr" to test round robin, "balance-uri" to test the default balance-uri method, and "balance-uri-path-only" which mixes H1 and H2 through "balance uri path-only" and verifies that they reach the same server. Note that for the latter, "proto h2" explicitly had to be placed on the listening socket otherwise it would timeout. This may indicate an issue in the H1->H2 upgrade depending how the H2 preface is sent maybe.
2020-09-23 07:02:13 +00:00
rxresp
expect resp.status == 200
expect resp.http.Server ~ s3
} -run
client c4 -connect ${h1_px_sock} {
txreq -url "/url3"
rxresp
expect resp.status == 200
expect resp.http.Server ~ s4
} -run
client c5 -connect ${h1_px_sock} {
txreq -url "/url4"
rxresp
expect resp.status == 200
expect resp.http.Server ~ s1
} -run
client c6h2 -connect ${h1_pxh2_sock} {
txpri
stream 0 {
txsettings
rxsettings
txsettings -ack
rxsettings
expect settings.ack == true
} -run
stream 1 {
txreq \
-req "GET" \
-scheme "https" \
-url "/url1"
rxhdrs
expect resp.status == 200
rxdata -all
expect resp.body == "s2"
} -run
} -run