jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abel Salgado Romero (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1320) Document requirements for Blob Storage accounts in azureblob provider
Date Tue, 11 Jul 2017 20:48:02 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082954#comment-16082954
] 

Abel Salgado Romero commented on JCLOUDS-1320:
----------------------------------------------

Exactly. No regression at all. All types of storage account work once the API version is upgraded,
and since your upgrade is to the last version, it should work.
Thanks,

> Document requirements for Blob Storage accounts in azureblob provider
> ---------------------------------------------------------------------
>
>                 Key: JCLOUDS-1320
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1320
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 2.0.2
>         Environment: Java 8
>            Reporter: Abel Salgado Romero
>            Priority: Minor
>
> First, thanks for the project!
> Now...access to Azure Blob Storage accounts requires an explicit update of the API version
to a newer version. Documentation could be improved to mention that.
> *Current behavior*:
> - Calls to a Blob Storage account (do not confuse with a blob container inside a general
purpose storage account) fail with the error
> {{org.jclouds.http.HttpResponseException: request: HEAD https://------.blob.core.windows.net/-----/Sample-20170711-064501930.pdf
HTTP/1.1 failed with response: HTTP/1.1 400 The value for one of the HTTP headers is not in
the correct format.}}
> - Same code (based on example https://jclouds.apache.org/guides/azure-storage/) works
when used in a general purpose account.
> *Applied fix*
> Debugging the code I could the whole error pointing to {{x-ms-version}} header, so fixing
the issue was easy. Setting the API version with {{ContextBuilder.apiVersion}} to the newer
version "2016-05-31"  was enough.
> *Request*
> I think that a note on the example could be added to help with it, or else, just update
the default version of the API, currently it uses "2013-8-15".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message