Gracefully handle non-compliant S3 bucket listing

Issue #286 wontfix
created an issue

S3QL maintainer here. Yes, if Exoscale returns object names that don't start with the provided prefix, it would cause this error. The S3 API requires returning an empty list if there are no objects with the prefix.

Thank you for your answer!

Could we add a check for those broken S3 implementations? I mean displaying a human error message.

Comments (3)

  1. Log in to comment