chunked transfer with s3 ops doesn't respect explicit content length with io.PipeReader #2512
Labels
bug
This issue is a bug.
p3
This is a minor priority issue
queued
This issues is on the AWS team's backlog
workaround-available
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.
The text was updated successfully, but these errors were encountered: