[KNOX-2453] Zeppelinws fails with error 'Host does not match SNI'

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: websockets
• Assignee: Sandeep More
• Reporter: Sandeep More
• Created: 11/Sep/20 14:14
• Updated: 14/Sep/20 17:51
• Resolved: 14/Sep/20 17:51

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)

Issue Links

• links to: GitHub Pull Request #374