GitHub user encyphered opened a pull request:

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

    S3 support for AWS Seoul region

    Support S3 Seoul region. In addition, this PR includes modification about 
Amazon signature V4 due to Seoul region does not support signature V2.
    
    Modification that S3 requires:
    * Removed HTTP method restriction from AWSRequestSignerAlgorithmV4
    * Added hash of the request payload as X-AMZ-Content-SHA256 header
    * Prevent Host / Accept-Encoding header duplication

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

    $ git pull https://github.com/encyphered/libcloud aws-s3-apne2

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

    https://github.com/apache/libcloud/pull/687.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 #687
    
----
commit f8d0b9b842d81488912d0caf9a176a2a33a67302
Author: Geunwoo Shin <[email protected]>
Date:   2016-01-27T10:47:12Z

    Do not add automatically host / accept-encoding header
    
    Due to headers dictionary always have host / accept-encoding value, when
    perform 'raw' request, host / accept-encoding header would be
    duplicated. If you use AWSRequestSignerAlgorithmV4, this occurs invalid
    payload hash.

commit 4ae9a5eb57f6cfb75c7160eae0a9bb932d75a320
Author: Geunwoo Shin <[email protected]>
Date:   2016-01-27T10:52:39Z

    Support methods any other GET and POST in Signature V4
    
    AWS S3 operations require HEAD / PUT / GET request

commit 7a90d03acedfb17589e9981cd41cbf9163012b5c
Author: Geunwoo Shin <[email protected]>
Date:   2016-01-27T14:46:34Z

    Cast header value as str in canonical_headers
    
    Type of header value may be other than a str, such as int.
    e.g. Value of content-lengh when POST/PUT

commit 061c0c6860490bb651736100b8f4017308e8b4ee
Author: Geunwoo Shin <[email protected]>
Date:   2016-01-27T14:51:40Z

    Add missing X-AMZ-Content-SHA256 header
    
    Missing X-AMZ-Content-SHA256 header can occur 400 bad request
    on several service such as S3

commit a77ca4fc342328d4aa9ad02e2ee16916a3149018
Author: Geunwoo Shin <[email protected]>
Date:   2016-01-27T15:08:49Z

    S3 provider / driver / connection for AWS Seoul region

----


---
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