We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
set header as this: headers: { 'x-amz-acl': 'public-read', },
upload failed with 403 error
upload can success.
upload failed with 403 code
The text was updated successfully, but these errors were encountered:
I also had this problem, and I think it was because
This latest signature version is supported in all regions and any new regions after January 30, 2014 will support only Signature Version 4.
That includes eu-central-1 and others https://docs.aws.amazon.com/general/latest/gr/signature-version-2.html
But knox does not support it. Automattic/knox#254
I replaced it with the official aws-sdk here: keystonejs/keystone-storage-adapter-s3#15.
Also, switching to a different region
Sorry, something went wrong.
This issue was resolved in the keystone-storage-adapter-s3 v2.0.0 release, which replaces the unmaintained Knox library with the official AWS JavaScript SDK.
keystone-storage-adapter-s3
No branches or pull requests
Steps to reproduce the behavior
set header as this:
headers: {
'x-amz-acl': 'public-read',
},
upload failed with 403 error
Expected behavior
upload can success.
Actual behavior
upload failed with 403 code
The text was updated successfully, but these errors were encountered: