On S3 connection, unable to open final directory in hierarchy to download file #4356
Comments
What application have you used to create these folders? The issue is that S3 lacks the concept of directories and these are just placeholder (marker) files with different applications having different strategies on their representation. We recognize directory markes with a MIME type of |
The S3fox plugin has a dumb behaviour of adding the |
My ISP automatically creates these files (they're backups) so I don't know what tools they're using. After seeing your comment, I downloaded yet another S3 client called S3Hub and it shows the folders fine as well, so Cyberduck remains the only client I've tried that suffers from this issue. I'll just use S3Hub instead. |
I just installed Cyberduck and am trying to download a file from my Amazon S3 account. I connected fine and could traverse through the hierarchy of folders fine until I got to the final (most descendent) set of folders in the hierarchy. Instead of showing as folders, these instead show as files (right-clicking and choosing Info shows "Unknown" kind) and when I double-clicked one it actually downloaded a 38 byte file with the following contents:
{E40327BF-517A-46e8-A6C3-AF51BC263F59}
When I look at my S3 account through the S3fox firefox plugin, these appear as normal folders and I can open them to see the actual files inside, so it's definitely a Cyberduck issue.
I don't know if this is related or not, but each of these folders contains only a single file which happens to be the same name as the folder plus an extension. For example, one of these folders is named "10-03-31" and it contains just one file named "10-03-31.sql.gz"
The text was updated successfully, but these errors were encountered: