[
https://issues.apache.org/jira/browse/SOLR-18055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-18055.
---------------------------------
Fix Version/s: 10.1
Resolution: Fixed
Thanks for contributing Vishnu!
> Use SOLR_SSL_ENABLED to auto-set urlScheme appropriately
> --------------------------------------------------------
>
> Key: SOLR-18055
> URL: https://issues.apache.org/jira/browse/SOLR-18055
> Project: Solr
> Issue Type: Improvement
> Components: security
> Reporter: David Smiley
> Priority: Major
> Labels: newdev, pull-request-available
> Fix For: 10.1
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> A user uses SOLR_SSL_ENABLED to enable https / SSL. It ought to be enough
> but today it isn't. For standalone mode, the solr.xml
> httpShardHandlerFactory has a urlScheme to manually set. I propose it need
> not; that component can examine solr.ssl.enabled prop to choose between http
> and https as a default. For SolrCloud, ZkStateReader.getBaseUrlForNodeName
> can do similarly, as the default if the urlScheme cluster property isn't set.
> CloudSolrClient can do the same if someone sets the system property. Thus a
> SolrCloud user need not feel compelled to set the urlScheme in a cluster
> property, which is an annoying step. That might eventually be deprecated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
