Some services require this header to be updated as part of the new signature. <p d

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Thanks for the context <a class="user-mention notranslate" data-hovercard-type="user"

Add support for X-Amz-Content-Sha256 about awssigner HOT 4 OPEN

netspi commented on September 22, 2024

Add support for X-Amz-Content-Sha256

from awssigner.

Comments (4)

rbeede commented on September 22, 2024

https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html

from awssigner.

jakekarnes42 commented on September 22, 2024

Hi @rbeede, there are a couple of things that you could provide that would help me jump right into this. Any chance you could provide the following:

The API that you're calling.
An example request (just copied out of Repeater or similar) that's not being signed correctly.

I see from your link that we're talking about S3 here, but those additional details would speed up my troubleshooting. Thanks!

from awssigner.

rbeede commented on September 22, 2024

I'm actually testing an API that is not S3 but has X-Amz-Content-Sha256 in it.

Is there a way to force that header to be updated anytime it is seen and not just if the service is S3?

from awssigner.

jakekarnes42 commented on September 22, 2024

Thanks for the context @rbeede. I'll need to dig into this a bit more on my side. If you're needing an immediate workaround, it looks like an alternative signing extension recently added support for this scenario. That being said, I'd like to find a way to incorporate this functionality.

from awssigner.

Recommend Projects