Unable to view Cloud container objects that contain folders

[cyberduck]

0101100 created the issue

When viewing a Mosso/Rackspace Cloud Files container that contains objects within folders, they do not display in Cyberduck. They can only be view via the Rackspace Control Panel page (see attached image).

---

Attachments

• Screen shot 2009-12-07 at 4.13.37 PM.png (39.6 KiB)
• Screen shot 2009-12-07 at 4.13.50 PM.2.png (98.3 KiB)
• Screen shot 2009-12-07 at 4.13.50 PM.png (98.3 KiB)
• Screen shot 2009-12-09 at 11.09.22 AM.png (31.1 KiB)
• Screen shot 2009-12-09 at 11.09.32 AM.png (42.8 KiB)

[cyberduck]

0101100 commented

Sorry for the multiple attachments and misnaming of the them.

[cyberduck]

@dkocher commented

Can you find any related output in the system.log (/Applications/Utilities/Console.app)?

[cyberduck]

0101100 commented

Nothing in the Console related to Cyberduck.

[cyberduck]

@dkocher commented

Replying to [comment:3 JPdemole]:

Nothing in the Console related to Cyberduck.

Of interest would also be the transcript in the log drawer. We will have to check with Rackspace support then as I cannot replicate the issue. Please also try to add another container and files.

[cyberduck]

0101100 commented

After some further investigation... it looks like it's the way I'm uploading the files (via Paperclip, rails plugin).

If I simply drag a folder that contains files into the container, it creates the object, but also creates and empty object for the directory listing.

I do not have that for the ones that were uploaded via paperclip. I created a folder called cues/ and also inside there added a couple test directories (1/, 2/, 3/ .. 10/) and dragged it into the container.

I can now view the cues/1/ - cues/10/ folders, but not anything else. So in order to see 11/ -- X/ I would have to by hand create these and drop them in to get visibility for these files for some reason.

Not sure if this helps :) But it's a workaround for now.

Thanks.

[cyberduck]

@dkocher commented

Ticket Number 11424 at Rackspace.

[cyberduck]

74cfdfc commented

I can duplicate the bug. Any file uploaded externally to Cyberduck cannot be seen if it has a "/" in it. I uploaded (via Cyberduck) a file inside of a folder and Cyberduck can see it. I uploaded (via the Python bindings) a file and Cyberduck can see it. I uploaded (via the Python bindings) a file with "/" in the filename, and Cyberduck does not show it.

John Dickinson Cloud Files Developer

[cyberduck]

@dkocher commented

Replying to [comment:7 john.dickinson@…]:

I can duplicate the bug. Any file uploaded externally to Cyberduck cannot be seen if it has a "/" in it. I uploaded (via Cyberduck) a file inside of a folder and Cyberduck can see it. I uploaded (via the Python bindings) a file and Cyberduck can see it. I uploaded (via the Python bindings) a file with "/" in the filename, and Cyberduck does not show it.

John Dickinson Cloud Files Developer

The cf-devguide documentation says:

To take advantage of this feature, the directory marker Objects must also be created to represent the appropriate directories. The following additional Objects need to be created. A good convention would be to create these as zero or one byte files with a Content-Type of application/directory.

As per this convention, Cyberduck will not recognize files nested with more than one / delimiter when there is no marker object between with a application/directory MIME type.

[cyberduck]

@dkocher commented

Support at Rackspace Cloud said:

Cyberduck is conforming to our dev docs. Other clients that upload nested directories without setting directory markers will not have their content shown in Cyberduck (because Cyberduck is using the path query on container listings).