Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for X-Amz-Content-Sha256 #37

Open
rbeede opened this issue Oct 13, 2022 · 4 comments
Open

Add support for X-Amz-Content-Sha256 #37

rbeede opened this issue Oct 13, 2022 · 4 comments

Comments

@rbeede
Copy link

rbeede commented Oct 13, 2022

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

X-Amz-Content-Sha256

@rbeede
Copy link
Author

rbeede commented Oct 13, 2022

@jakekarnes42
Copy link
Collaborator

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:

  1. The API that you're calling.
  2. 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!

@rbeede
Copy link
Author

rbeede commented Oct 13, 2022

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?

@jakekarnes42
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants