[
https://issues.apache.org/jira/browse/SOLR-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-4394:
---------------------------
Attachment: SOLR-4394.patch
revised patch...
* fixes nocommit by randomizing when we use SSL (50%)
* only randomize SSL if none of the ssl related properties have already been
explicitly set
* improve cleanup of properties that get set when randomizing ssl
* if the random logic decides to use ssl, then 50% of the time randomly require
client auth
The client auth changes make this patch dependent on the changes in SOLR-4451
(using SystemDefaultHttpClient so solrj's httpclient pays attention to the
javax.\* props)
there is still a TODO about promoting the SSL randomization code up into
SolrJettyTestBase, but i think it would be best to commit as is and let it soak
for a few days and see if anyone notices problems running tests before
randomizing SSL across all jetty related tests.
> Add SSL tests and example configs
> ---------------------------------
>
> Key: SOLR-4394
> URL: https://issues.apache.org/jira/browse/SOLR-4394
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 4.2
>
> Attachments: SOLR-4394.patch, SOLR-4394.patch
>
>
> We should provide some examples of running Solr+Jetty with SSL enabled, and
> have some basic tests using jetty over SSL
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
