Our servers use both Pound (www.apsis.ch/pound) and F5 (www.f5.com/products/big-ip) for SSL validation, load balancing, failover, and reverse proxying. That is, we do use Apache for SSL. This is a fairly common configuration for all but the smallest of business applications.
I have made a post about this recently in the forums, but have not received a response yet. And, on second thought, I feel that this really must be a bug since the very technical nature of SSL is that it must be handled before any virtual hosting issues (http://httpd.apache.org/docs/2.0/vhosts/name-based.html). Because SSL must be handled before name-based virtual hosting considerations, it is the case that any number of SSL handlers can do this separable task. The SSL handlers include handlers such as Pound, F5, Squid, Apache, and others.
I hope you see the above as an indication that Virtualmin should not make the assumption that SSL validation is provided by Apache and that features such as Administrator's Notes and Analytics Tracking that have a prerequisite that SSL be enabled take this into consideration.
I've marked the severity High since there is no workaround for this problem. I don't know how difficult the fix would be for this and I expect that that will reflected in your Priority evaluation. Nonetheless, I do hope that you can consider this issue for some implementation not too far off.
References:
http://www.virtualmin.com/forums/help-home-for-newbies/ssl-provided-by-o...
Comments
-