[BUGFIX] Using headObject to proof that a folder exists does not work in every case #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If files in the bucket were created by a 3rd party tool and the folder structure is not created explicity beforehand (which is not necesssary because S3 allows a structured filesystem just by prefixes), the headObject method returns a 404, because there is no folder object to fetch meta data from.
We can use listObjects in this case. If it delivers min. 1 object, we can assume that it is a folder.