e1d22849063e0d8cf2d3b123d78cd21652620d39
S3 never lists an empty result for another region: a valid region other than the endpoint's own gets 400 InvalidArgument, "Requests with bucket-region specified must be made to the corresponding regional endpoint", with no ArgumentValue. The gateway is a single regional endpoint, so it now does the same instead of clearing the listing. Match the region case-insensitively like S3, and check an empty bucket-region= too by looking for the query argument itself, since an empty value is not a valid AWS region either.
Description
My contributions to versity/versitygw: 24 commits, 11 merged PRs
345 KiB
0 Stars
1 Watchers
0 Forks
Languages
Go
95.9%
Shell
4.1%