How virtual directories work

In a typical URL, such as http://server:82/application/dir1/dir2/page.php, server represents the name of the server. The networking infrastructure resolves this name to locate the specific server computer. The port number (82) identifies the connection on that server, and the remainder of the URL provides a pathname to the specific page. Once the server is contacted by the browser, that pathname ("/application/dir1/dir2/page.php") is resolved by the server to identify the specific page to be processed and returned.

For static sites and pages, all that is necessary is for the server to open the file and send its contents to the browser. For dynamic sites and pages, there is more complicated processing that may require specific libraries and setup files to be installed for that specific site. JSP sites require a WEB-INF folder to be associated with a site. It contains Java code that is available to Web pages in the site. PHP and ASP can have special code or initialization information associated with a site (usually called a Web application). The first segment of the server pathname (application in this example) usually identifies the Web application. This first segment, also called a virtual directory or alias, can also be mapped to a specific folder on the server. This allows Web sites on the server to be located in any folder on the server's file system.

GoLive ASP and PHP sites do not require any special server Web application or virtual directory setup. The site can be located anywhere in the server's file structure. A properly setup ASP or PHP environment is required.

GoLive JSP sites follow the JSP conventions of requiring a WEB-INF folder with the GoLive Java libraries and setup files present. As part of creating a site, GoLive creates the WEB-INF folder for you. If your own site has been set up, you don't need to use the WEB-INF folder that GoLive creates, but you will need to place the libraries into the WEB-INF folder that you are using.