[
https://issues.apache.org/jira/browse/KNOX-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195592#comment-17195592
]
ASF subversion and git services commented on KNOX-2453:
-------------------------------------------------------
Commit b518853eb4cbaa1e0b37cca7a66613def39694bc in knox's branch
refs/heads/master from Sandeep Moré
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=b518853 ]
KNOX-2453 Fix Host header handling in websockets (#374)
> Zeppelinws fails with error 'Host does not match SNI'
> -----------------------------------------------------
>
> Key: KNOX-2453
> URL: https://issues.apache.org/jira/browse/KNOX-2453
> Project: Apache Knox
> Issue Type: Bug
> Components: websockets
> Reporter: Sandeep More
> Assignee: Sandeep More
> Priority: Major
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.
> {code}
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)