From: Willy Tarreau Date: Tue, 22 Sep 2026 22:50:12 +0000 (+0000) Subject: REGTESTS: http-messaging: make the /c5 abort land during the retries X-Git-Tag: v3.5-dev8~6 X-Git-Url: https://git.kaiwu.me/?a=commitdiff_plain;h=506391f874075c03f3095742ed1373104e9d8e86;p=haproxy.git REGTESTS: http-messaging: make the /c5 abort land during the retries The previous attempt at making this case robust, which raised the connect timeout so that the client abort is noticed before the retries are over, was not enough: the client closes immediately after its request, so under load the close is sometimes seen while the request is still being parsed, and the transaction is then logged as "CH--" with a 400 instead of the expected "CC--". The client now waits fifty milliseconds before closing, which leaves haproxy the time to read the request and to start connecting, and the raised connect timeout gives the abort a full second to be noticed. Twenty runs in parallel with the machine loaded pass. --- diff --git a/reg-tests/http-messaging/http_abortonclose.vtc b/reg-tests/http-messaging/http_abortonclose.vtc index c5eb1d37c..21889ad0b 100644 --- a/reg-tests/http-messaging/http_abortonclose.vtc +++ b/reg-tests/http-messaging/http_abortonclose.vtc @@ -226,6 +226,11 @@ syslog S1 -wait # abortonclose on backend only client c5 -connect ${h2_fe1_sock} { txreq -url /c5 + # leave haproxy the time to read the request and to start connecting, + # otherwise the close may be seen while the request is still being + # parsed, which is reported as a client abort during the headers and + # not during the connection retries + delay 0.05 } -run # Wait c5 log entry