Apache2 httpd.conf Configuration (i)

Source: Internet
Author: User
Tags md5 digest parent directory sendfile syslog system log

Excerpt from: http://jafy00.blog.51cto.com/2594646/501373

Common Configuration Instruction description

1. ServerRoot: The base directory of the server, in general it will contain conf/and logs/subdirectories, and the relative path of other profiles is based on this directory. The default is the installation directory, and no changes are required.

Syntax: Serverrootdirectory-path

such as: ServerRoot "/usr/local/apache-2.2.6"

Note that the path in this directive is not added at the end.

2. Listen: Specifies the IP and port on which the server listens. By default, Apache listens on all IP addresses. Listen is an instruction that must be set after Apache2.0, and if this instruction is not found in the configuration file, the server will

Failed to start.

Syntax: listen[ip-address:]portnumber [Protocol]

The listen instruction specifies that the server listens for access requests on that port or combination of addresses and ports. If you specify only one port, the server listens to the port on all addresses. If you specify a combination of addresses and ports, the server refers to the

Listens on the specified port of the fixed address. Optional Protocol parameters are not required in most cases, and if this parameter is not specified, the default HTTPS protocol is used for port 443 and the HTTP protocol is used for other ports.

Multiple listen directives can be used to specify multiple different listening ports and/or combination of address ports.

The default is: Listen 80

If you want the server to accept requests on ports 80 and 8080, you can set this:

Listen 80

Listen 8080

If you have the server accept the request on a combination of two identified address ports, you can set this:



If you use the IPV6 address, you must enclose the IPV6 address in square brackets:


3. LoadModule: Loading the specific DSO module. Apache defaults to storing the compiled DSO module in the dynamic loading module directory shown in the 4.1 Directory structure section.

Syntax: LoadModule modulefilename

such as: Loadmodulerewrite_module modules/mod_rewrite.so

If filename uses a relative path, the path is relative to the path indicated by ServerRoot.

The Apache configuration file loads all the compiled DSO modules by default, the author recommends loading only the following modules: Authn_file, Authn_default, Authz_host, Authz_user, Authz_default, Auth_basic, Dir, alias

, filter, speling, Log_config, env, Vhost_alias, Setenvif, mime, negotiation, rewrite, deflate, expires, headers, cache, File-cache, Disk-cache, Mem-cache

4. User: Sets the users of the child processes that actually provide the service. In order to use this directive, the server must be started and initialized as root. If you start the server as a non-root, the subprocess will not be able to switch to the unprivileged user and

Continue to run as the original user who started the server. If you do start the server as root, the parent process will still run as root.

The user who is running the subprocess must be a user without privileges to ensure that the child process does not have access to files that are not known to the outside world, and that the user does not have permission to execute programs that should not be executed by the outside world.

。 It is highly recommended that you create a separate user and group specifically for the Apache subprocess. Some administrators use nobody users, but this does not always meet the requirements because other programs may also be using the user.

Example: User daemon

5. Group: Sets the user group at runtime of the Apache child process that provides the service. In order to use this instruction, Apache must be initialized with root, otherwise it will fail when the user group is switched, and continue to run with the user group initialized at startup

Example: Group daemon

6. ServerAdmin: Sets the administrator e-mail address that is included in all error messages returned to the client.

Syntax: serveradminemail-address| Url

If httpd cannot recognize the supplied parameter as a URL, it assumes it is a email-address and uses mailto in a hyperlink: the back. It is recommended to use an email address because many CGI scripts do. If you

If you do want to use a URL, be sure to point to a server that you can control, or the user will not be able to make sure you get in touch with you.

7. ServerName: Set up the server to identify its own host name and port number.

