[
https://issues.apache.org/jira/browse/SOLR-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258168#comment-15258168
]
Mark Miller commented on SOLR-9040:
-----------------------------------
bq. why is it a distinct class with distinct setters in HttpClientUtil, instead
of being part of SolrHttpClientBuilder ?
I probably felt that the builder for the httpclient and setting this for the
pooling connection manager where somewhat distinct. I'm sure you could move it
to the builder. As it is, you could have some code somewhere that configures
the httpclient builder and then some code that turns on SSL somewhere else, and
the SSL code would not have to rebuild the same httpclient builder and add the
schema registry so that it could change schema registry and not any other
httpclient builder settings.
> bin/solr SSL support for client->server communcation broken on master
> ---------------------------------------------------------------------
>
> Key: SOLR-9040
> URL: https://issues.apache.org/jira/browse/SOLR-9040
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Hoss Man
> Attachments: SOLR-9040.patch
>
>
> Working on SOLR-9028 lead me to realize that {{bin/solr}} actions which
> require communicating with solr over HTTP are broken on master when SSL is
> enabled. My testing suggests that this doesn't affect branch 6x or 6.0.
> (Long) detailed steps to reproduce to follow in first comment
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
