[
https://issues.apache.org/jira/browse/SOLR-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249139#comment-17249139
]
Timothy Potter commented on SOLR-15046:
---------------------------------------
This problem was surfaced by the changes introduced in SOLR-12182, but the bug
is actually in the {{bin/solr}} script.
> bin/solr check to see if solr.jetty.https.port should be set always returns
> true
> --------------------------------------------------------------------------------
>
> Key: SOLR-15046
> URL: https://issues.apache.org/jira/browse/SOLR-15046
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: 8.8
> Reporter: Timothy Potter
> Assignee: Timothy Potter
> Priority: Minor
>
> This always returns {{true}} on Mac OS X (not sure about Linux):
> {code}
> if [ "$SOLR_SSL_ENABLED" ]; then
> # If using SSL and solr.jetty.https.port not set explicitly, use the
> jetty.port
> SSL_PORT_PROP="-Dsolr.jetty.https.port=$SOLR_PORT"
> SOLR_OPTS+=($SOLR_SSL_OPTS "$SSL_PORT_PROP")
> fi
> {code}
> On master, we do {{ if [ "$SOLR_SSL_ENABLED" == "true" ]; then}}
> The problem is that ZkContainer (when zkRun enabled) looks to see if
> {{solr.jetty.https.port}} is set, and if so, then it assumes TLS is enabled.
> So this little BASH bug causes Solr's HttpShardHandler to connect via https.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
