[
https://issues.apache.org/jira/browse/SOLR-12341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh resolved SOLR-12341.
------------------------------
Resolution: Won't Fix
These days, the post command lives in bin/solr post, and as part of being part
of the SolrCLI suite of tools, it has SSL support! See the example in
test_ssl.bats file:
run solr post --solr-update-url https://localhost:${SOLR_PORT}/solr/test/update
${SOLR_TIP}/example/exampledocs/books.csv
If you aren't seeing this working in Main, please reopen this ticket!
> Allow bin/post to include command-line-specified arguments to Java
> ------------------------------------------------------------------
>
> Key: SOLR-12341
> URL: https://issues.apache.org/jira/browse/SOLR-12341
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 7.3
> Reporter: Christopher Schultz
> Priority: Minor
> Labels: patch
> Attachments: SOLR-post.patch
>
>
> When using a standalone (non-clustered, non-ZK'd) Solr instance, enabling TLS
> was a chore for a few reasons. One of them was that `bin/post` doesn't
> provide a way to specify the client's trust store.
> This is easy to remedy: add a parameter to the `java` invocation in the
> script to include options set in the shell.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
