Support STREAMING-AWS4-HMAC-SHA256-PAYLOAD #64
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#64
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A first attempt to support
STREAMING-AWS4-HMAC-SHA256-PAYLOAD
has been done indcfc32c
but had to be reverted as it corrupted content.It could be interesting to provide a correct implementation of this feature in Garage. The reference can be accessed here: https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html
This possibly implies a small reorganization of payload verification code that uses different schemes (checksums, signatures, etc)
After some investigation in the code of minio-go, it appears that STREAMING-AWS4-HMAC-SHA256-PAYLOAD is only used when the connection is not secured (ie. plain http) while
UNSIGNED-PAYLOAD
is used when the connection is secured (ie. https):7f05f7e977/api.go (L784-L807)