Replies: 5 comments
-
What are you trying to sign the contents of a pre-signed upload URL for? Having a signed body for a pre-signed upload URL would mean that the consumer of the pre-signed URL would have to upload contents with the same signature - you'd have to know what they're going to upload when generating the URL. Using the |
Beta Was this translation helpful? Give feedback.
-
In this issue, there is a discussion (#1392 (comment)) about providing |
Beta Was this translation helpful? Give feedback.
-
@kstich Have you planned to explore this problem? Do you need any extra information and details? |
Beta Was this translation helpful? Give feedback.
-
I'm facing this issue currently |
Beta Was this translation helpful? Give feedback.
-
I hope that through signature in advance the way to let the client to complete shard upload (https://docs.amazonaws.cn/general/latest/gr/sigv4-create-canonical-request.html), but the return to upload address, UploadId/partNumber/unsigned-payload/unsigned-payload Here is my request: |
Beta Was this translation helpful? Give feedback.
-
According to this issue #1392 I've found some problem with checksum providing
ContentSha256
param in command for creating pre-signed URL.I think the problem in
getPresignedPayload()
method (https://github.com/jeskew/aws-sdk-php/blob/4e29e28494f8dc69c2ae1b34a0a658e8ed9537fe/src/Signature/S3SignatureV4.php#L53) which always returnsUNSIGNED-PAYLOAD
that doesn't match real body content of the uploading file.Beta Was this translation helpful? Give feedback.
All reactions