anybody
-
Joined: 17 Mar 2008
Posts: 90
|
 Posted: Mon Mar 17, 2008 12:37 pm Post subject: IP based virtual hosting? |
 |
|
Does abyss x2 support IP based virtual hosting.
I'm considering on buying abyss x2 and was looking up features in abyss on wikipedia.org. I was reading this about name based virtual hosting.
| Quote: | If the Domain Name System (DNS) is not properly functioning, it becomes much harder to access a virtually-hosted website. Ordinarily, in this case, the user could try and fall back to using the IP address to contact the system, as in http://12.37.56.78/. However, the web browser doesn't know what hostname to send when this happens, so the server will respond with a default website—often not the site the user expects. This workaround is not really useful for an average web user, but may be of some use to a site administrator while fixing DNS records.
A workaround in this case is to add the IP address and hostname to the client system's hosts file. At this point, accessing the server with the domain name should work again. However, users should be careful when doing this, as any changes to the true mapping between hostname and IP address will be overridden by the local setting.
Another issue with virtual hosting is the inability to host multiple secure websites running Secure Sockets Layer or SSL. Because the SSL handshake takes place before the expected hostname is sent to the server, the server doesn't know which certificate to present when the connection is made. One workaround is to run multiple web server programs, each listening to a different incoming port, which still allows the system to just use a single IP address. If running multiple web server programs is considered clumsy, a more efficient solution is to select TLS (TLS 1.1 or later, which enables name-based virtual hosting as of December 2006). Another option is to do IP aliasing, where a single computer listens on more than one IP address. |
Here is what wikipedia.org says about IP based virtual hosting.
| Quote: | In IP-based virtual hosting, each site (either a DNS hostname or a group of DNS hostnames that act the same) points to a unique IP address. The webserver is configured with multiple physical network interfaces, virtual network interfaces on the same physical interface or multiple IP addresses on one interface.
The webserver can obtain the address the TCP connection was intended for using a standard api and uses this to determine which website to serve. The client is not involved in this process and therefore (unlike with name based virtual hosting) there are no compatibility issues. |
|
|
