libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey (JIRA)" <>
Subject [jira] [Created] (LIBCLOUD-792) S3 SignatureDoesNotMatch
Date Mon, 11 Jan 2016 18:37:39 GMT
Alexey created LIBCLOUD-792:

             Summary: S3 SignatureDoesNotMatch
                 Key: LIBCLOUD-792
             Project: Libcloud
          Issue Type: Bug
          Components: Storage
            Reporter: Alexey

I noticed that *sometimes* upload fails with SignatureDoesNotMatch error. I tried to debug
this, and I got the following notice in the error message from S3:


and in the code libcloud/storage/drivers/ string_to_sign equals the following

string_to_sign = "PUT\nE8F2ok2KBiJTfNy91PLz+A==\n\n1452529414\n/mybucket/11.png?uploadId=DQGexmin_N3usw4giAtLWoRbCWWRWQij2a20xPO_BgSRENZRpgGqhgMm9goSPoHkmkheIMBrPcI_Z2xWZtqMmZcmekuVhpTBre4cuS.nfyP6DQuTPEuAYop5abOHbm2t&partNumber=1"

Obviously the order of GET parameters is not preserved. I have no idea how to hot-fix this
issue (except replacing *params* dictionary with OrderedDict or array of tuples, but this
is a pretty big change)

This message was sent by Atlassian JIRA

View raw message