jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashank Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3928) Enable pathStyleAccess in AWS Client
Date Tue, 15 Mar 2016 14:40:33 GMT

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

Shashank Gupta commented on JCR-3928:
-------------------------------------

[~afilimonov]  Few questions around your patch:
1. Why HTTP support is removed. JCR-3804
2. Why endpoint handling is removed. JCR-3732, JCR-3788

CC [~mmarth]

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

Mime
View raw message