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
SignatureDoesNotMatch #1515
Comments
@sanderhahn thanks for reporting! will get back |
@sanderhahn minio/minio-go#245 fixes this issue. Once it is merged it will be included in the 'mc' source. |
Tested locally, works like a charm :) |
signature-presign: new minio-go vendorized fixes #1515
A new release has been made fixing this issue along with others. Thanks for your report @sanderhahn |
Perfect! Was getting the same error when creating subdirectories and this solved. it. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Wow very cool project :-)
Trying the
mc share download
function from mc with bothminio
and s3-eu-west-1.amazonaws.com. The mc tool properly gives back a url that i can visit, however the url generates a signature error on both aws and using the minio server locally. Switching back to S3v2 for aws makes the signed urls work properly, but that doesn't work when using the minio server. Tried both buildingmc
from source using go get and the downloadable binary (on darwin-amd64). Is there something wrong with the S3v4 signing inmc
or am i doing something wrong?The text was updated successfully, but these errors were encountered: