You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2016/04/28 00:44:12 UTC
[jira] [Resolved] (SOLR-9040) bin/solr SSL support for
client->server communcation (as well as default SSL behavior in 'new
HttpSolrClient(String)') broken on master
[ https://issues.apache.org/jira/browse/SOLR-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-9040.
----------------------------
Resolution: Fixed
Fix Version/s: master
> 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
> Fix For: master
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org