You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2015/04/02 00:27:53 UTC
[jira] [Updated] (SOLR-7299) bin/solr.cmd doesn't use the jetty SSL
configuration
[ https://issues.apache.org/jira/browse/SOLR-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Rowe updated SOLR-7299:
-----------------------------
Attachment: SOLR-7299.patch
Patch against branch_5x that adds SSL handling to {{bin\solr.cmd}}. I successfully manually tested standalone and cloud starting, collection/core creation, admin UI access (including client auth), healthcheck (cloud only), and stopping in both SSL and non-SSL mode.
There also is a bug in {{-s}} (solr home) param handling in {{bin\solr.cmd}} that this patch fixes: a relative solr home dir is interpreted relative to {{%SOLR_SERVER_DIR%}} instead of relative to the current directory at script invocation.
Committing to branch_5x and lucene_solr_5_1 shortly.
> bin/solr.cmd doesn't use the jetty SSL configuration
> ----------------------------------------------------
>
> Key: SOLR-7299
> URL: https://issues.apache.org/jira/browse/SOLR-7299
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.0
> Reporter: Steve Rowe
> Fix For: 5.1
>
> Attachments: SOLR-7299.patch
>
>
> In SOLR-7020 I added an alternate jetty config file to use when in SSL mode, but I forgot to make the same changes in {{bin/solr.cmd}}.
--
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