[
https://issues.apache.org/jira/browse/HDDS-15302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chu Cheng Li updated HDDS-15302:
--------------------------------
Description:
* Tests:
[{{test_bucket_list_maxkeys_invalid}}|https://ozone.s3.peterxcli.dev/?q=test_bucket_list_maxkeys_invalid&run=2026-05-17T05-56-28Z&caseSuite=s3_tests&test=test_bucket_list_maxkeys_invalid#search-section]
* Failure: s3-tests expects {{{}InvalidArgument{}}}; Ozone returns an empty or
differently mapped error code.
* Analysis: The listing implementation exists; the gap is strict request
validation and error body mapping.
was:
* Tests:
[{{test_bucket_list_maxkeys_invalid}}|https://ozone.s3.peterxcli.dev/?q=test_bucket_list_maxkeys_invalid&run=2026-05-17T05-56-28Z&caseSuite=s3_tests&test=test_bucket_list_maxkeys_invalid#search-section]
* Failure: s3-tests expects {{{}InvalidArgument{}}}; Ozone returns an empty or
differently mapped error code.
* Analysis: The listing implementation exists; the gap is strict request
validation and error body mapping.
* Root cause: The max-keys parsing/validation path handles only part of the
invalid value space before exceptions escape through generic mapping.
* Possible fix: Validate non-integer, negative, and out-of-range max-keys
before listing, and return the AWS {{InvalidArgument}} error shape.
> Throw S3 InvalidArgument for RequestParameters getInt if parsing error
> ----------------------------------------------------------------------
>
> Key: HDDS-15302
> URL: https://issues.apache.org/jira/browse/HDDS-15302
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: s3gateway
> Reporter: Chu Cheng Li
> Assignee: Chu Cheng Li
> Priority: Minor
>
> * Tests:
> [{{test_bucket_list_maxkeys_invalid}}|https://ozone.s3.peterxcli.dev/?q=test_bucket_list_maxkeys_invalid&run=2026-05-17T05-56-28Z&caseSuite=s3_tests&test=test_bucket_list_maxkeys_invalid#search-section]
> * Failure: s3-tests expects {{{}InvalidArgument{}}}; Ozone returns an empty
> or differently mapped error code.
> * Analysis: The listing implementation exists; the gap is strict request
> validation and error body mapping.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
