uploaded contents in S3 bucket are invisible / unreadable ?

[vesper8]

I am trying out this plugin. It appears to be working. It's created folders on my bucket and refreshing the page while spoofing GoogleBot is resulting in the page being returned super fast.

I use a GUI client (Forklift) to explore my S3 bucket and was met with some baffling stuff.. it's created dozens of folders with no name as far as I can see, and no files in them. I then logged on to my AWS console to have a look there.. thinking my GUI client might be at fault.. and even here in the bucket explorer, I can see the top level folder name but inside it's empty.. although going to "get total size" does reveal that it's not completely empty.

Just curious how come this plugin creates invisible files and folders like this?

On that note.. is there currently a way to invalidate all cache? short of deleting the whole root folder in the S3 bucket? I know I can use the POST to recache individual entries.. but what about if I just want to clear them.. and not recache them right away?

[okgolove]

That happens because of trailing slash.
For your GUI client and for AWS S3 console test222/ is a "directory" (technically, there are no directories in s3).
If you request url without trailing slash cache is saved as a "file".