sneak
eba697af48
check / check (push) Waiting to run
When SWRP_MAX_RESPONSE_TIME_MS ran out before the last of a short answer was written, the flush failed. If the visitor had stopped short of its announced body, Go's server then read the rest until SWRP_MAX_REQUEST_TIME_MS ran out, keeping the connection open with the answer cut off. finish now flushes once more, and if that fails at its deadline, it ends the reading of the body at once. ReverseProxy ignores the failed flush when the app's answer came in one read, and panics when it was still waiting for more; finish runs after both. Go's server never reuses a connection after a failed write, so it closes it. Model: opus-5-5