You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Krishna Kumar Asawa (Jira)" <ji...@apache.org> on 2023/08/03 10:14:00 UTC

[jira] [Resolved] (HDDS-4361) S3 native error messages when header is illegal

     [ https://issues.apache.org/jira/browse/HDDS-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krishna Kumar Asawa resolved HDDS-4361.
---------------------------------------
    Resolution: Abandoned

> S3 native error messages when header is illegal
> -----------------------------------------------
>
>                 Key: HDDS-4361
>                 URL: https://issues.apache.org/jira/browse/HDDS-4361
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: S3
>    Affects Versions: 1.0.0
>            Reporter: Li Cheng
>            Priority: Major
>
> Following up on https://issues.apache.org/jira/browse/HDDS-4339 and https://issues.apache.org/jira/browse/HDDS-3843, missing auth or other info in header may cause S3Client to throw NPE or log an error message.
> Rather than that, s3g should return s3 native error messages to requests with invalid header or other reasons. However, s3client should be able to initialized. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org