You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Peter Schmidt (JIRA)" <ji...@apache.org> on 2014/12/01 00:39:14 UTC

[jira] [Updated] (LIBCLOUD-638) Can't set CORS headers via container.upload_object_via_stream()

     [ https://issues.apache.org/jira/browse/LIBCLOUD-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Schmidt updated LIBCLOUD-638:
-----------------------------------
    Attachment: libcloud_638.patch

As it was reviewed on Github PR #403, optimistically adding a final patch.

https://libcloud.readthedocs.org/en/latest/development.html#contribution-workflow

> Can't set CORS headers via container.upload_object_via_stream()
> ---------------------------------------------------------------
>
>                 Key: LIBCLOUD-638
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-638
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: Storage
>            Reporter: Peter Schmidt
>         Attachments: libcloud_638.patch
>
>
> Would be nice to have the ability to set Cross-Origin Resource Sharing (CORS) headers, and probably other headers too when using `container.upload_object_via_stream()` without subclassing and overriding several lower level functions.
> References:
> https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS#Access-Control-Allow-Origin
> http://docs.rackspace.com/files/api/v1/cf-devguide/content/Assigning_CORS_Headers_to_Requests-d1e2120.html
> Ran into this migrating a project from Rackspace cloudfiles which allows setting of CORS headers.



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