tentacle: rgw/s3: Always include x-amz-content-sha256 header in AWS v4 signatures#66358
tentacle: rgw/s3: Always include x-amz-content-sha256 header in AWS v4 signatures#66358mheler wants to merge 2 commits intoceph:tentaclefrom
Conversation
|
jenkins test api |
|
thanks @mheler - for backports, please cherry-pick with -x so the commit message contains "(cherry picked from commit xyz)" (see https://github.com/ceph/ceph/blob/main/SubmittingPatches-backports.rst#cherry-picking-rules) |
…es for S3 compatibility Signed-off-by: Matthew N. Heler <matthew.heler@hotmail.com> (cherry picked from commit 4429c7b)
183672f to
619c14d
Compare
@cbodley thanks that should be fixed now! |
|
Removing needs-qa until we have notifiaction/multisite fixes backported to tentacle. |
|
@adamemerson this backport is needed to fix cloud-transition for non-AWS S3 providers. |
|
Can one of the admins verify this patch? |
|
@mheler this change in |
…n empty payload hash computed for UNSIGNED-PAYLOAD. use that hash for the header 'x-amz-content-sha256' in AWSSignerV4::prepare() Signed-off-by: Shilpa Jagannath <smanjara@redhat.com> (cherry picked from commit 5d35671)
Done. |
thank you! |
|
@smanjara are we good to merge this? or do we need to do further qa testing? |
backport tracker: https://tracker.ceph.com/issues/73496
backport of #65723
parent tracker: https://tracker.ceph.com/issues/73315