You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @NathanielRN, thanks for raising this!
In other services we tend to use the @amzn_request_id-annotation to automatically add a RequestId to every response, but that doesn't happen in S3. Marking it as an enhancement!
This was using
botocore
at1.19.12
andmoto
at1.3.16
What Actually Happened
When I use
moto
to mocks3
, I expected to seeRequestId
in theResponseMetadata
. This was my setup:However, when I printed out the response, I only saw the following:
What I Expected to Happen
This is compared to my sample application where I do this:
And I get a response like this from S3:
Please let me know if I'm missing something here.
The text was updated successfully, but these errors were encountered: