-
Notifications
You must be signed in to change notification settings - Fork 89
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
All Rejected after updating AwsSdk.S3 library #240
Comments
I have a same issue :-( |
Hi, thanks for reporting this. Could you please provide a repository link with a minimal example? |
Hey Jakob, this is the minimal example, that works with AwsSdk.S3 nuget 3.7.304.7, but not with 3.7.304.8
|
Thank you very much! However, could you please provide an entire repository complete with project files that contain the dependencies and instructions about how to switch between the versions? You know, I don't usually work with .NET. In fact, I did not for more than a decade, and most of my software development takes place on a Mac where .NET is not quite the most prominent environment. 😉 I am sure I could figure out myself how to set everything up to run your sample, but I am seriously lacking the time to do that. So, I would really need a repository that I can check out, please. If I can run that on my Mac, I can have a look at what goes wrong on our side. (Or ask a colleague who happens to own a PC.) |
I'm seeing this issue as well on bun. If I use the latest npm package I get the issue:
But by downgrading to
@jakobvogel I have a repository I can share with you privately if you like. |
We had to switch to another project - https://github.com/Robothy/local-s3 |
I recently updated AwsSdk.S3 nuget (.NET) from 3.7.304.7 to 3.7.304.8 and s3ninja started to reject all requests done to the a bucket (credentials unchanged, any other code unchanged as well). I am getting following error:
"The computed request signature does not match the one provided. Check login credentials. (Expected: abc, Found: def)"
I was trying to track down the issue and changes in the AwsSdk.S3 nuget but I wasn't able to find any obvious change. Actually the only change seems to be in the construction of the User-Agent header, however I wasn't able to locate any possible effect in the s3ninja source.
The text was updated successfully, but these errors were encountered: