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/01/23 23:09:35 UTC
[jira] [Updated] (JCLOUDS-185) Support configuration of Azure
Cache-Control Headers
[ https://issues.apache.org/jira/browse/JCLOUDS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Gaul updated JCLOUDS-185:
--------------------------------
Component/s: jclouds-blobstore
> 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/browser
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)