Skip to content
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 error with non-ASCII metadata #1300

Open
aileo opened this issue May 31, 2024 · 2 comments
Open

SignatureDoesNotMatch error with non-ASCII metadata #1300

aileo opened this issue May 31, 2024 · 2 comments

Comments

@aileo
Copy link

aileo commented May 31, 2024

Hello,

I am not sure if this is a bug or not, if it is related to the js client or minio...

I got 'S3Error: The request signature we calculated does not match the signature you provided. Check your key and signing method.' while other users did not while uploading some file to our dockerized minio on local development environment.

After a lot of reading about minio and reverse proxies, which does not apply in my case, I found out it was because we store author firstname in metadata and mine has an accented character in it.

As I did not find any resources about this while searching about this error, I thought it would be a good idea to write about it somewhere, let me know if here is not the best place.

@prakashsvmx
Copy link
Member

Yes.

 await minioClient.putObject("test-bucket", "test.txt", fileStream, stats.size,{
        "x-amz-tagging":"Key1=Value3",
        "test-meta":"meta key",
       //  "firstname": "Léo" // This fails. 
    })

I checked minio-go it works. i will investigate further in this sdk

@prakashsvmx
Copy link
Member

Mostly how the header values are encoded while request is sent. needs investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants