By default, ServerTokens is set to Full which sends information about the Operating System type and compiled-in modules. Setting the ServerTokens to Prod sends the product name only and is recommended as many hackers check information in the Server header when scanning for vulnerabilities. Non-CGI requests are still processed with the user and group specified in the User and Group directives.
Timeout defines, in seconds, the amount of time that the server waits for receipts and transmissions during communications. Timeout is set to seconds by default, which is appropriate for most situations. TypesConfig names the file which sets the default list of MIME type mappings file name extensions to content types.
When UseCanonicalName is set to off , the server instead uses the value used by the requesting client when referring to itself. The User directive sets the username of the server process and determines what files the server is allowed to access. UserDir is the subdirectory within each user's home directory where they should place personal HTML files which are served by the Web server. This directive is set to disable by default.
The VirtualHost container accepts most configuration directives. Configuration Directives in httpd. The httpd. The default configuration works for most situations; however, it is a good idea to become familiar some of the more important configuration options. If migrating from version 1. General Configuration Tips. Before editing httpd. Creating a backup makes it easier to recover from mistakes made while editing the configuration file.
If a mistake is made and the Web server does not work correctly, first review recently edited passages in httpd. The error log may not be easy to interpret, depending on your level of expertise.
However, the last entries in the error log should provide useful information. The following subsections contain a list of short descriptions for many of the directives included in httpd.
These descriptions are not exhaustive. Immediately after the AccessFileName directive, a set of Files tags apply access control to any file beginning with a.
These directives deny Web access to any. This directive enables CGIs outside of the cgi-bin to function in any directory on the server which has the ExecCGI option within the directories container. CacheEnable — Specifies whether the cache is a disk, memory, or file descriptor cache.
CacheRoot — Specifies the name of the directory containing cached files. CacheSize — Specifies how much space the cache can use in kilobytes. The default CacheSize is 5 KB. The following is a list of some of the other common cache-related directives. The default is 24 hours seconds. CacheLastModifiedFactor — Specifies the creation of an expiry expiration date for a document which did not come from its originating server with its own expiry set.
The default CacheLastModifiedFactor is set to 0. CacheDefaultExpire — Specifies the expiry time in hours for a document that was received using a protocol that does not support expiry times. The default is set to 1 hour seconds. NoProxy — Specifies a space-separated list of subnets, IP addresses, domains, or hosts whose content is not cached. This setting is most useful for Intranet sites. The default CustomLog format is the combined log file format, as illustrated here:. Under this configuration, any directory on the system which needs more permissive settings has to be explicitly given those settings.
In the default configuration, another Directory container is configured for the DocumentRoot which assigns less rigid parameters to the directory tree so that the Apache HTTP Server can access the files residing there.
The Directory container can be also be used to configure additional cgi-bin directories for server-side applications outside of the directory specified in the ScriptAlias directive refer to ScriptAlias for more information. Next, the AddHandler directive must be uncommented to identify files with the. Refer to AddHandler for instructions on setting AddHandler. For this to work, permissions for CGI scripts, and the entire path to the scripts, must be set to The default for DirectoryIndex is index.
The server tries to find either of these files and returns the first one it finds. If it does not find one of these files and Options Indexes is set for that directory, the server generates and returns a listing, in HTML format, of the subdirectories and files within the directory, unless the directory listing feature is turned off. It is used to serve more than half of all active websites. Although there are many viable web servers that will serve your content, it is helpful to understand how Apache works because of its ubiquity.
In this article, we will examine some general configuration files and options that can be controlled within them. If you do not already have Apache installed, you can do so now by issuing the following commands:. This is all that is necessary to have a working web server.
There are a number of plain text files and some sub-directories in this directory. These are some of the more useful locations to be familiar with:. As you can see, Apache configuration does not take place in a single monolithic file, but instead happens through a modular design where new files can be added and modified as needed. This file is divided into three main sections: configuration for the global Apache server process, configuration for the default server, and configuration of Virtual Hosts.
In Ubuntu and Debian, the majority of the file is for global definitions, and the configuration of the default server and virtual hosts is handled at the end, by using the "Include The "Include" directive allows Apache to read other configuration files into the current file at the location that the statement appears.
The result is that Apache dynamically generates an overarching configuration file on startup. If you scroll to the bottom of the file, there are a number of different "Include" statements. These load module definitions, the ports. By default, this parameter is set to "", which means that the server has a maximum of seconds to fulfill each request. This is probably too high for most set ups and can safely be dropped to something between 30 and 60 seconds.
This option, if set to "On", will allow each connection to remain open to handle multiple requests from the same client.
If this is set to "Off", each request will have to establish a new connection, which can result in significant overhead depending on your setup and traffic situation. This controls how many separate request each connection will handle before dying. Keeping this number high will allow Apache to serve content to each client more effectively. Setting this value to 0 will allow Apache to serve an unlimited amount of request for each connection. This setting specifies how long to wait for the next request after finishing the last one.
If the timeout threshold is reached, then the connection will die. This just means that the next time content is requested, the server will establish a new connection to handle the request for the content that make up the page the client is visiting.
You can cross-reference which section your Apache installation was compiled with by exiting into the terminal and typing:. As you can see, in this server, "prefork. Your installation may have multiple to choose from, but only one can be selected. The default Virtual Host declaration can be found in a file called "default" in the "sites-available" directory. However, there are some situations where having too many individual virtual host files that set the same cluster of configuration options for a group of hosts can cause confusion and increase the maintenance burden.
In these cases, a single file may be the best option for keeping Apache configured properly. This is the preferred organization for virtual host configuration in some distributions, including CentOS, Fedora, and Arch Linux. While you should check the default Apache configuration for your distribution, commonly there is a conf. If you want to combine a number of virtual host configuration files into a single file, create a vhosts.
The conf. Both configuration options are functionally equivalent, but offer easier administration in different scenarios. The configuration file organization that you choose depends on the needs of your particular deployment. You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on Friday, November 6, Let us know if this guide made it easy to get the answer you needed. Explore docs. Docs Home List Sections Tiles. To allow better organization, many operating systems and Apache distributions also read configuration files in the conf. This latter subdirectory contains config files for all available modules, while mods-enabled contains only a subset, namely the modules that should actually be enabled.
The symlinks are created using the a2enmod tool. If the mods-enabled mechanism is not available then you can paste configuration snippets into httpd.
What is this?
0コメント