You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Andrei Filimonov (JIRA)" <ji...@apache.org> on 2016/11/11 22:54:58 UTC

[jira] [Commented] (JCR-3928) Enable pathStyleAccess in AWS Client

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

Andrei Filimonov commented on JCR-3928:
---------------------------------------

HTTP support is not removed at all. https is used just as example. I'm not sure if understand second question. Endpoint handling is the same. The only enhancement is to be able to use pathStyleAccess for S3 buckets.

> Enable pathStyleAccess in AWS Client
> ------------------------------------
>
>                 Key: JCR-3928
>                 URL: https://issues.apache.org/jira/browse/JCR-3928
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.11.1
>            Reporter: Andrei Filimonov
>
> jackrabbit-aws-ext:
> Enable pathStyleAccess in AWS Client. Some on premise S3 compatible storage solutions require path style access to S3 objects i.e.
> https://s3endpoint/s3bucket/objectkey
> instead of default
> https://s3bucket.s3endpoint/objectkey
> New property pathStyleAccess=true/false can control this option. I submitted pull request with proposed implementation:
> https://github.com/apache/jackrabbit/pull/31



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