GitHub user pzrq opened a pull request:

    https://github.com/apache/libcloud/pull/403

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

    https://issues.apache.org/jira/browse/LIBCLOUD-638

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mathspace/libcloud 638_cors_headers

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/libcloud/pull/403.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #403
    
----
commit d453ef99bffdeaa7c41f5fb76a5df6985ddce2ae
Author: Peter Schmidt <[email protected]>
Date:   2014-11-27T00:20:38Z

    Remove misleading .

commit a1b078b729e0f68bbc83cd56ed51bbf8b70726e1
Author: Peter Schmidt <[email protected]>
Date:   2014-11-27T00:20:57Z

    Typo: fill instead of will.

commit 5c9ad396f54b90912cefe272f68df5fc1b5926fe
Author: Peter Schmidt <[email protected]>
Date:   2014-11-27T03:01:07Z

    [LIBCLOUD-638] Add, document and test for headers to 
``upload_object_via_stream``, and similar methods to enable supporting CORS (or 
other) headers in the cloudfiles driver:
    
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

commit 599f33a5eaff7408a7bc577f3863f302fe98e5e7
Author: Peter Schmidt <[email protected]>
Date:   2014-11-27T03:44:47Z

    Document something that affects a full usage of a bytes iterator but I have 
no idea on the correct fix for.
    e.g. bytes(37) returns 37 null bytes...

commit bf0ef50dfc83e1a78c60f080cabe07faddaa9d71
Author: Peter Schmidt <[email protected]>
Date:   2014-11-27T05:05:43Z

    Consistently order as :param arg: then :type arg: (if there's a higher 
level coding convention I'll happily swap the other half of this file instead).

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to