We need to rethink the way that the Fileserver UI works 

Now that Chrome auto redirects to https by default, we may need to rethink how we do things.

Currently we provide a "landing page" (aka tkl-webcp) via http and WebDAV-CGI (or webDAV) via 443.

I propose that we consider changing the webDAV/WebDAV-CGI access via a subdirectory? Or perhaps just via alternate port?

Note that currently Jellyfin uses port 12322 for HTTPS access.