duongnguyen0 commented on PR #3531: URL: https://github.com/apache/ozone/pull/3531#issuecomment-1163830859
> Thanks @duongnguyen0 for working on this. The change looks good, but I have two questions on scope. > > I see one more exception stack trace (see below) related to invalid auth headers. Is [HDDS-6905](https://issues.apache.org/jira/browse/HDDS-6905) intended to address it, or should it be fixed here? Thanks for the detailed review, @adoroszlai. The following log line, as well as others in `AuthorizationV4HeaderParser` should be addressed in this CR. It's great that you pointed out. I'll be sending a new version for this. ``` s3g_1 | 2022-06-18 00:28:29,054 [qtp1305004711-24] ERROR signature.AuthorizationV4HeaderParser: AWS access id shouldn't be empty. credential:/20220618/us-west-1/s3/aws4_request ``` And the other looks like a mishandling of exception and that results in an unhandled exception logging, it should be a part of [HDDS-6905](https://issues.apache.org/jira/browse/HDDS-6905). ``` Jun 18, 2022 12:28:29 AM org.glassfish.jersey.internal.Errors logErrors s3g_1 | WARNING: The following warnings have been detected: WARNING: Unknown HK2 failure detected: s3g_1 | MultiException stack 1 of 1 s3g_1 | javax.ws.rs.WebApplicationException: The authorization header you provided is invalid. s3g_1 | at org.apache.hadoop.ozone.s3.OzoneClientProducer.wrapOS3Exception(OzoneClientProducer.java:140) s3g_1 | at org.apache.hadoop.ozone.s3.OzoneClientProducer.getSignature(OzoneClientProducer.java:101) ``` -- 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]
