[
https://issues.apache.org/jira/browse/SOLR-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261100#comment-15261100
]
ASF subversion and git services commented on SOLR-9040:
-------------------------------------------------------
Commit 9ab76a1e41d7019fd07b16a79a587653cf6d76a4 in lucene-solr's branch
refs/heads/master from [~hossman_luc...@fucit.org]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9ab76a1 ]
SOLR-9040 / SOLR-4509: Fix default SchemaRegistryProvider so javax.net.ssl.*
system properties are respected by default
> bin/solr SSL support for client->server communcation (as well as default SSL
> behavior in 'new HttpSolrClient(String)') 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, 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
> Further investigation indicates this is a general problem with HTTP based
> SolrClient initialization when standard {{javax.net.ssl.*}} sys properties
> are expected to be used for initializing the underlying HTTP client code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
