You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Shashank Gupta (JIRA)" <ji...@apache.org> on 2015/04/03 21:05:53 UTC

[jira] [Updated] (JCR-3867) [jackrabbit-aws-ext] Handle 403(forbidden) status in checking existence of object in S3

     [ https://issues.apache.org/jira/browse/JCR-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shashank Gupta updated JCR-3867:
--------------------------------
        Fix Version/s: 2.10
    Affects Version/s: 2.10
               Status: Patch Available  (was: Open)

> [jackrabbit-aws-ext] Handle 403(forbidden) status in checking existence of object in S3
> ---------------------------------------------------------------------------------------
>
>                 Key: JCR-3867
>                 URL: https://issues.apache.org/jira/browse/JCR-3867
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>    Affects Versions: 2.10
>            Reporter: Shashank Gupta
>            Assignee: Shashank Gupta
>             Fix For: 2.10
>
>         Attachments: JCR-3867.patch
>
>
> Some cloud provider ( for e.g. Adobe S3) send 403 (forbidden) status indicating object doesn't exists in S3. Till now S3DS rely only  404 (not found) status . Add handling of 403 (forbidden) status . 



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