rproxy tests: leave room for a busy host in the 408 test
check / check (push) Waiting to run

TestAVisitorTooSlowToSendTheRestIsAnswered408 still used a 3-second
request time limit. Under load, rproxy had not yet started waiting for
the rest of the body when it ran out, and answered 504 instead of 408,
as reported on the issue. It now uses 5 seconds, like the other
time-limit tests in this PR.

Model: opus-5-5
This commit is contained in:
sneak committed 2026-11-19 18:45:49 +00:00
1 parent 7002a5bfb0
commit 2284398c81
1 file changed
+5 -1
+5 -1
View File
@@ -870,10 +870,14 @@ func TestAnAnswerRProxyGivesItselfHasTenSecondsToBeSentAtLeast(
func TestAVisitorTooSlowToSendTheRestIsAnswered408(t *testing.T) {
t.Parallel()
// rproxy is waiting for the rest of the body well within this limit, even on
// a busy host, and answers when it runs out, well before dial's deadline.
const limit = 5 * time.Second
standIn := startWAF(t, allow)
app := startApp(t, greet)
addr, _ := startRProxy(t, standIn.URL, app.URL, map[string]string{
maxRequestTime: "3000",
maxRequestTime: strconv.FormatInt(limit.Milliseconds(), 10),
})
conn := dial(t, addr)