chunked transfer with s3 ops doesn't respect explicit content length with io.PipeReader

[lucix-aws]

See #2511.

We have a special case for io.PipeReader that sets request ContentLength to -1, which is at odds with certain payload signing schemes in S3.

Unclear whether we'll be able to fix this long-term given that it may be behaviorally sensitive.

[charlesyu108]

Hi I see this has been tagged with workaround-available, would you mind sharing what that is?

[remore]

Same here - would really appreciate the workaround if available 🙇

[Ernestet]

Hi @lucix-aws could you share the work around, please?