Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
lucix-aws opened this issue Feb 21, 2024 · 0 comments
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

Comments

@lucix-aws
Copy link
Contributor

lucix-aws commented Feb 21, 2024

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.

@lucix-aws lucix-aws added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 21, 2024
@lucix-aws lucix-aws self-assigned this Feb 21, 2024
@lucix-aws lucix-aws added investigating This issue is being investigated and/or work is in progress to resolve the issue. p2 This is a standard priority issue queued This issues is on the AWS team's backlog and removed needs-triage This issue or PR still needs to be triaged. queued This issues is on the AWS team's backlog labels Feb 21, 2024
@lucix-aws lucix-aws added queued This issues is on the AWS team's backlog workaround-available p3 This is a minor priority issue and removed investigating This issue is being investigated and/or work is in progress to resolve the issue. p2 This is a standard priority issue labels Mar 5, 2024
@lucix-aws lucix-aws removed their assignment Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant