Improve HTTPS usability in web server access to Flexshares
Migrated from: https://tracker.clearos.com/view.php?id=1285
Reported by: Peter Baldwin
HTTPS handling in Flexshare (and in general!) is non-intuitive at times.
-
Only one SSL certificate is permitted per IP, so hostname-based SSL is a bit misleading. Though https://flex1.example.com and https://flex2.example.com can co-exist, only one SSL certificate is permitted.
-
If a user disables SSL support, the hostname-based Flexshare (e.g. flex1.example.com) is removed. However, if other SSL Flexshares are enabled, the disabled https://flex1.example.com Flexshare will still resolve, but it will point to a different Flexshare. Confusing, but that's an HTTPS-ism that's hard to get around. Note: the path-based Flexshare (e.g. example.com/flexshare/flex1) remains, but it should be possible to remove the HTTPS path-based access.
.
Note 1:
Source Code Changelog
Moved stuff around to support both HTTP and HTTPS for web sites / web apps [tracker 0001285]
File Changes
Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=6400
U webconfig/apps/flexshare/trunk/libraries/Flexshare.php