[Cyberduck-trac] [Cyberduck] #11752: S3 Empty prefix causing "Failure to read attributes of <prefix>"

Cyberduck trac at cyberduck.io
Wed Aug 4 08:50:34 UTC 2021

#11752: S3 Empty prefix causing "Failure to read attributes of <prefix>"
    Reporter:  freakk    |      Owner:
        Type:  defect    |     Status:  new
    Priority:  high      |  Milestone:
   Component:  core      |    Version:  7.10.0
    Severity:  critical  |   Keywords:  failure attributes empty prefix 404
Architecture:  Intel     |   Platform:  macOS 10.15
 '''USe Case'''
 S3 credentials are restricted to a specific prefix (not root)
 Cyberduck is configured as landing path in the bookmark under "More

 '''Expected''': Cyberduck connects and displays the content of an empty

 Attempt to login when there's no file with that prefix (empty prefix
 "folder") causes error  "Failure to read attributes of <prefix>".
 When there is no file with the prefix, the "folder" itself is eventually
 deleted by S3 (there are no actual s3 folders) and files under the prefix
 will eventually expire according to the lifecycle policy.

 Logs tailed via:
 log stream --predicate '(process == "Cyberduck") && (category ==
 "transcript")' --level info

 Show a failed HEAD call to the prefix (as expected)
 HEAD /orders/**********/ HTTP/1.1
 HTTP/1.1 404 Not Found
 Followed by a succeessful GET
 GET /?encoding-type=url&max-
 HTTP/1.1 200 OK

 - Version 6.7.0 connects to an empty path successfully
 - {{{aws s3 ls XXXXXX}}} returns a successful response with empty payload

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

More information about the Cyberduck-trac mailing list