Aurelien DARRAGON 26d97ec148 REGTESTS: fix reg-tests/server/abnsz.vtc ... It was proved in GH #2875 that the regtest was broken, at least for the server-side abnsz, as the connect() was not performed using the proper family, which results in kernel refusing to perform the call, while the reg-test actually succeeds. Indeed, in the test we used vtest client to connect to haproxy, which then routed the request to another haproxy instance listening on an abnsz socket, and this last haproxy was the one to answer the http request. As we only used "rxresp" in vtest client, the test succeeded with empty responses, which was the case due to the server connection failing on the first haproxy process.		2025-02-21 08:22:25 +01:00
..
abnsz.vtc	REGTESTS: fix reg-tests/server/abnsz.vtc	2025-02-21 08:22:25 +01:00
cli_add_check_server.vtc	REGTESTS: use -dW by default on every reg-tests	2024-11-19 16:53:10 +01:00
cli_add_server.vtc	REGTESTS: use -dW by default on every reg-tests	2024-11-19 16:53:10 +01:00
cli_add_ssl_server.vtc	REGTESTS: use -dW by default on every reg-tests	2024-11-19 16:53:10 +01:00
cli_add_track_server.vtc	REGTESTS: use -dW by default on every reg-tests	2024-11-19 16:53:10 +01:00
cli_delete_dynamic_server.vtc	REGTESTS: use -dW by default on every reg-tests	2024-11-19 16:53:10 +01:00
cli_delete_server.vtc	REGTESTS: use -dW by default on every reg-tests	2024-11-19 16:53:10 +01:00
cli_set_fqdn.vtc	REGTESTS: use -dW by default on every reg-tests	2024-11-19 16:53:10 +01:00
cli_set_ssl.vtc	REGTESTS: use -dW by default on every reg-tests	2024-11-19 16:53:10 +01:00
common.pem
get_srv_stats.lua