Willy Tarreau 4137889911 REGTESTS: mark proxy_protocol_random_fail as broken ... As indicated in issue #907 it very frequently fails on FreeBSD, and looking at it, it's broken in multiple ways. It relies on log ordering between two layers, the first one being allowed to support h2. Given that on FreeBSD it usually ends up in timeouts, it's very likely that for some reason one frontend logs before the other one or that curl uses h2 instead of h1 there, and that the log instance waits forever for its lines. Usually it works fine when run locally though, so let's not remove it and mark it as broken instead so that it can still be used when relevant.		2020-11-21 15:33:03 +01:00
..
common.pem	REGTEST/MINOR: Add a reg testing file for b406b87 commit.	2018-08-24 16:53:27 +02:00
dispatch.vtc	REGTEST: rename the reg test files.	2019-04-23 15:37:03 +02:00
proxy_protocol_random_fail.vtc	REGTESTS: mark proxy_protocol_random_fail as broken	2020-11-21 15:33:03 +01:00
proxy_protocol_send_unique_id_alpn.vtc	REGTEST: Add connection/proxy_protocol_send_unique_id_alpn	2020-05-27 13:29:56 +02:00
proxy_protocol_send_unique_id.vtc	MEDIUM: proxy_protocol: Support sending unique IDs using PPv2	2020-03-13 17:26:43 +01:00
proxy_protocol_tlv_validation.vtc	REGTEST: make the PROXY TLV validation depend on version 2.2	2020-03-31 16:37:58 +02:00