[Cyberduck-trac] [Cyberduck] #3353: Directory not visible when key with same name exists

[Cyberduck]

#3353: Directory not visible when key with same name exists
-----------------------+----------------------------------------------------
 Reporter:  anonymous  |       Owner:  dkocher
     Type:  defect     |      Status:  new    
 Priority:  normal     |   Milestone:         
Component:  s3         |     Version:  3.2.1  
 Severity:  normal     |    Keywords:         
-----------------------+----------------------------------------------------

Old description:

> This is a problem revealed when using "s3sync" to store backups on S3.
>
> s3sync (and other S3 clients, presumably) use "fake" S3 objects to
> represent directories.
>
> Let's say I have two objects in my bucket:
>
> mybucket:folder1
> mybucket:folder1/myfile.txt
>
> In this case, "folder1" is both a prefix and a valid object which was
> created to simulate a folder.
>
> What will happen is Cyberduck will only display the fake folder object
> and not show the folder1 "directory", so I can't tell there's a real
> directory there too.

New description:

 This is a problem revealed when using "s3sync" to store backups on S3.

 s3sync (and other S3 clients, presumably) use "fake" S3 objects to
 represent directories.

 Let's say I have two objects in my bucket:


 {{{
 mybucket:folder1
 mybucket:folder1/myfile.txt
 }}}


 In this case, "folder1" is both a prefix and a valid object which was
 created to simulate a folder.

 What will happen is Cyberduck will only display the fake folder object and
 not show the folder1 "directory", so I can't tell there's a real directory
 there too.

--

Comment(by dkocher):

 This really should work as we do the same thing to create an empty
 directory; create a file with a MIME type of application/x-directory.

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/3353#comment:3>
Cyberduck <http://cyberduck.ch>
FTP, SFTP, WebDAV, Cloud Files and Amazon S3 Browser for Mac OS X.