Chris Lu 155140bed8 s3: return IncompleteBody instead of 500 for truncated PUT bodies (#10186) ...

* s3: add IncompleteBody error code

* operation: tag a truncated source read as ErrTruncatedBody

The chunked uploader wraps both source-read failures and volume-upload failures,
and a mid-write volume server drop also carries io.ErrUnexpectedEOF. Tag only the
source read so callers can tell a truncated input apart from a server-side fault.

* s3: return IncompleteBody for a truncated PUT body

A client abort or reverse-proxy timeout truncates the request body mid-upload.
putToFiler mapped every streaming-upload failure to InternalError (500), which a
reverse proxy relays as a 502. Classify a source-read truncation as IncompleteBody
(400) so the response matches AWS and passes through. All S3 write paths share
putToFiler, so they all benefit.

2026-07-01 18:45:17 -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

fix(s3/audit): emit audit log for successful GET/HEAD (#9467)

2026-05-13 09:24:59 -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: return IncompleteBody instead of 500 for truncated PUT bodies (#10186)

2026-07-01 18:45:17 -07:00