S3 signature doesn't match expected when path contains special chars

[gipeshka]

Hi guys.

Currently I'm facing an issue with alpakka s3 client 0.10 when accessing a file like files/überall.csv

The request signature we calculated does not match the signature you provided. Check your key and signing method.

When I pass the key with encoded special chars, e.g. files/%C3%BCberall.csv I get another exception: The specified key does not exist.

Supposedly the issue is related to #357 and #316 because in version 0.9 I had exactly the error
akka.http.scaladsl.model.IllegalUriException: Illegal URI reference: Invalid input 'ü', expected '/', 'EOI', '#', '?' or pchar for exactly same configuration.

[francisdb]

Will create a test and look into this!

[gipeshka]

Hey @francisdb I added one on my local branch, actually shows that it's broken. I'll try to look into it myself, but anyway hope it helps gipeshka@d10058b

[francisdb]

Also got this reproduced, I wonder if there is still some issue with the CanonicalRequest logic

[francisdb]

found the issue, non-ASCII chars are not correctly encoded by CanonicalRequest, fix on it's way