[
https://issues.apache.org/jira/browse/SOLR-12639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613409#comment-16613409
]
Kevin Risden commented on SOLR-12639:
-------------------------------------
The problem with Kerberos and HTTP/2 is that HTTP/2 is multiplexed and Kerberos
typically requires multiple requests. This is typically a request -> 401
response -> challenge -> answer. Solr may not need to worry about this if Jetty
handles the fallback. If Kerberos auth is required though, the Solr server will
need to listen for both HTTP 1.1 and HTTP/2 I think.
Some references about how this may not work well with HTTP/2. The first link
describes the overall problem. The next is a message list about authentication
with HTTP/2. The last few are about browsers needing to fallback to HTTP 1.1.
*
[https://support.radware.com/app/answers/answer_view/a_id/19024/~/note-regarding-ntlm-with-http%2F2]
* [https://www.ietf.org/mail-archive/web/httpbisa/current/msg26809.html]
**
[https://www.ietf.org/archive/id/draft-montenegro-httpbis-multilegged-auth-01.txt]
*
[https://www.fxsitecompat.com/en-CA/docs/2017/ntlm-authentication-fails-in-certain-cases/]
** [https://bugs.chromium.org/p/chromium/issues/detail?id=713851]
** [https://bugzilla.mozilla.org/show_bug.cgi?format=default&id=1346392]
> Umbrella JIRA for adding support HTTP/2, jira/http2
> ---------------------------------------------------
>
> Key: SOLR-12639
> URL: https://issues.apache.org/jira/browse/SOLR-12639
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: http2
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
>
> This ticket will aim to replace/add support of http2 by using jetty HTTP
> client to Solr. All the works will be committed to jira/http2 branch. This
> branch will be served like a stepping stone between the master branch and
> Mark Miller starburst branch. I will try to keep jira/http2 as close as
> master as possible (this will make merging in the future easier). In the same
> time, changes in starburst branch will be split into smaller/testable parts
> then push it to jira/http2 branch.
> Anyone who interests at http2 for Solr can use jira/http2 branch but there is
> no backward-compatibility guarantee.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