Syntax: servername[scheme://]fully-qualified-domain-name[:p ORT]

The optional ' scheme://' prefix is available only in later versions of 2.2.3, and can be used to properly detect the normalized server URL after the agent or offline device.

When servername is not specified, the server attempts to reverse query the IP address to infer the host name. If you do not specify a port number in ServerName, the server uses the port that accepts the request.

To enhance reliability and predictability, it is recommended that you explicitly specify a host name and port number using ServerName.

If you are using a domain-based virtual host, the ServerName in <VirtualHost> will be to match this virtual host, the hostname that must appear in the "Host:" Request header.

8. DocumentRoot: Sets the Web document root directory.

Syntax: Documentrootdirectory-path

Without instructions such as Alias, the server appends the URL in the request to the DocumentRoot to form the path to the document.

If Directory-path is not an absolute path, it is assumed to be a path relative to the ServerRoot.

The last "/" should not be included when specifying DocumentRoot.

9. <Directory>:<Directory> and </Directory> are used to encapsulate a set of instructions that take effect only on a directory and its subdirectories.

Grammar:<directorydirectory-path> ... </Directory>

Directory-path can be a full path to a directory or a wildcard string that contains a unixshell matching syntax. In the wildcard string, "?" Matches any single character, and "*" matches any sequence of characters. can also make

Use ' [] ' to determine the range of characters. You can also use regular expressions after the "~" character.

If more than one (non-regular expression) <Directory> configuration segment conforms to the directory containing the document (or its parent directory), the instruction is applied with a short directory precedence rule and contains instructions in the. htaccess file.

Regular expressions are considered after all normal configuration segments. All regular expressions are applied according to the order in which they appear in the configuration file.

<Directory> directives cannot be nested or appear in <Limit> or <LimitExcept> configuration segments.

<FILES>: Provides file-based access control, similar to <Directory> and <Location> directives.

Grammar:<filesfilename> ... </Files>

The filename argument should be a filename or a string containing a wildcard character, where "?" Matches any single character, and "*" matches any string sequence. You can use regular expressions after the "~" character.

The directives defined in this configuration segment will act on objects whose base name (not the full path) matches the specified file name. <Files> sections are processed according to the order in which they appear in the configuration file: in <Directory> and. htaccess

After the file is processed, but before the <Location> section. <Files> can be embedded in the <Directory> section to limit the range of file systems they function, and can also be used in. htaccess files to allow users to control them at the file level

Access to their own files.

<ifmodule>: Encapsulates an instruction that determines whether or not the specified module is enabled, depending on whether it is active or not.

Grammar: <ifmodule[!] Module-file|module-identifier> ... </IfModule>

Module-file refers to the file name, such as MOD_REWRITE.C, when the module is compiled.

Module-identifier refers to the identifier of a module, such as Mod_rewrite.

Instructions in the <IfModule> configuration section are processed only when the test results are true, otherwise all instructions will be ignored.

Options: Control which server features are used in a particular directory

Syntax: Options [+|-]option[[+|-]option] ...

Option can be none, no additional features are enabled, or one or more of the following options:

All except MultiViews, this is the default setting.

EXECCGI allows CGI scripts to be executed using mod_cgi.

The FollowSymLinks server allows symbolic connections to be used in this directory, and is ignored if this configuration is in the <Location> configuration section.

Includes allows server-side inclusion with Mod_include.

IncludesNOEXEC allows server-side inclusion, but disables "#execcmd" and "#exec CGI", but can still use "#include virtual" virtual CGI scripts from the Scriptalias directory.

Indexes if a URL that maps to a directory is requested and there is no directoryindex (for example, index.html) in this directory, the server returns a formatted list of directories generated by Mod_autoindex.

MultiViews allows the use of mod_negotiation to provide content negotiation "more attention to the graph" (multiviews).

The SymLinksIfOwnerMatch server uses a symbolic connection only if it has the same UID as the owner of its destination directory or file. If this configuration appears in the <Location> configuration section, it will be ignored.

In general, if a directory is set up more than once, the most special one is fully accepted (others are ignored), and the settings for each option are not fused. However, if all the options that are available for the options directive

The "+" or "-" symbol is added to the front, and this option is merged. All options preceded with the "+" number will force the override of the current option setting, and all previously available options for the "-" sign will be forced to be removed from the current option settings.

AllowOverride: Determines the type of instruction that is allowed to exist in a. htaccess file.

Syntax: allowoverrideall| None|directive-type [Directive-type] ...

If this instruction is set to none, the. htaccess file is completely ignored. In fact, the server does not read. htaccess files at all.

When this directive is set to all, all directives with the ". htaccess" Scope are allowed to appear in the. htaccess file.

Directive-type can be one of the following groups of instructions:

Authconfig allows the use of instructions related to authentication authorization

FileInfo allows you to use instructions that control document types, instructions for controlling document metadata, instructions in mod_rewrite, and action instructions in Mod_actions

Indexes allows you to use instructions that control the index of a directory

Limit allows you to use commands that control host access

Options[=option,...] Allows you to use instructions that control the specified directory functionality (options and Xbithack). You can attach a comma-delimited (space-free) options list after the equal sign to control the Allow options directive

which options to use.

AllowOverride is valid only in <Directory> configuration segments that do not contain regular expressions. Invalid in <location>, <directorymatch>, <Files> configuration section.

Order: Controls the sequence in which the default access state and allow and deny directives take effect.

Ordering range is one of several examples:

The deny,allow deny instruction is evaluated before the Allow instruction. All access is allowed by default. Any client that does not match the deny directive or matches the allow instruction is allowed access.

The Allow,deny Allow instruction is evaluated before the Deny instruction. All access is denied by default. Any client that does not match the Allow directive or matches the deny instruction will be prevented from accessing it.

Mutual-failure only hosts that appear in the Allow list and do not appear in the Deny list are allowed access. This order has the same effect as "Orderallow,deny" and is not in favor of use.

Keywords can only be separated by commas, they cannot have spaces between them, and in all cases each allow and DENY instruction statement is evaluated.

Allow: Controls which hosts can access the server's area. You can control the client request characteristics that are captured in the host name, IP address, IP address range, or other environment variable.

Syntax: Allow fromall|host|env=env-variable [host|env=env-variable] ...

The first parameter of this instruction is always "from", and subsequent arguments can have three different forms: if you specify "Allow from", then all hosts are allowed access, configured with the following deny and order directives; to allow only specific primary

Machine or main cluster access server, host can be specified in any of the following formats: A (partial) domain name, complete IP address, part of the IP address, network/mask, network/nnn classless Inter-domain routing specifications; the third parameter format allows

Access to the server is specified by an extension of the environment variable specifying "Allowfrom env=env-variable" and access is allowed if the environment variable env-variable exists, using the instructions provided by the MOD_SETENVIF server

A flexible approach based on client requests provides the ability to set environment variables. Therefore, this instruction can be used to allow access based on like user-agent (browser type), Referer, or other HTTP request header fields.

Deny: This zone controls which hosts are blocked from accessing the server. You can control the client request characteristics that are captured in the host name, IP address, IP address range, or other environment variable.

Syntax: Deny from all|host|env=env-variable[host|env=env-variable] ...

The parameter settings for this directive are exactly the same as the Allow directives.

DirectoryIndex: A list of resources to look for when a client requests a directory.

Syntax: Directoryindexlocal-url [Local-url] ...

Local-url (% decoded) is a URL (usually a file in that directory) relative to the requested directory's document. Multiple URLs can be specified, and the server will return the first one found, for example:

DirectoryIndex index.htmlindex.php

ErrorLog: Specifies the file that logs the error log when the server encounters an error.

Grammar: errorlogfile-path|syslog[:facility]

If File-path is not an absolute path that begins with a slash (/), it is considered a relative path relative to the ServerRoot; if File-path is a pipe symbol (|) Begins, a command is assigned to it to handle the

Error logs, such as ErrorLog "|/usr/local/sbin/cronolog/var/log/httpd/%w/errors_log".

If supported by the system, using the "syslog" alternative filename will record the log through SYSLOGD (8). The default will be to use the system log mechanism LOCAL7, but you can override this setting with the "syslog:facility" syntax, where facility

is the value of any one of the names recorded in Syslog (1).

LogLevel: The level of detail used to adjust the information recorded in the error log.

Grammar: LogLevel level

You can select the following level, sorted by importance in descending order:

Emerg Emergency (System not available)

Alert must take immediate action

Crit Fatal condition

Error condition

Warn warning situation

Notice General Important situation

Info General Information

Debug Debug Information

When a level is specified, information that is higher than it for all levels is also logged. For example, specifying loglevel info, all notice and warn levels of information are also recorded. It is recommended to use at least the crit level.

When the error log is a separate official file, notice-level messages are always recorded and cannot be blocked. However, there is no such problem when logging with syslog.

Logformat: Defines the record format for accessing the log.

Syntax: Logformatformat|nickname [Nickname]

Logformat directives can be used in one of two definition formats.

In the first format, the instruction takes only one parameter to define the log format for subsequent transferlog directives. It can also use nickname to refer to a previous Logformat-defined log format in the following ways.

The second defines the format of the Logformat directive by linking a direct format to a nickname. In this way, in subsequent logformat or customlog instructions, you do not have to repeat the entire lengthy format string repeatedly. Define Alias

The logformat instruction is only used to define a nickname without doing anything else, that is, it simply defines the alias, it does not actually apply the alias, nor does it set it to the default format. Therefore, it does not

will affect subsequent transferlog directives. In addition, Logformat cannot use an alias to define another alias. Nickname cannot contain a percent semicolon (%).

For formatting the format, see the Custom Log Format section in the Apache2.2 official documentation.

Customlog: Set the file name and format for the log.

Syntax: Customlog file|pipeformat|nickname [env=[!] Environment-variable]

The first parameter specifies the location of the log record, which can be set in the following two ways:

File's log file name relative to ServerRoot.
Pipe pipe character "|" followed by a handler path that treats the log output as a standard input.

The second parameter specifies the content to write to the log file. It can be defined either by the nickname defined by the previous Logformat directive, or by the rules described in the Custom Log Format section of the Apache2.2 Official document.

The format string.

The third parameter is optional, which determines whether a particular request is logged, depending on whether the specific environment variable on the server is set. If this particular environment variable is set (or, in the case of "env=!name"), it is not

setting), the request will be logged. You can use the mod_setenvif and/or Mod_rewrite modules to set environment variables for each request.

