Chris LuandGitHub f582c8451b s3: report a peer that went away as ClientDisconnected, not IncompleteBody (#10511) ...

* s3: report a peer that went away as ClientDisconnected, not IncompleteBody

A streaming PUT whose body ends early is always reported as IncompleteBody
(400). That collapses two cases with opposite causes: the peer vanished
mid-upload, and the peer sent fewer bytes than it promised while still
connected. The first points at the network path, the second at the client,
and once merged they cannot be told apart from the logs.

Split out ClientDisconnected (499) and select it when the request context
shows the peer is gone. The upload itself keeps running on a background
context so chunks still finish, which means cancellation races the read
error; a missed signal degrades to IncompleteBody exactly as before.

* s3: note what request-context cancellation is taken to mean

2026-07-31 19:43:45 -07:00

..

audit_fluent_test.go

fix(s3/audit): populate requester for GET/HEAD/IAM operations (#9581)

2026-05-20 10:13:33 -07:00

audit_fluent.go

Add codespell support with configuration and typo fixes (#10393)

2026-07-22 14:38:06 -07:00

error_handler_test.go

s3/iam: reuse one request id per request (#8538)

2026-03-06 15:22:39 -08:00

error_handler.go

fix(s3): return 403 on POST policy violation instead of 307 redirect (#9122)

2026-04-17 14:54:58 -07:00

s3-error.go

Fix #7305: Return 400 BadDigest instead of 500 InternalError for MD5 mismatch (#7306)

2025-10-08 14:24:10 -07:00

s3api_errors.go

s3: report a peer that went away as ClientDisconnected, not IncompleteBody (#10511)

2026-07-31 19:43:45 -07:00