versity-versitygw

0 Fork 0

T

dualfroz cbe870a618 fix: accept upload-id-marker together with key-marker in ListMultipartUploads

The posix and azure backends dropped every upload with a key equal to
the key-marker before handing the list to the lister, which then looked
for the upload-id-marker under the next key. An upload-id-marker that
belongs to the key-marker could never be found, so the request failed
with "Invalid uploadId marker", including when a client paged with the
NextKeyMarker and NextUploadIdMarker the gateway returned.

Keep the uploads of the key-marker itself when an upload-id-marker is
set, so the listing continues right after the given upload, as S3 does.
Enable the REST test that covers it.

Fixes #2149

2026-10-03 16:41:32 +02:00

backend

fix: accept upload-id-marker together with key-marker in ListMultipartUploads

2026-10-03 16:41:32 +02:00

s3api

fix: drop upload-id-marker without key-marker in ListMultipartUploads

2026-10-03 17:49:52 +02:00

s3err

fix: validate and apply the ListBuckets bucket-region query

2026-10-05 20:42:18 +02:00

tests

fix: accept upload-id-marker together with key-marker in ListMultipartUploads

2026-10-03 16:41:32 +02:00

website

fix: return InvalidURI for a malformed escape in the request path

2026-10-03 15:13:16 +02:00