Transferlog: Specifies the location of the log file.

Syntax: Transferlogfile|pipe

This directive has exactly the same parameters and functions as the customlog instruction, except that it does not allow direct definition of log format or logging according to conditions. In practice, the format of the log is specified by the most recent non-alias-defined logformat directive

。 If no log format is defined, the common log format is used.

Alias: Map URLs to specific areas of the file system.

Syntax: Alias url-pathfile-path|directory-path

The alias directive enables a document to be stored in a local file system other than DocumentRoot. URLs that begin with the (% decoded) Url-path path can be mapped to local files that begin with Directory-path.

If you create an alias for a directory other than DocumentRoot, you may need to explicitly set access to the target directory through the <Directory> section.

21.ScriptAlias: Map a URL to a file system and view it as a CGI script directory.

Syntax: Scriptalias url-pathfile-path|directory-path

The scriptalias instruction behaves the same as the alias directive, but it also indicates that the directory contains CGI scripts that should be handled by the Cgi-script processor. URLs that begin with Url-path (% decoded) are mapped to the second argument

A script in a local file system that has a full path name.

Scriptsock: Sets the socket filename prefix that is used to communicate with the CGI daemon (followed by attaching the parent process PID to the complete file name) in Apache, which is running in line program MPM (worker). This socket will be used to start the Apache suit

