Gargi Jaiswal created HDDS-15958:
------------------------------------
Summary: Return InvalidURI for unreadable S3 object keys on
GetObject
Key: HDDS-15958
URL: https://issues.apache.org/jira/browse/HDDS-15958
Project: Apache Ozone
Issue Type: Sub-task
Components: S3
Reporter: Gargi Jaiswal
Assignee: Gargi Jaiswal
S3 Gateway returns {color:#de350b}404 NoSuchKey{color} for *{{GetObject}}*
requests with unreadable/invalid object keys, instead of {color:#00875a}400
InvalidURI{color} as AWS S3 does.
Ozone already defines the correct error in
{color:#de350b}{{S3ErrorTable.INVALID_URI}}{color} but never uses it:
{code:java}
INVALID_URI("InvalidURI", "Couldn't parse the specified URI.",
HTTP_BAD_REQUEST){code}
The key {{{*}\xae\x8a{*}-}} contains non-printable high bytes
({{{}\x80–\xff{}}}) that Ozone cannot store and that AWS treats as an invalid
URI. S3G should reject it before OM lookup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
