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

Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2019/12/18 12:40:00 UTC

[jira] [Closed] (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 ]

Julian Reschke closed JCR-3867.
-------------------------------

> [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
>          Components: jackrabbit-data
>    Affects Versions: 2.10
>            Reporter: Shashank Gupta
>            Assignee: Shashank Gupta
>            Priority: Major
>             Fix For: 2.10
>
>         Attachments: JCR-3867.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> 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
(v8.3.4#803005)