Gargi-jais11 opened a new pull request, #10860:
URL: https://github.com/apache/ozone/pull/10860
## What changes were proposed in this pull request?
S3 Gateway returns `404 NoSuchKey` for GetObject requests with
unreadable/invalid object keys, instead of `400 InvalidURI `as AWS S3 does.
Ozone already defines the correct error in S3ErrorTable.INVALID_URI but
never uses it:
`INVALID_URI("InvalidURI", "Couldn't parse the specified URI.",
HTTP_BAD_REQUEST)`
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.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-15958
## How was this patch tested?
Add Unit and Integration Tests.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
