-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
wasabisys throws a 403 with latest [workaround included] #1184
Comments
Side note: I'd be willing to provide a key and ARN to a wasabi s3 bucket for testing if necessary. |
Looking at the diffs between
I did find this from a java client: I found this on their API website: |
could you give a try and disable this option https://async-aws.com/clients/s3.html#chunked-body ? |
Hmm.. that doesn't seem to do it either .. I did also find this sad-fact with wasabi: Apparently if it's a AWS4 version signature, it ALWAYS has to go to us-east-1? [EDIT]I updated my ARN / endpoints / etc to us-east-1 and it still fails. |
a blank s3bucket.ini (parsed from script) fill in your details - if you need a wasabi ARN / key secret for testing I can give you one offline.
Here is my script I am using (commandline)
|
Summary:
For wasabisys - Apparently there are breaking changes as far back as 1.1.0 .. so only 1.0.0 works.
I'm still digging into this issue, maybe someone has further light and knowledge to assist on helping this over the line?
Problem:
Resolution:
So those of you who experience technical difficulties uploading to wasabi here is a non-ideal workaround:
composer --ignore-platform-reqs require async-aws/s3 -v 1.0.0
The text was updated successfully, but these errors were encountered: