You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by sfriesel <gi...@git.apache.org> on 2014/09/09 19:06:21 UTC

[GitHub] libcloud pull request: [LIBCLOUD-612] Customize HTTP vendor prefix...

GitHub user sfriesel opened a pull request:

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

    [LIBCLOUD-612] Customize HTTP vendor prefix for Google Storage

    https://issues.apache.org/jira/browse/LIBCLOUD-612
    
    Google storage uses/expects custom headers like meta data
    and storage class to be prefixed with "x-goog" instead of
    "x-amz". This enables use of object tagging in the Google
    Storage provider.


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

    $ git pull https://github.com/sfriesel/libcloud gs_meta_data

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

    https://github.com/apache/libcloud/pull/356.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 #356
    
----
commit 4b4ed2b578f12387f7abafabacbd8ff9164e598f
Author: Stefan Friesel <sf...@cloudcontrol.de>
Date:   2014-09-09T16:23:34Z

    Customize HTTP vendor prefix for Google Storage
    
    Google storage uses/expects custom headers like meta data
    and storage class to be prefixed with "x-goog" instead of
    "x-amz". This enables use of object tagging in the Google
    Storage provider.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] libcloud pull request: [LIBCLOUD-612] Customize HTTP vendor prefix...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---