The Document Root must point to the directory that holds the web; Directory Indexes can specify a list of files that act as special index files, for instance: index.html,index.php.
A simple virtual server can handle an unlimited number of domain names. In fact, it is even able to configure a virtual server to handle all the domains that match with a list of custom wildcats. For example:
www.alobbs.com
*.example.com
If the domain name list is empty, the domain alias will be used internally as its only entry.
This is the most important part of the virtual server configuration. This section sets the rules about how the virtual server will reply to the client requests.
When a request is going to be replied by a virtual server, it needs to make a decision on what it should do. For instance, whether it ought to execute a CGI, read a static file or relay the request on an application server. That decision will be based on the rules defined by this list.
The virtual server will try to match the request will all the rules from highest to lowest priority until an entry matches.
It is possible to customize how the server reports errors. Depending on the error handler it will generate different error responses.
The default handler replies as you expect a server to reply, so most probably you will not need to change it.
However, there is another error handler that allows you to set a custom redirection for each different error code; in that way you can show your own error messages.
By default the virtual server does not log the server transactions, nor the error messages. In this section you have to specify the format that the server should use when writing accesses and errors and where it should store them.
The most popular choice is Apache Compatible format using a single file for the access log and the error log.
This section allows you to configure the required files to enable the TLS/SSL support for a certain virtual server.
A Certificate, Certificate key and CA List files are needed in order to allow the server to activate the secure connections (https) engine.