libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-430) Support content-disposition header
Date Mon, 02 Dec 2013 12:01:41 GMT

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

ASF subversion and git services commented on LIBCLOUD-430:
----------------------------------------------------------

Commit 7b3fd341a5dcf5ce2d313e8a20ec7b9177f5c727 in branch refs/heads/trunk from [~micolous]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=7b3fd34 ]

LIBCLOUD-430: Implement support for content-disposition header in the CloudFiles driver.

Signed-off-by: Tomaz Muraus <tomaz@apache.org>


> Support content-disposition header
> ----------------------------------
>
>                 Key: LIBCLOUD-430
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-430
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: Storage
>    Affects Versions: 0.13.2
>            Reporter: Michael Farrell
>         Attachments: libcloud430.patch
>
>
> Implement functionality to be able to support sending the Content-Disposition header
with stored files.  This allows them to have flags set allowing their original filename to
be preserved when downloaded from a CDN, and suggest to the browser that the file should be
saved to disk rather than displayed.
> I've implemented this in https://github.com/Caramel/libcloud/commit/181ed20, however
it also included an initial workaround for the problem I've separately reported in LIBCLOUD-429.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message