jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alin Dreghiciu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-1391) [azureblob] Headers must be sorted by lowercase when calculating signature
Date Wed, 07 Mar 2018 21:29:00 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alin Dreghiciu updated JCLOUDS-1391:
------------------------------------
    Description: 
Azure will sort headers by lowercase value so if there are headers like: B=v1 and a=v2, jclouds
will sort them in the order B,a while Azure will sort them as a,B

This will result in an invalid signature.

The failure only appear when copying metadata as the copy options do not lowercase the metadata
keys,

  was:
Azure will sort headers by lowercase value so if there are headers like: B=v1 and a=v2, jclouds
will sort them in the order B,a while Azure will sort them as a,B

This will result in an invalid signature.


> [azureblob] Headers must be sorted by lowercase when calculating signature
> --------------------------------------------------------------------------
>
>                 Key: JCLOUDS-1391
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1391
>             Project: jclouds
>          Issue Type: Bug
>            Reporter: Alin Dreghiciu
>            Priority: Major
>
> Azure will sort headers by lowercase value so if there are headers like: B=v1 and a=v2,
jclouds will sort them in the order B,a while Azure will sort them as a,B
> This will result in an invalid signature.
> The failure only appear when copying metadata as the copy options do not lowercase the
metadata keys,



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message