sneak
b36a2a6df2
check / check (push) Waiting to run
A new test fails on the current code: when the response time limit runs out before rproxy can write the app's short body, and the visitor has stopped a little short of its announced length, the connection stays open until the request time limit instead of closing. The test that failed under load used a 300 ms response time limit, which a busy host can use up between the app's headers and its body. It and the test that answers a visitor that stops sending now use limits far longer than the test's 10-second read deadline. Model: opus-5-5