[
https://issues.apache.org/jira/browse/JCLOUDS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103535#comment-15103535
]
ASF subversion and git services commented on JCLOUDS-185:
---------------------------------------------------------
Commit 01e10bba6692f3904199305d50fea76f5658014e in jclouds's branch
refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=01e10bb ]
JCLOUDS-948: Azure Cache-Control support
References JCLOUDS-185.
> 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
> Affects Versions: 1.9.0
> Reporter: John Kew
> Assignee: Andrew Gaul
> 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)
