Cyberduck shows fake "phantom" folders on S3 #8830
Comments
Here's the log for that btw: GET /?max-keys=1000&prefix=2015%2FTest4%2F&delimiter=%2F HTTP/1.1 Date: Thu, 14 May 2015 16:24:42 GMT Authorization: AWS [obfuscated] Host: nuk-tnl-editorial-prod-graphics.s3.amazonaws.com:443 Connection: Keep-Alive User-Agent: Cyberduck/4.7.17432 (Mac OS X/10.9.5) (x86_64) HTTP/1.1 200 OK x-amz-id-2: [obfuscated] x-amz-request-id: [obfuscated] Date: Thu, 14 May 2015 16:24:44 GMT Content-Type: application/xml Transfer-Encoding: chunked Server: AmazonS3 GET /?max-keys=1000&versions&prefix=2015%2FTest4%2F&delimiter=%2F HTTP/1.1 Date: Thu, 14 May 2015 16:24:43 GMT Authorization: AWS [obfuscated] Host: nuk-tnl-editorial-prod-graphics.s3.amazonaws.com:443 Connection: Keep-Alive User-Agent: Cyberduck/4.7.17432 (Mac OS X/10.9.5) (x86_64) x-amz-id-2: [obfuscated] x-amz-request-id: [obfuscated] Date: Thu, 14 May 2015 16:24:44 GMT Content-Type: application/xml Transfer-Encoding: chunked Server: AmazonS3 |
I've noticed (and so has a colleague, who just showed me the same behaviour on his machine) that Cyberduck shows empty "phantom" duplicate folders in S3 with the same name as the parent folder, which don't actually exist in S3.
I.e., if you upload "hurr" to /my-bucket, there's an empty folder as /my-bucket/hurr/hurr, but this folder doesn't actually exist if you look inside the bucket via the AWS console.
Attachments
Screen Shot 2015-05-14 at 17.19.11.png(288.4 KiB)The text was updated successfully, but these errors were encountered: