fix(s3): max-keys=0 returns empty non-truncated page#2003
Merged
Conversation
ListObjectsV2/V1 with max-keys=0 hit `count >= max_keys` (0 >= 0) on the first
object, setting IsTruncated=true and emitting a continuation token over an
empty last_key (base64("") = ""), which the next request rejects with
InvalidArgument. AWS returns KeyCount=0, IsTruncated=false, no token. Force
is_truncated=false when max-keys=0 in both handlers.
Test: put 2 objects, list with max-keys=0 via V2 and V1 -> empty, not
truncated, no continuation token / NextMarker.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
2026-06-27 bug-hunt Tier 1 finding 1.19 (S3).
ListObjectsV2/ListObjectswithmax-keys=0hitcount >= max_keys(0 >= 0) on the first object, settingIsTruncated=trueand emitting a continuation token over an emptylast_key(base64("") = ""), which the next request rejects withInvalidArgument. AWS returnsKeyCount=0,IsTruncated=false, no token. Forceis_truncated=falsewhenmax-keys=0in both handlers.Test: put 2 objects, list with
max-keys=0via V2 and V1 -> empty, not truncated, no token / NextMarker.Summary by cubic
Fixes S3 ListObjects/ListObjectsV2 when max-keys=0 to return an empty, non-truncated page with no continuation token/NextMarker, matching AWS. Prevents InvalidArgument errors caused by an empty continuation token.
Written for commit 1958688. Summary will update on new commits.