This object is in archive! 
Implementation for a vhost for unbound traffic
Open Discussion
At the moment if I enter our server's https IP address into the browser, our only account's website appears since they are the only one who use https for their website. It means that when you go to https://IP it goes to the apache configuration and see if anything matches that exactly.
If it doesn't, it then defaults to using the first vhost of that nature(generally ssl/non-ssl).
It is not a desirable solution and the implemenation of a vhost for all unbound traffic would solve this problem.
Replies have been locked on this page!