You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2014/03/18 05:07:43 UTC
[jira] [Reopened] (SOLR-5866) UpdateShardHandler needs to use the
system default scheme registry to properly handle https via javax.net.ssl.*
properties
[ https://issues.apache.org/jira/browse/SOLR-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar reopened SOLR-5866:
-----------------------------------------
I'm going to backport this to 4.7.1
> UpdateShardHandler needs to use the system default scheme registry to properly handle https via javax.net.ssl.* properties
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-5866
> URL: https://issues.apache.org/jira/browse/SOLR-5866
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.7
> Reporter: Steve Davids
> Assignee: Shalin Shekhar Mangar
> Fix For: 4.8, 5.0, 4.7.1
>
> Attachments: SOLR-5866.patch
>
>
> The UpdateShardHandler configures it's own PoolingClientConnectionManager which *doesn't* use the system default scheme registry factory which interrogates the javax.net.ssl.* system properties to wire up the https scheme into HttpClient. To ease configuration the system default registry should be used.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org