You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🐛 fix(oci): answer a failed request body as a client error
An upload whose body failed answered 502 with "upstream transfer failed". No
upstream serves a request body: the bytes were coming from the client and peryx
is the server. The stall bound #2182 added made it reachable with the client
still connected, so a client that paused for thirty seconds was told something
upstream of peryx had gone wrong.
502 also carries a meaning to intermediaries, a bad response from an upstream
server, which invites a retry against a different backend for a condition no
backend change reaches.
A stall now answers 408, which says the server gave up waiting for a message
that never arrived, and names the offset a resumable session stands at so the
client knows where to continue. Anything else the body ends with answers 400,
since repeating it unchanged fails the same way. Both come from the shared
classification rather than from each call site reading an opaque error.
Four tests asserted the old status. Their intent survives unchanged: the stall
pair asserted a cut chunk must not read as accepted, which 408 satisfies, and
the monolithic case was named for the gateway status it happened to produce
rather than for a gateway being involved.
0 commit comments