- SSL website bug.
Steps to reproduce.
- Create virtual server. g____.com
- Create 2 sub servers under that virtual server. In this case, both happen to be on subdomains. shop.g____.com and pm.g_____.com
- Enable SSL website in all 3 virtual server options / domains.
- Disable SSL website on top level virtual server in the list.
- In browser, go to https top level virtual server website.
It redirects to subserver htpps site.!! Should not do that. Should give a 404 or some error - ssl site not found.
- Disable SSL website on subservers. In browser, go to https subserver. It spills over into the next (unrelated account!) top-level virtual server's subservers!! In other words, the wrong SSL website shows in the browser.
Seems like the user interface settings, trigger Virtualmin code, which generate the apache settings, which have as a side effect, spillover logic for the SSL virtualservers which doesn't match the user interface settings, which are a simple on/off checkbox. Probably related to the default SSL host in some way, and/or the pattern matching rules that Apache uses to select the SSL virtual host to serve up to the browser.
Additional issue - Apache FAILS to START !! when SSL is enabled on top level virtual server AND SSL disabled on the subservers. Under the steps to reproduce from above. The workaround - so that Apache will at least start - is to disable SSL on the top level virtual server.