fix: reject start-after in ListObjects V1

listobjects v1 now returns InvalidArgument when the start-after query parameter is present, matching s3, which only accepts it with list-type=2. previously the parameter was silently ignored.

Fixes #2004
This commit is contained in:
dualfroz committed 2026-10-07 19:38:54 +02:00
1 parent 09e1b65724
commit b3bf48bdcb
6 files changed
+67 -3

No files matched your search

+18
View File
@@ -1212,6 +1212,24 @@ func TestS3ApiController_ListObjects(t *testing.T) {
err: s3err.GetInvalidArgMaxLimiter(string(utils.LimiterTypeMaxKeys), "bla"),
},
},
{
name: "start-after is not supported",
input: testInput{
locals: defaultLocals,
beRes: listResult,
queries: map[string]string{
"start-after": "my-key",
},
},
output: testOutput{
response: &Response{
MetaOpts: &MetaOptions{
BucketOwner: "root",
},
},
err: s3err.GetInvalidArgumentErr(s3err.InvalidArgStartAfter, ""),
},
},
{
name: "backend returns error",
input: testInput{