haproxy/reg-tests/connection
Amaury Denoyelle 36d936dd15 REGTESTS: write a full reverse regtest
This test instantiates two haproxy instances :
* first one uses a reverse server with two bind pub and priv
* second one uses a reverse bind to initiate connection to priv endpoint

On startup, only first haproxy instance is up. A client send a request
to pub endpoint and should receive a HTTP 503 as no connection are
available on the reverse server.

Second haproxy instance is started. A delay of 3 seconds is inserted to
wait for the connection between the two LBs. Then a client retry the
request and this time should receive a HTTP 200 reusing the bootstrapped
connection.
2023-08-24 17:03:08 +02:00
..
ca-auth.crt REGTESTS: provide a reverse-server test with name argument 2023-08-24 17:02:37 +02:00
cli_src_dst.vtc
client1.pem REGTESTS: provide a reverse-server test with name argument 2023-08-24 17:02:37 +02:00
common.pem
dispatch.vtc
http_reuse_aggressive.vtc
http_reuse_always.vtc
http_reuse_be_transparent.vtc
http_reuse_conn_hash.vtc
http_reuse_dispatch.vtc
http_reuse_never.vtc
http_reuse_safe.vtc
proxy_protocol_random_fail.vtc
proxy_protocol_send_unique_id_alpn.vtc
proxy_protocol_send_unique_id.vtc
proxy_protocol_tlv_validation.vtc
reverse_connect_full.vtc REGTESTS: write a full reverse regtest 2023-08-24 17:03:08 +02:00
reverse_server_name.vtc REGTESTS: provide a reverse-server test with name argument 2023-08-24 17:02:37 +02:00
reverse_server.vtc REGTESTS: provide a reverse-server test 2023-08-24 15:02:56 +02:00
tcp_to_http_upgrade.vtc