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

Zeppelinws fails with error 'Host does not match SNI'

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.0
    • Component/s: websockets
    • Labels:
      None

      Description

      Knox will fail to proxy ZeppelinWS service when zeppelin is SSL configured and has multiple SAN entries in its certificate.

      Issue is due to zeppelin trying to validate SNI against the request header received from Knox, which has 'Host: ' header with knox/proxy host.

      org.eclipse.jetty.http.BadMessageException: 400: Host does not match SNI
              at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:278)
              at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:207)
              at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:379)
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                smore Sandeep More
                Reporter:
                smore Sandeep More
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m