haproxy/reg-tests/sample_fetches
Christopher Faulet 82c2911248 REGTESTS: Make the script testing conditional set-var compatible with Vtest2
VTest2 will replaced VTest in few months. There is not so much change
expected. One of them is that a User-Agent header is added by default in all
requests, except if an custom one is already set or if "-nouseragent" option
is used. To still be compatible with VTest, it is not possible to use the
option to avoid the header addition. So, a custom user-agent is added in the
last test of "sample_fetches/cond_set_var.vtc" to be sure it will pass with
Vtest and Vtest2. It is mandatory because the request length is tested.
2025-05-26 19:00:00 +02:00
..
acl.vtc REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
cond_set_var.vtc REGTESTS: Make the script testing conditional set-var compatible with Vtest2 2025-05-26 19:00:00 +02:00
cook.vtc REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
hashes.vtc REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
so_name.vtc REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
srv_name.vtc REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
tcpinfo_rtt.vtc REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
tlvs.vtc REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
ubase64.vtc REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00
vars.vtc REGTESTS: use -dW by default on every reg-tests 2024-11-19 16:53:10 +01:00