You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/06/29 07:21:05 UTC

[jira] [Commented] (JCLOUDS-185) Support configuration of Azure Cache-Control Headers

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

Andrew Gaul commented on JCLOUDS-185:
-------------------------------------

API reference:

https://msdn.microsoft.com/en-us/library/azure/ee691966.aspx

> Support configuration of Azure Cache-Control Headers
> ----------------------------------------------------
>
>                 Key: JCLOUDS-185
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-185
>             Project: jclouds
>          Issue Type: New Feature
>          Components: jclouds-blobstore
>            Reporter: John Kew
>              Labels: azureblob
>
> Currently cache-control headers cannot be easily set with azure blobs; because we assume that all user metadata has the same prefix. Cache-Control headers fall into the grey area of content vs user metadata, but we need a way to either allow for directly set headers, or to make an exception for the Cache-Control headers.
> See: http://mail-archives.apache.org/mod_mbox/incubator-jclouds-user/201306.mbox/%3CCAJ7Hqj_aEpa1yh4BE%3DWz4ew%2BO5JnJhuPztgYDUE%2BY4-h%2BSpmNQ%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)