The parent process user right (usually root) of the service opens. In order to maintain security with CGI script communication, it is important that other users not be allowed to have permission to write to the directory in which the socket resides.

DefaultType: The default MIME content type that is sent when the server cannot determine the content type by another method.

Syntax: Defaulttypemime-type

Default: Defaulttypetext/plain

AddType: Establishes a mapping relationship between a given file name extension and a specific content type.

Syntax: AddType mime-typeextension [extension] ...

Mime-type indicates the media type of the file containing the extension extension. This mapping relationship is added on all valid mapping relationships and overwrites all the same extension extension mappings.

The extension parameter is not case-sensitive and can be brought with or without a leading point.

ErrorDocument: Instructions What kind of response the server will give the client when it encounters an error.

Syntax: Errordocumenterror-code document

Error code returned by the Error-code server

The document can be preceded by a slash (/) to indicate a local URL (relative to documentroot) or a complete URL that can be interpreted by the client. In addition, you can provide a message that can be displayed by the browser. Like what:


ErrorDocument 404/errors/bad_urls.html

ErrorDocument 403 "Sorrycan ' t allow you in Access today"

Enablemmap: Indicates whether the httpd can use a memory map if it needs to read the contents of a file in the delivery.

Syntax: Enablemmap on| Off

When processing a request to access the data in a file, for example, when delivering a file that uses Mod_include for server-side analysis, Apache uses the memory map by default if the operating system supports it.

This memory mapping can sometimes improve performance, but in some cases you may need to disable memory mappings to avoid some operating system problems:

On some multiprocessor systems, memory mapping reduces the performance of some httpd;

If a file has been mapped in memory on DocumentRoot that is mounted on NFS, deleting or truncating the file can cause httpd to crash due to a segmented failure.

You should use the following command to disable memory mapping during server configuration that may encounter these problems:

Enablemmap off

