656 Part V . Running Servers Access control (Free web servers)
656 Part V . Running Servers Access control files are useful for allowing users to change specific settings without having access to the server configuration files. The configuration directives permitted within an access configuration file are determined by the AllowOverride setting on the directory in which they are contained. Some directives do not make sense at that level and generally result in a server internal error message when trying to access the URI. The AllowOverride option is covered in detail at http://httpd.apache.org/docs/mod/core.html#allowoverride. Three directives commonly found in location blocks and access control files are DirectoryIndex, Options, and ErrorDocument: . DirectoryIndex tells Apache which file to load when the URI contains a directory but not a filename. This directive doesn t work in Files blocks. . Options is used to adjust how Apache handles files within a directory. The ExecCGI option tells Apache that files in that directory can be run as CGI scripts, and the Includes option tells Apache that server-side includes (SSI) are permitted. Also commonly used is the Indexes option, which tells Apache to generate a list of files if one of the filenames found in the DirectoryIndex setting is missing. An absolute list of options can be specified, or the list of options can be modified by adding + or - in front of an option name. See http://httpd.apache.org/docs/mod/core.html#options for more information. . ErrorDocument directives can be used to specify which file to send in the result of an error. The directive must specify an error code and the full URI for the error document. Possible error codes include 403 (access denied), 404 (file not found), and 500 (server internal error). More information about the ErrorDocument directive can be found at http://httpd.apache.org/ docs/mod/core.html#errordocument. Another common use for location blocks and access control files is to limit access to a resource. The Allow directive can be used to permit access to matching hosts, and the Deny directive can be used to forbid it. Both of these options can occur more than once within a block and are handled based on the Order setting. Setting Order to Deny,Allow permits access to any host that is not listed in a Deny directive. A setting of Allow,Deny denies access to any host not allowed in an Allow directive. Like most other options, the most specific Allow or Deny option for a host is used, meaning that you can Deny access to a range and Allow access to subsets of that range. By adding the Satisfy option and some additional parameters, you can add password authentication. For more information about access control, see http://httpd.apache.org/docs/mod/mod_access.html. Note
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.