search

nitisht / minio-evaporatejs-example

Benchmark browser uploads to Minio server via EvaporateJS library
2 stars 0 forks source link

Error: signature does not match #1

Open thomaslange24 opened 5 years ago

thomaslange24 commented 5 years ago

Hi,

I am trying to use evaporate for minio. I installed it with "npm install evaporate" and basically have the same setup like this example shows. except that i am importing evaporate.js form the node_module directory and with the parameter names in the config given from the evaporate docuemntation: https://github.com/TTLabs/EvaporateJS/wiki/Evaporate.create() (Like awsAccessKey is aws_key and awsUrl is aws_url)

I could not figure out crucial differences between the evaporate.js file you are using and the evaporate.js file that is installed with npm. But using the npm installation i get the following error, when trying the upload:

SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.uploadfile100MB.bintestbucket/testbucket/uploadfile100MB.bin15ADDF07C8EFAC9F79a52691-f176-4537-bf57-0dcb78bf7472

Do you have any idea on fixing that? webapp_minio_test.zip

To repoduce first run the "npm ci" command in webapp_minio_test and then "node app-server.js" in webapp_minio_test/evaporate_example. Then open the browser and go to http://localhost:8080

luizotcarvalho commented 4 years ago

Digging around a little I notice that was added port support in the modified evaporate file.

https://github.com/nitisht/minio-evaporatejs-example/blob/190f42f5f15ee4b1e89007789f906abec6cecb4c/evaporate.js#L1019

A solution i've found is to run minio on port 80 and change aws_url to 'http://127.0.0.1'. That way is possible to use the NPM Evaporate file

Ensure that the parameters aws_url and aws_key is named right. (NOT awsAccessKey and awsUrl)