Is part-number-marker = 0
valid in list-parts request #207
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#207
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is your feature request related to a problem? Please describe.
Some S3 API clients set "0" values in
part-number-marker
parameter of list-parts request.FrostFS S3 Gateway denies "0" value.
Meanwhile minio allows (1,2 it.
Describe the solution you'd like
Check out AWS S3 docs once again and AWS S3 API whether "0" value is allowed or not.
If it is allowed, then fix condition in FrostFS S3 Gateway.
If it is not allowed, then add a "kludge" flag and make condition based on a flag value.
Describe alternatives you've considered
None.
"0" value is allowed.
Also if
part-number-marker
isn't less than the largest loaded part number, no parts should be returned. In current implementation it returns parts starting from the first one.