For folders that Mount NFS, you can specify the disable memory mappings separately in the <directory> section:

<directory "/path-to-nfs-files" >
Enablemmap off

Enablesendfile: Controls whether httpd can use the Sendfile support of the operating system kernel to send files to the client.

By default, when processing a request does not require access to the data inside the file (such as sending a static file content), if the operating system supports Apache will use Sendfile to send the contents of the file directly to the client without reading

Fetch the file.

This sendfile mechanism avoids separate read and write operations and buffer allocations, but on some platforms or some file systems, it is best to ban this feature to avoid some problems:

Some platforms may have defective sendfile support that is not detected by the compilation system, especially if the binaries that are compiled on other platforms are run on the currently defective platform for sendfile support;

When IPV6 is enabled on Linux, using Sendfile will trigger TCP checksum uninstall bugs on some network adapters;

When Linux is running on an Itanium processor, Sendfile may not be able to handle files larger than 2GB.

For a documentroot (for example, NFS or SMB) that mounts NFS file systems over the network, the kernel may not be able to reliably service network files through its own buffers.

If the above situation arises, you should disable Sendfile:

Enablesendfile off

For NFS or SMB, you can specify the Disable in <directory> section individually:

<directory "/path-to-nfs-files" >
Enablesendfile off

Include: Contains additional configuration files in the server configuration file.

Syntax: Includefile-path|directory-path

The wildcard character of the shell style (Fnmatch ()) can be used to include multiple files at once in alphabetical order. In addition, if the include points to a directory instead of a file, Apache reads all the files in the directory and its subdirectories, and

These files are parsed in alphabetical order as a configuration file. This is not recommended, however, because occasional temporary files are generated in this directory, causing httpd to fail to start.

The path to the file can be a complete absolute path (beginning with a slash), or relative to the ServerRoot directory.

29. Set dynamically loaded DSO module

#如果需要提供基于文本文件的认证, load this module, or comment out

LoadModule authn_file_modulemodules/mod_authn_file.so

#如果需要提供基于DBM文件的认证, load this module, or comment out

#LoadModule authn_dbm_modulemodules/mod_authn_dbm.so

#如果需要提供匿名用户认证, load this module, or comment out

#LoadModule authn_anon_modulemodules/mod_authn_anon.so

#如果需要提供基于SQL数据库的认证, load this module, or comment out

#LoadModule authn_dbd_modulemodules/mod_authn_dbd.so

#如果需要在未正确配置认证模块的情况下简单拒绝一切认证信息, load this module, or comment out

Loadmoduleauthn_default_module modules/mod_authn_default.so

#此模块提供基于主机名, IP address, request characteristics of access control, Allow, deny instruction required, recommended loading.

LoadModule authz_host_modulemodules/mod_authz_host.so

#如果需要使用纯文本文件为组提供授权支持, load this module, or comment out

#LoadModuleauthz_groupfile_module modules/mod_authz_groupfile.so

#如果需要提供基于每个用户的授权支持, load this module, or comment out

LoadModule authz_user_modulemodules/mod_authz_user.so

#如果需要使用DBM文件为组提供授权支持, load this module, or comment out

#LoadModule authz_dbm_modulemodules/mod_authz_dbm.so

#如果需要基于文件的所有者进行授权, load this module, or comment out

#LoadModuleauthz_owner_module modules/mod_authz_owner.so

#如果需要在未正确配置授权支持模块的情况下简单拒绝一切授权请求, load this module, or comment out

Loadmoduleauthz_default_module modules/mod_authz_default.so

#如果需要提供基本的HTTP认证, load this module or comment out that the module needs to load at least one authentication support module and one authorization support module at a time

LoadModule auth_basic_modulemodules/mod_auth_basic.so

# #如果需要提供HTTP MD5 Digest authentication, load this module, or comment out, this module needs to load at least one authentication support module and one authorization support module

#LoadModuleauth_digest_module modules/mod_auth_digest.so

#此模块提供文件描述符缓存支持 to improve Apache performance, recommend loading, but be careful to use

LoadModule file_cache_modulemodules/mod_file_cache.so

#此模块提供基于URI键的内容动态缓存 (memory or disk) to improve Apache performance, must be used concurrently with Mod_disk_cache/mod_mem_cache, recommended load

LoadModule cache_modulemodules/mod_cache.so

#此模块为mod_cache提供基于磁盘的缓存管理, recommended loading

