Uploaded image for project: 'Apache Knox'
  1. Apache Knox
  2. KNOX-520

WEBHDFS with knox doesn't support PAT for OPEN operation

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 0.5.0
    • 0.6.0
    • Server
    • None
    • Centos 6
      Hadoop 2.6

    Description

      Network topology :

                                    /==> knox1 ==\
      Load balancer =                              ==> Namenodes
                                    \==> knox2 ==/

      A VIP (dns : knox-server) is supported by the load balancer, listening on 443 TCP port (HTTPS).
      knox1 and knox2 listen on 8443 TCP port (HTTPS).
      So the traffic is NATed/PATed from knox-server:443 to knox1:8443 or knox2:8443.

      When doing an open operation on a file with webhdfs API throught knox it fails beacuse of a bad redirection 307.

      First request from the client (authenticated)
      ==> https://knox-server/gateway/sandbox/webhdfs/v1/tmp/myfile?OP=OPEN

      Response for this request by knox :
      ==> Location: https://knox-server:8443/gateway/sandbox/webhdfs/v1/tmp/myfile?_=<my_access_token>

      So the Knox gateway response contains a redirection to the good dns (knox-server) but to the unPATed port (8443) it should be 443.

      Redirection should be like the first request :
      ==> Location : https://knox-server/gateway/sandbox/webhdfs/v1/tmp/myfile?_=<my_access_token>

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            kminder Kevin Minder
            Alexandre LINTE LINTE
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment