SignatureDoesNotMatch when sending several S3 commands #6620
Labels
bug
This issue is a bug.
p2
This is a standard priority issue
potential-regression
Marking this issue as a potential regression to be checked by team member
response-requested
Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.
Checkboxes for prior research
Describe the bug
We noticed our tests started to fail with this dependabot upgrade: taskcluster/taskcluster#7365 (comment) (please note that this PR contains multiple packages, it was tested separately and confirmed with just
@aws-sdk/[email protected]
to be broken for us)Tests were failing with
SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.
Upon further investigation it was determined that breaking change was introduced around v3.645.0...v3.649.0 (with 3.645.0 being the last version working, and 3.649.0 first one being broken)
After adding debug middleware I've discovered that request objects might be sharing some properties from the previous request, namely
path
. I suspect this might be a reason, but I'm not too sure.Regression Issue
SDK version number
@aws-sdk/[email protected]
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v22.11.0, v20.16.0
Reproduction Steps
Code:
Running this sequence on 3.645.0 works and produces different output.
Here is how the output of the 3.649.0 looks like:
Second one contains
path
which belongs to the previous command that was sent.With
3.645.0
this request looked like:Observed Behavior
List command fails:
Expected Behavior
ListCommand is being sent with the correct signature
Possible Solution
No response
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: