by baaldemon » Wed Jan 12, 2011 2:44 pm
HTTPS is supported in the application by default, meaning that it handles the writing of the urls based on what context its being accessed by (ie it keeps you in https if thats how you are accessing the server). Also the native android application is able to work under the https context.
This does not mean that SSL is enabled by default, but that is not up to the application itself, that depends on the webserver. The current stand alone install runs the application through a jetty webserver that is not configured to run ssl, however jetty can be configured to run ssl, however im not sure the feasibility of building this into the installer, nor do I believe its necessarily the way to go about it.
I would suggest for those of you who want ssl, and I would encourage its use, to install something like tomcat and run subsonic within it. You can follow the many guides out there to enable ssl through tomcat, its a couple command line utils and modifying a couple config files. Then its as simple as deploying a war file to the tomcat instance. Upgrading your install is as simple as deploying the new war file.
If you want ssl enabled it can be done fairly easily. Yes there are manual steps, but really if you are going to be running a web server you should be able to do it.