I have been trying this out recently, in part to look at service workers [1] I am using BaseX 9 betas for this. This has a newer jetty version. I have put a jetty.xml that is working for me as a gist [2]
You will need to change the keystore location [3] to something that points to your keystore. It is based on the jetty9 article [4]
/Andy
https://w3c.github.io/ServiceWorker/ https://gist.github.com/apb2006/b24e92f84c42838ec7ef7de2cf937835 https://gist.github.com/apb2006/b24e92f84c42838ec7ef7de2cf937835#file-jetty-... https://www.blackpepper.co.uk/what-we-think/blog/jetty-runner-https-xml-conf...
On 14 March 2018 at 20:59, Liam R. E. Quin liam@w3.org wrote:
On Wed, 2018-03-14 at 14:18 -0500, Giavanna J Richards wrote:
I'm trying to determine how to enable SSL communications with the BaseX server
I don't know if this helps, but I run BaseX listening only to "localhost" so that SSL isn't an issue (as a connection to localhost doesn't normally go over a network), and connect (on the same system) from PHP or Perl (!) or you can proxy via apache.
If BaseX is running on a different computer, you could also proxy on the system running BaseX e.g. with apache and .htaccess or the server conf & mod_rewrite. That way you'd use SSL to get to apache and then an in-memory connection from there to BaseX.
Liam
-- Liam Quin, W3C, http://www.w3.org/People/Quin/ Staff contact for Verifiable Claims WG, SVG WG, XQuery WG Improving Web Advertising: https://www.w3.org/community/web-adv/ Personal: awesome vintage art: http://www.fromoldbooks.org/