SignatureDoesNotMatch error with non-ASCII metadata

[aileo]

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]

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]

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

[prakashsvmx]

Applications/clients can use encodeURIComponent( to encode when required and decodeURIComponent(. because it may be a breaking change in this repository for existing applications .. i will see how best we can accommodate it.

node js does not auto encode/decode non-ascii values in headers( metadata)