As discussed with @jestabro both of us have not seen the adoption of the https virtual-host CLI option.
What it did?
- Create multiple webservers each listening on a different IP/Port (but in the same VRF)
- All webservers shared one common documentroot
- All webservers shared the same SSL certificates
- All webservers could have had individual allow-client configurations
- API could be enabled for a particular virtual-host but was always enabled on the default host
This configuration tried to provide a full webserver via the CLI but VyOS is a router and the Webserver is there for an API or to serve files for a local-ui.
Changes
- Remove support for virtual-hosts as it's an incomplete and thus mostly useless "thing"
- Migrate all allow-client statements to one top-level allow statement