[
https://issues.apache.org/jira/browse/JCLOUDS-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441737#comment-16441737
]
Andrew Gaul edited comment on JCLOUDS-1409 at 4/18/18 1:28 AM:
---------------------------------------------------------------
It looks like 68e6539192690a10afc450c1bb6cc623e0e25224 introduced this
regression while fixing the symptoms in JCLOUDS-1042. In this case we removed
a (cached) bucket call during an object operation for permission reasons. It
does not appear that S3 returns the bucket or object ACL during this request.
It may be best to always return the URL even if not public, disable the test,
or remove this functionality altogether.
was (Author: gaul):
It looks like 68e6539192690a10afc450c1bb6cc623e0e25224 regression which fixed
the symptoms in JCLOUDS-1042. Often times regressions creep in when fixing
other things. In this case we removed a (cached) bucket call during an object
operation for permission regions. It does not appear that S3 returns the
bucket or object ACL during this request. It may be best to always return the
URL even if not public, disable the test, or remove this functionality
altogether.
> Cannot set public access at s3 objects.
> ---------------------------------------
>
> Key: JCLOUDS-1409
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1409
> Project: jclouds
> Issue Type: Bug
> Reporter: Sharad Holani
> Priority: Major
>
> Why are the S3ContainerLiveTest.testPublicAccess() and
> PathBasedContainerLiveTest.testPublicAccess() failing against S3 default
> region (Did not try for other regions)?
> There is no provision to apply public level access control using
> S3Client.putObject() API.
> And if these test cases are failing why aren't they disabled or ignored?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
