Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Issue #47 Missed Max Keys on Response #175

Open
castlec opened this issue Aug 20, 2020 · 0 comments
Open

Issue #47 Missed Max Keys on Response #175

castlec opened this issue Aug 20, 2020 · 0 comments

Comments

@castlec
Copy link

castlec commented Aug 20, 2020

It is expected that paging will continue to work as specified on the initial request. For this to function, max keys must be relayed from the request to the response. ListBucket response object does not have a parameter for max keys and instead defaults to 1000. This results in first page being as requested and subsequent pages being at 1000.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant