[
https://issues.apache.org/jira/browse/SOLR-7020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-7020:
-----------------------------
Attachment: SOLR-7020.patch
Patch against branch_5x implementing the idea.
I chose the name {{jetty-https-ssl.xml}} for the alternative jetty config file,
to avoid collision with the Jetty 9 changes on trunk (SOLR-4839) that will
eventually be backported to branch_5x. (Trunk has files named
{{jetty-ssl.xml}} and {{jetty-https.xml}}.)
{{bin/solr start}} will choose to use {{jetty-https-ssl.xml}} instead of the
default jetty config file when {{$SOLR_SSL_OPTS}} is defined - just like
already happens when it chooses the url scheme used to address running
instances - so no explicit options are required to choose the SSL jetty config
file.
> Stop requiring jetty.xml edits to enable bin/solr to start in SSL mode
> ----------------------------------------------------------------------
>
> Key: SOLR-7020
> URL: https://issues.apache.org/jira/browse/SOLR-7020
> Project: Solr
> Issue Type: Task
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Minor
> Fix For: 5.0, 5.1
>
> Attachments: SOLR-7020.patch
>
>
> Right now we tell people to edit {{server/etc/jetty.xml}} to enable SSL:
> comment out the non-SSL connector(s), uncomment the SSL connector.
> Jetty can be started using alternate configuration files - see
> https://wiki.eclipse.org/Jetty/Reference/jetty.xml_usage - we should make use
> of this capability and provide an SSL-enabled alternative to {{jetty.xml}}
> that {{bin/solr start}} can use when SSL is enabled. That way no manual
> edits to {{jetty.xml}} will be required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
