[
https://issues.apache.org/jira/browse/SOLR-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692593#comment-17692593
]
ASF subversion and git services commented on SOLR-16669:
--------------------------------------------------------
Commit 8130dc5924e6a0b3366e29e16db9c4cb71e586d5 in solr's branch
refs/heads/branch_9x from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=8130dc5924e ]
SOLR-16669: Fix default checkPeerName in Http2SolrClient (#1367)
(cherry picked from commit b070b5c19159962f77017901a0fcf03afac01a66)
> Http2SolrClient defaults checkPeerName incorrectly
> --------------------------------------------------
>
> Key: SOLR-16669
> URL: https://issues.apache.org/jira/browse/SOLR-16669
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: http2, SolrJ
> Reporter: Houston Putman
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> While I was going through the HTTP2ClientCode I realized that the \{{
> solr.ssl.checkPeerName }} option defaults to false if the system property is
> not provided. Instead we want it to default to true, which the documentation
> and the code both say is the functionality.
> Fixing this in a minor version would be back-compat breaking, though it would
> be adhering to the provided documentation. So I'm not sure whether we want
> this in 9x or just 10.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
