Error Document ………………………………………………………………………………………. ErrorDocument 404 /missing.html ………………………………………………………………………………………. When
Error Document ………………………………………………………………………………………. ErrorDocument 404 /missing.html ………………………………………………………………………………………. When a browser requests a document that’s not on the server, the server returns an error. You can create a custom error page with the ErrorDocument directive. Include ………………………………………………………………………………………. Include /usr/local/etc/apache/vhosts.conf ………………………………………………………………………………………. The httpd.conf file can include other files, a feature that can be useful when you have several subsystems maintained by different people. This can also be useful if you want to make your configuration easier to digest. For example, many add-on Apache modules have their own bits of configuration code. It’s simpler to give each model its own configuration file and include it than to pile it on the main httpd.conf file. Similarly, if you have a person whose job it is to maintain virtual hosts, you can create a virtual hosts file with permissions that allow that person (or group of people) to maintain it (see Chapter 
. Directory Configuration Apache has many nifty features, but it’s not a good idea to enable everything everywhere a bit of sloppy programming can result in your giving out too much information from your Web site, or even letting someone break in. Permissions to access Apache functions are set on a directory-by-directory basis. The configuration looks much like XML: You have a Directory label in angle brackets, a list of permissions and settings, and then a closing directory entry with a backslash. Any options or settings between the opening and closing Directory statements affect that directory. Here’s the basic format: ……………………………………………………………………………………….
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Unix Web Hosting services