-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add support for aws-chunked #913
Comments
smallhive
added a commit
that referenced
this issue
Nov 30, 2023
closes #913. Signed-off-by: Evgenii Baidakov <[email protected]>
smallhive
added a commit
that referenced
this issue
Nov 30, 2023
closes #913. Signed-off-by: Evgenii Baidakov <[email protected]>
smallhive
added a commit
that referenced
this issue
Nov 30, 2023
closes #913. Signed-off-by: Evgenii Baidakov <[email protected]>
smallhive
added a commit
that referenced
this issue
Dec 1, 2023
closes #913. Signed-off-by: Evgenii Baidakov <[email protected]>
smallhive
added a commit
that referenced
this issue
Dec 1, 2023
closes #913. Signed-off-by: Evgenii Baidakov <[email protected]>
smallhive
added a commit
that referenced
this issue
Dec 1, 2023
closes #913. Signed-off-by: Evgenii Baidakov <[email protected]>
roman-khimov
added a commit
that referenced
this issue
Dec 1, 2023
This was referenced Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I'm always frustrated when I find unsupported S3 features that are used in the wild. Seems like https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html is one of them. In absence of proper
aws-chunked
handling we treat its metadata as a part of object payload and that's not what client software expects.Describe the solution you'd like
Add support for
aws-chunked
.Describe alternatives you've considered
If some clients use it, you don't have a lot of options.
The text was updated successfully, but these errors were encountered: