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

Posted to hdfs-dev@hadoop.apache.org by "Steve Vaughan (Jira)" <ji...@apache.org> on 2022/08/30 19:13:00 UTC

[jira] [Created] (HDFS-16753) WebHDFSHandler should reject non-compliant requests

Steve Vaughan created HDFS-16753:
------------------------------------

             Summary: WebHDFSHandler should reject non-compliant requests
                 Key: HDFS-16753
                 URL: https://issues.apache.org/jira/browse/HDFS-16753
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: hdfs
    Affects Versions: 3.4.0, 3.3.9
         Environment: Tested using both Maven Surefire and an IDE to demonstrate that the fix correctly rejects the invalid request with a 400 status code.
            Reporter: Steve Vaughan
            Assignee: Steve Vaughan


When the nnId is not provided to the WebHDFSClient, the request uses null to generate a URI using a host name of "null" to construct a DFSClient instance.  In environments where the host name "null" doesn't resolve, the test passes due to the unresolvable name.  If the host name "null" does resolve, then this results in repeated attempts through the retry mechanism, eventually causing a timeout and a failed test result.

This change make the parameter a precondition for constructing the DFSClient, which throws an exception, rejecting the request, and return the expected 400 status code.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org