You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On certain APIs, it appears the body isn't used for signing in the canonical request (e.g. when the body is part of a multipart upload, this API is one example where this happens)
In the example above, there is an X-Amz-Content-Sha256 header that provides the value UNSIGNED-PAYLOAD that's used in place of the actual body SHA256 in the canonical request when calculating the signature.
Is it possible to add an option to use the value of the X-Amz-Content-Sha256 header instead of the calculated payload SHA256 when signing?
The text was updated successfully, but these errors were encountered:
On certain APIs, it appears the body isn't used for signing in the canonical request (e.g. when the body is part of a multipart upload, this API is one example where this happens)
In the example above, there is an X-Amz-Content-Sha256 header that provides the value UNSIGNED-PAYLOAD that's used in place of the actual body SHA256 in the canonical request when calculating the signature.
Is it possible to add an option to use the value of the X-Amz-Content-Sha256 header instead of the calculated payload SHA256 when signing?
The text was updated successfully, but these errors were encountered: