Through this page, you can configure some of the options which affect global URL construction. These options include: Your server will use the name you give your server here as the central Uniform Resource Locator (URL) when users access your home page. An example URL is the URL for the home page of Netscape Communications, http://home.netscape.com/. The server name is built from our domain name, netscape.com, and the name of our server, home. Be sure to include your domain name as well as the machine name.

Your system administrator may have already set up a DNS alias for your server such as www.subdomain.dom. If this is the case, then you should use that alias here. If not, you should use the machine's name combined with your domain as the name.

For example, if your machine was named server, and you were part of the domain acme.com, you would use the server name server.acme.com. The machine your server runs on has a number of ports that the machine uses to differentiate requests using different protocols. Just as the standard Telnet port number is 23, the standard HTTP port number is 80, and the standard HTTPS port is 443. You can choose any port number from 1 to 65535 - but you should be careful which number you pick:

If you have any doubts at all about which port number you should use, you should probably use the standard port. At times it may be desirable for your workstation to answer to two URLs. For example, you may want to serve both http://www.a.com/ and http://www.b.com/ from one machine. Due to limitations in the HTTP protocol, this is difficult. There is one trick to do this, however, which involves causing your machine to think it must answer to more than one IP address. This trick only works on certain systems.

If you have already set up your system to listen to multiple IP addresses and want to use this feature, you must tell this installation of the server which IP address it belongs to.