LoadModule disk_cache_modulemodules/mod_disk_cache.so

#此模块为mod_cache提供基于内存的缓存管理, recommended loading

LoadModule mem_cache_modulemodules/mod_mem_cache.so

#如果需要管理SQL数据库连接, to provide support for modules that require database functionality, load this module or comment out (recommended)

#LoadModule dbd_modulemodules/mod_dbd.so

Dumping #此模块将所有I/O operations into the error log can result in the writing of a large amount of data in the log and only recommended when the problem is discovered and debugged

#LoadModule dumpio_modulemodules/mod_dumpio.so

#如果需要使用外部程序作为过滤器, load this module (not recommended), or comment out

#LoadModule ext_filter_modulemodules/mod_ext_filter.so

#如果需要实现服务端包含文档 (SSI) processing, load this module (not recommended), or comment out

#LoadModule include_modulemodules/mod_include.so

#如果需要根据上下文实际情况对输出过滤器进行动态配置, load this module, or comment out

LoadModule filter_modulemodules/mod_filter.so

#如果需要服务器在将输出内容发送到客户端以前进行压缩以节约带宽, load this module (recommended), or comment out

LoadModule deflate_modulemodules/mod_deflate.so

# #如果需要记录日志和定制日志文件格式, load this module (recommended), otherwise comment out

LoadModule log_config_modulemodules/mod_log_config.so

#如果需要对每个请求的输入/Output bytes and HTTP headers for logging, load this module, or comment out

#LoadModule logio_modulemodules/mod_logio.so

#如果允许Apache修改或清除传送到CGI脚本和SSI页面的环境变量, load this module, or comment out

LoadModule env_modulemodules/mod_env.so

#如果允许通过配置文件控制HTTP的 "Expires:" and "Cache-control:" header content, load this module (recommended), otherwise comment out

LoadModule expires_modulemodules/mod_expires.so

#如果允许通过配置文件控制任意的HTTP请求和应答头信息, load this module, or comment out

LoadModule headers_modulemodules/mod_headers.so

#如果需要实现RFC1413规定的ident查找, load this module (not recommended), or comment out

#LoadModule ident_modulemodules/mod_ident.so

#如果需要根据客户端请求头字段设置环境变量, load this module, or comment out

LoadModule setenvif_modulemodules/mod_setenvif.so

#此模块是mod_proxy的扩展, provides Apache Jserv protocol support, loading only when necessary

#LoadModule proxy_ajp_modulemodules/mod_proxy_ajp.so

#此模块是mod_proxy的扩展, provides load balancing support, loading only when necessary

#LoadModuleproxy_balancer_module modules/mod_proxy_balancer.so

#如果需要根据文件扩展名决定应答的行为 (processor/filter) and content (MIME type/language/character set/encoding), load this module, or comment out

LoadModule mime_modulemodules/mod_mime.so

#如果允许Apache提供DAV协议支持, load this module, or comment out

#LoadModule dav_modulemodules/mod_dav.so

#此模块生成描述服务器状态的Web页面, it is only recommended to load when tracking server performance and problems

#LoadModule status_modulemodules/mod_status.so

#如果需要自动对目录中的内容生成列表 (similar to "ls" or "dir" commands), loading this module (poses a security issue, not recommended), or comment out

#LoadModule autoindex_modulemodules/mod_autoindex.so

#如果需要服务器发送自己包含HTTP头内容的文件, load this module, or comment out

#LoadModule asis_modulemodules/mod_asis.so

#如果需要生成Apache配置情况的Web页面, load this module (poses a security issue, not recommended), or comment out

#LoadModule info_modulemodules/mod_info.so

#如果需要在非线程型MPM (Prefork) provides support for CGI script execution, loading this module, or commenting out

#LoadModule cgi_modulemodules/mod_cgi.so

#此模块在线程型MPM (worker) executes a CGI script with an external CGI daemon, and if you are using a CGI program in multithreaded mode, it is recommended that you replace the mod_cgi load or comment out

#LoadModule cgid_modulemodules/mod_cgid.so

#此模块为mod_dav访问服务器上的文件系统提供支持, this module should also be loaded if the MOD_DAV is loaded, or else it will be commented out

#LoadModule dav_fs_modulemodules/mod_dav_fs.so

#如果需要提供大批量虚拟主机的动态配置支持, </.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.