[
https://issues.apache.org/jira/browse/HDDS-15600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-15600:
----------------------------------
Labels: pull-request-available (was: )
> Fix ListObjects response for encoding-type, empty delimiter, and
> control-character prefix
> -----------------------------------------------------------------------------------------
>
> Key: HDDS-15600
> URL: https://issues.apache.org/jira/browse/HDDS-15600
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: S3
> Reporter: Gargi Jaiswal
> Assignee: Gargi Jaiswal
> Priority: Major
> Labels: pull-request-available
>
> Ozone S3 Gateway fails *s3-tests ListObjects* cases that AWS S3 passes:
> # {{{color:#de350b}test_bucket_list_encoding_basic{color}}}{color:#de350b} —
> {color}With {*}{{EncodingType=url}}{*}, keys and CommonPrefixes containing
> spaces are encoded with {{+}} (Java {{URLEncoder}} form encoding) instead of
> *AWS-style {{{}%20{}}}.*
> Example: {color:#00875a}prefix {{quux ab/}}{color} is returned as
> *{{quux+ab/}}* but should be {*}{{quux%20ab/}}{*}.
> # {color:#de350b}{{test_bucket_list_delimiter_empty}} —{color} When
> {{{*}Delimiter='{*}'}} is sent, listing behavior is correct (all keys
> returned, no CommonPrefixes), but the response incorrectly includes a
> {*}{{Delimiter}} field{*}. AWS omits {{Delimiter}} from the XML when the
> client passes an empty delimiter.
> # {{{color:#de350b}test_bucket_list_prefix_unreadable{color}}} —
> {{{*}ListObject{*}s}} with *{{Prefix='\x0a'}} (newline)* should echo the
> prefix in the response and return empty Contents/CommonPrefixes. Ozone may
> not preserve or echo the control-character prefix correctly.
> https://ozone.s3.peterxcli.dev/#latest-run-section
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
