[Cyberduck-trac] [Cyberduck] #11896: Cannot read container configuration for S3 bucket in server field

[Cyberduck]

#11896: Cannot read container configuration for S3 bucket in server field
-----------------------+---------------------
    Reporter:  jmalek  |      Owner:  dkocher
        Type:  defect  |     Status:  new
    Priority:  normal  |  Milestone:
   Component:  s3      |    Version:  8.0.0
    Severity:  normal  |   Keywords:
Architecture:          |   Platform:
-----------------------+---------------------
 For S3 connections to bucket.s3.amazonaws.com navigating to any path
 results in a Cannot read container configuration.

 This is due to:
 [https://github.com/iterate-
 ch/cyberduck/blob/master/s3/src/main/java/ch/cyberduck/core/s3/S3VersioningFeature.java#L139
 S3VersioningFeature] trying to get path container information, which
 cannot be retrieved, as the bucket (from containerService, which is a
 [https://github.com/iterate-
 ch/cyberduck/blob/master/s3/src/main/java/ch/cyberduck/core/s3/S3Protocol.java#L187
 DirectoryDelimiterPathContainerService]) is already supplied in the server
 hostname.

 Fixing requires checking whether a bucket name has been set in the
 hostname to prevent subsequent checks for buckets in buckets.

--
Ticket URL: <https://trac.cyberduck.io/ticket/11896>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows