sneak
387744ab50
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 and ReverseProxy ignored it. 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. Go does that read even after an aborting panic. forward now checks for a failed flush once ReverseProxy returns. It then records a 504 refusal, ends the reading of the body at once, and panics so that Go's server closes the connection, as SPEC.md says a cut-off answer does. Model: opus-5-5