commonPrefixes is only for delimiter request; check size and tier null

[jixinchi]

No description provided.

[gaul]

These seem to make sense but could you explain the user symptoms more clearly, e.g., which provider does this currently fail on?

[jixinchi]

These seem to make sense but could you explain the user symptoms more clearly, e.g., which provider does this currently fail on?

I'm using filesystem as provider, and I have a problem of deleting a "directory" recursively by aws cli. The cli list files with Prefix and without Delimeter, and then delete each items in the Contents field of response. If there are empty directories below the directory to be deleted, these empty directories can not be deleted because they are not in the Contents filed.

There will be a jclouds PR to solve the problem that empty directories not in the Contents field. Here, if an empty directory item is in the Contents field, its size and tier may be null, so I check it here.

In addition, I checked aws doc, and I think commonPrefixes should be only for delimeter request, so I fixed it. But it won't cause failure.

[jixinchi]

Sorry, there are something wrong in above expaination. If the request does not contains delimeter, it should be added to Contents. So I break the switch-case, not continue to next item

[gaul]

Thank you for your contribution and explanation @jixinchi!