-
Notifications
You must be signed in to change notification settings - Fork 1
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
SigV4-S3 Support #5
Comments
Found the problem, in canonical request it was trying to compute body_digest where it should only have stated "UNSIGNED-PAYLOAD" in order to match what the client was sending (last line of canonical request). |
That is SigV4-S3 instead of plain SigV4; I can’t recall if I ever implemented that (I suspect not).
S3 does request signing differently (partially due to legacy design decisions around URLs, partially due to the practicality of holding large request bodies in memory).
You have me curious: what are you using this for? I don’t find many other people doing server side SigV4. Always interesting to hear from someone else in this space. 😀
On Jun 10, 2022, at 8:15 AM, infosisio ***@***.***> wrote:
Found the problem, in canonical request it was trying to compute body_digest where it should only have stated "UNSIGNED-PAYLOAD" in order to match what the client was sending (last line of canonical request).
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAJ3HVGGHJUIX57A6HWD22TVONLZRANCNFSM5YN4MWBA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
@dacut Thank you, that makes sense. Switching to awssig.AWSSigV4S3Verifier from awssig.AWSSigV4Verifier works without errors somehow but I just noticed that it lacks the functionality that collects and computes everything. It's a personal project that I started recently, nothing serious yet. |
Ah, maybe I had gotten further along that I had remembered. Yes, this is also a personal project that I haven't touched in awhile, so I can't remember exactly where I was with the S3 version. |
@dacut It seems that you have implemented AWSSigV4S3Verifier to a working degree at least, it inherits from AWSSigV4Verifier the rest of the stuff. |
Hello, I don't know why but https does not seem to work. The request headers seem to be the same so I am not sure what is stopping it from working. The signatures do not match. Do you have any idea? Thank you.
The text was updated successfully, but these errors were encountered: