sneak
e3c5b4ecf8
check / check (push) Waiting to run
The app now sends its late parts only once rproxy has ended the request to it, not after a sleep timed against the limit. With the body in one part it stalls after its headers; with two parts, after the first part, which reaches the visitor. Both cases fail on the current code: nothing cuts the answer off, and the connection stays open. The 2-second limit lets rproxy pass on a part sent at once, even on a busy host. A new test, which passes on the current code, has every flush fail with no refusal, so that only the failed-flush check in finish ends the reading of the visitor's body. Model: opus-5-5