Incorrect processing of signed payload in pre-signed URL

[MNV]

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 returns UNSIGNED-PAYLOAD that doesn't match real body content of the uploading file.

[kstich]

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 UNSIGNED-PAYLOAD allows the consumer to upload whatever contents they wish to the file. You can read more about pre-signed upload URLs here.

[MNV]

In this issue, there is a discussion (#1392 (comment)) about providing ContentSha256 hash generating pre-signed URL to allow the server to know what they are going to upload.
I would like to pass the checksum to the server to generate the URL for uploading and check that client tries to upload the same file for which pre-signed URL was given (#1392 (comment)).

[MNV]

@kstich Have you planned to explore this problem? Do you need any extra information and details?

[abiodunjames]

I'm facing this issue currently