From: Joshua Slive This directive controls whether requests that contain trailing
pathname information that follows an actual filename (or
@@ -54,7 +54,7 @@ available When returning a document to the client the server looks for
the first existing access control file from this list of names
in every directory of the path to the document, if access
@@ -75,8 +75,8 @@ AccessFileName .acl
AllowOverride None See also See also This directive specifies the name of the character set that
will be added to any response that does not have any parameter on
@@ -92,7 +92,7 @@ response without an explicit character set The server can have modules compiled in which are not
actively in use. This directive can be used to enable the use
of those modules. The server comes with a pre-loaded list of
@@ -102,8 +102,8 @@ response without an explicit character set When the server finds an .htaccess file (as specified by Example: See also See also This directive sets the name of the authorization realm for a
directory. This realm is given to the client so that the user
knows which username and password to send.
@@ -183,8 +183,8 @@ authentication See also This directive selects the type of user authentication for a
directory. Only See also See also This directive enables the generation of
There will be times when the server is asked to provide a
document whose type cannot be determined by its MIME types
mappings. See also See also See also This directive sets the directory from which httpd will
serve files. Unless matched by a directive like Alias, the
server appends the path from the requested URL to the document
@@ -372,10 +372,10 @@ from the web The See also See also In the event of a problem or error, Apache can be configured
to do one of four things, See also See also The See also
The The See also See also The would match most common Internet graphics formats. See also See also When placed into an This directive enables DNS lookups so that host names can be
logged (and passed to CGIs/SSIs in This directive enables RFC1413-compliant logging of the
remote user name for each connection, where the client machine
runs identd or something similar. This information is logged in
@@ -602,9 +602,9 @@ user The The This directive allows inclusion of other configuration files
from within the server configuration files. See also The Keep-Alive extension to HTTP/1.0 and the persistent
connection feature of HTTP/1.1 provide long-lived HTTP sessions
which allow multiple requests to be sent over the same TCP
@@ -744,8 +744,8 @@ the server configuration files See also The number of seconds Apache will wait for a subsequent
request before closing the connection. Once a request has been
received, the timeout value specified by the
@@ -755,9 +755,9 @@ requests on a persistent connection Access controls are normally effective for
all access methods, and this is the usual
desired behavior. In the general case, access control
@@ -782,9 +782,9 @@ methods This directive specifies the number of bytes from 0
(meaning unlimited) to 2147483647 (2GB) that are allowed in a
request body. The default value is defined by the compile-time
@@ -817,8 +817,8 @@ from the client Number is an integer from 0 (meaning unlimited) to
32767. The default value is defined by the compile-time
constant This directive specifies the number of bytes from 0
to the value of the compile-time constant
This directive sets the number of bytes from 0 to
the value of the compile-time constant
Limit (in bytes) on maximum size of an XML-based request
body. A value of The See also See also The See also See also The The The The default in the absence of any other settings is
This directive selects which authenticated users can access
a directory. The allowed syntaxes are: See also See also Takes 1 or 2 parameters. The first parameter sets the soft
resource limit for all processes and the second parameter sets
the maximum resource limit. Either parameter can be a number,
@@ -1337,8 +1337,8 @@ by Apache children See also Takes 1 or 2 parameters. The first parameter sets the soft
resource limit for all processes and the second parameter sets
the maximum resource limit. Either parameter can be a number,
@@ -1356,8 +1356,8 @@ by Apache children See also Takes 1 or 2 parameters. The first parameter sets the soft
resource limit for all processes and the second parameter sets
the maximum resource limit. Either parameter can be a number,
@@ -1381,8 +1381,8 @@ processes launched by Apache children See also Access policy if both This directive is used to control how Apache finds the
interpreter used to run CGI scripts. The default technique is to
use the interpreter pointed to by the #! line in the
script. Setting The as users do not always mention that they are talking about the
server! The See also See also The See also See also The See also See also The See also See also The This directive controls whether When placed into an The If more than one filter is specified, they must be separated
by semicolons in the order in which they should process the
content. See also See also The If more than one filter is specified, they must be separated
by semicolons in the order in which they should process the
content. See also See also The In many situations Apache has to construct a
self-referential URL. That is, a URL which refers back to
the same server. With See also See also See also See also Each Apache directive available in the standard Apache
distribution is listed here. They are described using a
consistent format, and there is a dictionary of the terms used in their
descriptions available. Below is a list of all of the modules that come as part of
the Apache distribution. See also the complete
alphabetical list of all Apache
directives. The directives provided by mod_access are used in
-Apache HTTP Server Version 2.0
Apache Module core
Description: Status: Core Directives
AcceptPathInfo Directive
Description: Controls whether requests can contain trailing pathname information Syntax: Default: AcceptPathInfo Default
Context: server config, virtual host, directory, .htaccess Status: Core Module: core Compatibility: Available in Apache 2.0.30 and later
-Apache HTTP Server Version 2.0
Apache Module core
Description: Core Apache HTTP Server features that are always
+available Status: Core Directives
AcceptPathInfo Directive
Description: Controls whether requests can contain trailing pathname information Syntax: AcceptPathInfo On|Off|Default Default: AcceptPathInfo Default
Context: server config, virtual host, directory, .htaccess Status: Core Module: core Compatibility: Available in Apache 2.0.30 and later
</Files>
AccessFileName Directive
Description: Sets the name of the .htaccess file Syntax: Default: AccessFileName .htaccess
Context: server config, virtual host Status: Core Module: core AccessFileName Directive
Description: Sets the name of the .htaccess file Syntax: AccessFileName filename [filename] ... Default: AccessFileName .htaccess
Context: server config, virtual host Status: Core Module: core
</Directory>
AddDefaultCharset Directive
Description: Specifies the default character set to be added for a
-response without an explicit character set Syntax: Default: AddDefaultCharset Off
Context: server config, virtual host, directory, .htaccess Status: Core Module: core AddDefaultCharset Directive
Description: Specifies the default character set to be added for a
+response without an explicit character set Syntax: AddDefaultCharset On|Off|charset Default: AddDefaultCharset Off
Context: server config, virtual host, directory, .htaccess Status: Core Module: core
-
AddDefaultCharset utf-8
AddModule Directive
Description: Syntax: Context: server config Status: Core Module: core AddModule Directive
Description: Syntax: AddModule module [module] ... Context: server config Status: Core Module: core
-
AddDefaultCharset utf-8
AllowOverride Directive
Description: Sets the types of directives that are allowed in
-.htaccess files Syntax: Default: AllowOverride All
Context: directory Status: Core Module: core AllowOverride Directive
Description: Sets the types of directives that are allowed in
+.htaccess files Syntax: AllowOverride All|None|directive-type [directive-type] ... Default: AllowOverride All
Context: directory Status: Core Module: core AccessFileName
) it needs to know
which directives declared in that file can override earlier
access information.
-AllowOverride AuthConfig Indexes
AuthName Directive
Description: Sets the authorization realm for use in HTTP
-authentication Syntax: Context: directory, .htaccess Override: AuthConfig Status: Core Module: core AuthName Directive
Description: Sets the authorization realm for use in HTTP
+authentication Syntax: AuthName auth-domain Context: directory, .htaccess Override: AuthConfig Status: Core Module: core Authentication, Authorization, and
- Access Control AuthType Directive
Description: Selects the type of user authentication Syntax: Context: directory, .htaccess Override: AuthConfig Status: Core Module: core AuthType Directive
Description: Selects the type of user authentication Syntax: AuthType Basic|Digest Context: directory, .htaccess Override: AuthConfig Status: Core Module: core Basic
and Digest
are
currently implemented.
@@ -193,9 +193,9 @@ authenticationAuthUserFile
and
AuthGroupFile
to
work.
-ContentDigest Directive
Description: Enables the generation of Content-MD5 HTTP Response
-headers Syntax: Default: ContentDigest off
Context: server config, virtual host, directory, .htaccess Override: Options Status: Core Module: core Compatibility: Available in Apache 1.1 and later Syntax: ContentDigest on|off Default: ContentDigest off
Context: server config, virtual host, directory, .htaccess Override: Options Status: Core Module: core Compatibility: Available in Apache 1.1 and later Content-MD5
headers as defined in RFC1864
respectively RFC2068.Synta
by the core, and not by any module. For example, SSI documents,
output from CGI scripts, and byte range responses do not have
this header.
- DefaultType Directive
Description: Sets the MIME content-type that will be sent if the
-server cannot determine a type in any other way Syntax: Default: DefaultType text/html
Context: server config, virtual host, directory, .htaccess Override: FileInfo Status: Core Module: core DefaultType Directive
Description: Sets the MIME content-type that will be sent if the
+server cannot determine a type in any other way Syntax: DefaultType MIME-type Default: DefaultType text/html
Context: server config, virtual host, directory, .htaccess Override: FileInfo Status: Core Module: core <Directory> Directive Description: Enclose a group of directives that apply only to the
-named file-system directory and sub-directories Syntax: Context: server config, virtual host Status: Core Module: core <Directory> Directive
Description: Enclose a group of directives that apply only to the
+named file-system directory and sub-directories Syntax: <Directory directory-path>
+... </Directory> Context: server config, virtual host Status: Core Module: core <Directory>
and
</Directory>
are used to enclose a group of
directives which will apply only to the named directory and
@@ -335,13 +335,13 @@ named file-system directory and sub-directories<Directory> directives
cannot nest, and cannot appear in a <Limit>
or <LimitExcept>
section.
-<DirectoryMatch> Directive
Description: Enclose a group of directives that apply only to
file-system directories that match a regular expression and their
-subdirectories Syntax: Context: server config, virtual host Status: Core Module: core Syntax: <Directory regex>
+... </Directory> Context: server config, virtual host Status: Core Module: core <DirectoryMatch>
and
</DirectoryMatch>
are used to enclose a group
of directives which will apply only to the named directory and
@@ -353,12 +353,12 @@ subdirectories<Directory>
for
+<Directory>
for
a description of how regular expressions are mixed in with normal
<Directory>
sDocumentRoot Directive
Description: Sets the directory that forms the main document tree visible
-from the web Syntax: Default: DocumentRoot /usr/local/apache/htdocs
Context: server config, virtual host Status: Core Module: core Syntax: DocumentRoot directory-path Default: DocumentRoot /usr/local/apache/htdocs
Context: server config, virtual host Status: Core Module: core
DocumentRoot
should be specified without
a trailing slash.ErrorDocument Directive
Description: Specifies what the server will return to the client
-in case of an error Syntax: Context: server config, virtual host, directory, .htaccess Override: FileInfo Status: Core Module: core Compatibility: Quoting syntax for text messages is different in Apache
-2.0 Syntax: ErrorDocument error-code document Context: server config, virtual host, directory, .htaccess Override: FileInfo Status: Core Module: core Compatibility: Quoting syntax for text messages is different in Apache
+2.0 Prior to version 2.0, messages were indicated by prefixing
them with a single unmatched double quote character.
- ErrorLog Directive
Description: Sets the name of the file to which the server
-will log errors Syntax: Default: ErrorLog logs/error_log (Unix)
-ErrorLog logs/error.log (Windows and OS/2)
Context: server config, virtual host Status: Core Module: core Syntax: ErrorLog file-path|syslog[:facility] Default: ErrorLog logs/error_log (Unix)
+ErrorLog logs/error.log (Windows and OS/2)
Context: server config, virtual host Status: Core Module: core ErrorLog
directive sets the name of
the file to which the server will log any errors it encounters. If
the file-path does not begin with a slash (/) then it is
@@ -450,8 +450,8 @@ ErrorLog logs/error.log (Windows and OS/2)LogLevel
FileETag Directive
Description: Configures the file attributes used to create the ETag
-HTTP response header Syntax: Context: server config, virtual host, directory, .htaccess Override: FileInfo Status: Core Module: core FileETag Directive
Description: Configures the file attributes used to create the ETag
+HTTP response header Syntax: FileETag component ... Context: server config, virtual host, directory, .htaccess Override: FileInfo Status: Core Module: core FileETag
directive configures the file
attributes that are used to create the ETag (entity tag) response
@@ -491,8 +491,8 @@ HTTP response headerFileETag MTime Size'.
- <Files> Directive
Description: Contains that directives that apply to matched
-filenames Syntax: Context: server config, virtual host, directory, .htaccess Status: Core Module: core <Files> Directive
Description: Contains that directives that apply to matched
+filenames Syntax: <Files filename> ... </Files> Context: server config, virtual host, directory, .htaccess Status: Core Module: core <Files>
directive
provides for access control by filename. It is comparable to the
Directory
@@ -523,11 +523,11 @@ filenamesSyn
.htaccess files. This allows users to control access to their own
files, at a file-by-file level.
- <FilesMatch> Directive
Description: Contains that directives that apply to regular-expression matched
-filenames Syntax: Context: server config, virtual host, directory, .htaccess Status: Core Module: core Syntax: <FilesMatch regex> ... </FilesMatch> Context: server config, virtual host, directory, .htaccess Status: Core Module: core <FilesMatch>
directive
provides for access control by filename, just as the <Files>
directive
does. However, it accepts a regular expression. For example:Syn
ForceType Directive
Description: Forces all matching files to be served with the specified
-MIME content-type Syntax: Context: directory, .htaccess Status: Core Module: core Compatibility: Moved to the core in Apache 2.0 Syntax: ForceType mime-type Context: directory, .htaccess Status: Core Module: core Compatibility: Moved to the core in Apache 2.0 .htaccess
file or a
<Directory>
, or
<Location>
or
@@ -557,7 +557,7 @@ MIME content-typeDefaultType
,
this directive overrides all mime-type associations, including
filename extensions, that might identify the media type.
-HostnameLookups Directive
Description: Enables DNS lookups on client IP addresses Syntax: Default: HostnameLookups off
Context: server config, virtual host, directory Status: Core Module: core HostnameLookups Directive
Description: Enables DNS lookups on client IP addresses Syntax: HostnameLookups on|off|double Default: HostnameLookups off
Context: server config, virtual host, directory Status: Core Module: core REMOTE_HOST
).
The value double
refers to doing double-reverse
@@ -586,8 +586,8 @@ MIME content-typelogresolve, provided in
the /support directory, can be used to look up host
names from logged IP addresses offline.
- IdentityCheck Directive
Description: Enables logging of the RFC1413 identity of the remote
-user Syntax: Default: IdentityCheck off
Context: Status: Core Module: core IdentityCheck Directive
Description: Enables logging of the RFC1413 identity of the remote
+user Syntax: IdentityCheck on|off Default: IdentityCheck off
Context: Status: Core Module: core Syntax:<
possibly fail and add 30 seconds of latency to each hit. So in
general this is not very useful on public servers accessible
from the Internet.
- <IfDefine> Directive
Description: Encloses directives that will be processed only
-if a test is true at startup Syntax: Context: server config, virtual host, directory, .htaccess Status: Core Module: core <IfDefine> Directive
Description: Encloses directives that will be processed only
+if a test is true at startup Syntax: <IfDefine [!]parameter-name> ...
+ </IfDefine> Context: server config, virtual host, directory, .htaccess Status: Core Module: core <IfDefine
test>...</IfDefine>
section is used to
mark directives that are conditional. The directives within an
@@ -645,9 +645,9 @@ if a test is true at startup<IfModule> Directive Description: Encloses directives that are processed conditional on the
-presence of absence of a specific module Syntax: Context: server config, virtual host, directory, .htaccess Status: Core Module: core <IfModule> Directive
Description: Encloses directives that are processed conditional on the
+presence of absence of a specific module Syntax: <IfModule [!]module-name> ...
+ </IfModule> Context: server config, virtual host, directory, .htaccess Status: Core Module: core <IfModule
test>...</IfModule>
section is used to
mark directives that are conditional. The directives within an
@@ -678,8 +678,8 @@ presence of absence of a specific module<IfModule> sections are
nest-able, which can be used to implement simple multiple-module
tests.
- Include Directive
Description: Includes other configuration files from within
-the server configuration files Syntax: Context: server config Status: Core Module: core Include Directive
Description: Includes other configuration files from within
+the server configuration files Syntax: Include file-path|directory-path Context: server config Status: Core Module: core apachectl KeepAlive Directive
Description: Turns on or off HTTP persistent connections. Syntax: Default: KeepAlive On
Context: server config Status: Core Module: core KeepAlive Directive
Description: Turns on or off HTTP persistent connections. Syntax: KeepAlive on|off Default: KeepAlive On
Context: server config Status: Core Module: core MaxKeepAliveRequests
KeepAliveTimeout Directive
Description: Sets the amount of time the server will wait for subsequent
-requests on a persistent connection Syntax: Default: KeepAliveTimeout 15
Context: server config Status: Core Module: core KeepAliveTimeout Directive
Description: Sets the amount of time the server will wait for subsequent
+requests on a persistent connection Syntax: KeepAliveTimeout seconds Default: KeepAliveTimeout 15
Context: server config Status: Core Module: core <Limit> Directive Description: Restrict access controls to only certain HTTP
-methods Syntax: Context: server config, virtual host, directory, .htaccess Status: Core Module: core <Limit> Directive
Description: Restrict access controls to only certain HTTP
+methods Syntax: <Limit method [method] ... > ...
+ </Limit> Context: server config, virtual host, directory, .htaccess Status: Core Module: core Synta
MKCOL, COPY, MOVE, LOCK, and UNLOCK. The method name is
case-sensitive. If GET is used it will also restrict
HEAD requests.
- <LimitExcept> Directive
Description: Restrict access controls to all HTTP methods
-except the named ones Syntax: Context: server config, virtual host, directory, .htaccess Status: Core Module: core <LimitExcept> Directive
Description: Restrict access controls to all HTTP methods
+except the named ones Syntax: <LimitExcept method [method] ... > ...
+ </LimitExcept> Context: server config, virtual host, directory, .htaccess Status: Core Module: core <LimitExcept>
and
</LimitExcept>
are used to enclose a group of
access control directives which will then apply to any HTTP access
@@ -792,8 +792,8 @@ except the named ones<Limit>
section and can be used to control
both standard and nonstandard/unrecognized methods. See the
documentation for <Limit>
for more details.
-LimitRequestBody Directive
Description: Restricts the total size of the HTTP request body sent
-from the client Syntax: Default: LimitRequestBody 0
Context: server config, virtual host, directory, .htaccess Status: Core Module: core LimitRequestBody Directive
Description: Restricts the total size of the HTTP request body sent
+from the client Syntax: LimitRequestBody bytes Default: LimitRequestBody 0
Context: server config, virtual host, directory, .htaccess Status: Core Module: core LimitRequestFields Directive Description: Limits the number of HTTP request header fields that
-will be accepted from the client Syntax: Default: LimitRequestFields 100
Context: server config Status: Core Module: core LimitRequestFields Directive
Description: Limits the number of HTTP request header fields that
+will be accepted from the client Syntax: LimitRequestFields number Default: LimitRequestFields 100
Context: server config Status: Core Module: core DEFAULT_LIMIT_REQUEST_FIELDS
(100 as
@@ -841,8 +841,8 @@ will be accepted from the clientLimitRequestFieldSize Directive Description: Limits the size of the HTTP request header allowed from the
-client Syntax: Default: LimitRequestFieldsize 8190
Context: server config Status: Core Module: core LimitRequestFieldSize Directive
Description: Limits the size of the HTTP request header allowed from the
+client Syntax: LimitRequestFieldsize bytes Default: LimitRequestFieldsize 8190
Context: server config Status: Core Module: core DEFAULT_LIMIT_REQUEST_FIELDSIZE
(8190 as
@@ -864,8 +864,8 @@ clientSyntax
useful for avoiding some forms of denial-of-service attacks.
Under normal conditions, the value should not be changed from
the default.
- LimitRequestLine Directive
Description: Limit the size of the HTTP request line that will be accepted
-from the client Syntax: Default: LimitRequestLine 8190
Context: server config Status: Core Module: core LimitRequestLine Directive
Description: Limit the size of the HTTP request line that will be accepted
+from the client Syntax: LimitRequestLine bytes Default: LimitRequestLine 8190
Context: server config Status: Core Module: core DEFAULT_LIMIT_REQUEST_LINE
(8190 as distributed)
@@ -887,12 +887,12 @@ from the client
-LimitXMLRequestBody Directive Description: Limits the size of an XML-based request body Syntax: Default: LimitXMLRequestBody 1000000
Context: server config Status: Core Module: core LimitXMLRequestBody Directive
Description: Limits the size of an XML-based request body Syntax: LimitXMLRequestBody number Default: LimitXMLRequestBody 1000000
Context: server config Status: Core Module: core 0
will disable any checking.<Location> Directive
Description: Applies the enclosed directives only to matching
-URLs Syntax: Context: server config, virtual host Status: Core Module: core <Location> Directive
Description: Applies the enclosed directives only to matching
+URLs Syntax: <Location
+ URL-path|URL> ... </Location> Context: server config, virtual host Status: Core Module: core <Location>
directive
provides for access control by URL. It is similar to the
<Directory>
@@ -959,12 +959,12 @@ will implicitly match multiple slashes with a single slash. For
example, if you specify <Location /abc/def>
and the
request is to /abc//def
then it will match.<LocationMatch> Directive
Description: Applies the enclosed directives only to regular-expression
-matching URLs Syntax: Context: server config, virtual host Status: Core Module: core Syntax: <LocationMatch
+ regex> ... </Location> Context: server config, virtual host Status: Core Module: core <LocationMatch>
directive
provides for access control by URL, in an identical manner to
<Location>
. However, it takes a regular
@@ -976,10 +976,10 @@ matching URLswould match URLs that contained the substring "/extra/data"
or "/special/data".
- LogLevel Directive
Description: Controls the verbosity of the ErrorLog Syntax: Default: LogLevel warn
Context: server config, virtual host Status: Core Module: core LogLevel Directive
Description: Controls the verbosity of the ErrorLog Syntax: LogLevel level Default: LogLevel warn
Context: server config, virtual host Status: Core Module: core LogLevel
adjusts the verbosity of the
messages recorded in the error logs (see ErrorLog
directive). The following
levels are available, in order of decreasing
@@ -1115,16 +1115,16 @@ matching URLsUsing a level of at least crit
is
recommended.
-MaxKeepAliveRequests Directive
Description: Sets the number of requests allowed on a persistent
-connection Syntax: Default: MaxKeepAliveRequests 100
Context: server config Status: Core Module: core MaxKeepAliveRequests Directive
Description: Sets the number of requests allowed on a persistent
+connection Syntax: MaxKeepAliveRequests number Default: MaxKeepAliveRequests 100
Context: server config Status: Core Module: core MaxKeepAliveRequests
directive
limits the number of requests allowed per connection when
KeepAlive
is on. If it is
set to "0
", unlimited requests will be allowed. We
recommend that this setting be kept to a high value for maximum
server performance.NameVirtualHost Directive
Description: Configures an IP address for name-virtual
-hosting Syntax: Context: server config Status: Core Module: core NameVirtualHost Directive
Description: Configures an IP address for name-virtual
+hosting Syntax: NameVirtualHost addr[:port] Context: server config Status: Core Module: core NameVirtualHost
directive is a
required directive if you want to configure name-based virtual hosts.Synta
-NameVirtualHost [fe80::a00:20ff:fea7:ccea]:8080
Options Directive
Description: Configures what features are available in a particular
-directory Syntax: Default: Options All
Context: server config, virtual host, directory, .htaccess Override: Options Status: Core Module: core Options Directive
Description: Configures what features are available in a particular
+directory Syntax: Options
+ [+|-]option [[+|-]option] ... Default: Options All
Context: server config, virtual host, directory, .htaccess Override: Options Status: Core Module: core Options
directive controls which
server features are available in a particular directory.Syn
All
.Require Directive
Description: Selects which authenticated users can access
-a resource Syntax: Context: directory, .htaccess Override: AuthConfig Status: Core Module: core Require Directive
Description: Selects which authenticated users can access
+a resource Syntax: Require entity-name [entity-name] ... Context: directory, .htaccess Override: AuthConfig Status: Core Module: core Sy
place the Require
statement into a
<Limit>
section.
-RLimitCPU Directive
Description: Limits the CPU consumption of processes launched
-by Apache children Syntax: Default: Unset; uses operating system defaults
Context: server config, virtual host Status: Core Module: core Compatibility: Moved in version 2.0 to
- the MPMs RLimitCPU Directive
Description: Limits the CPU consumption of processes launched
+by Apache children Syntax: RLimitCPU number|max [number|max] Default: Unset; uses operating system defaults
Context: server config, virtual host Status: Core Module: core Compatibility: Moved in version 2.0 to
+ the MPMs RLimitMEM
RLimitNPROC
RLimitMEM Directive
Description: Limits the memory consumption of processes launched
-by Apache children Syntax: Default: Unset; uses operating system defaults
Context: server config, virtual host Status: Core Module: core Compatibility: Moved in version 2.0 to the MPMs. RLimitMEM Directive
Description: Limits the memory consumption of processes launched
+by Apache children Syntax: RLimitMEM number|max [number|max] Default: Unset; uses operating system defaults
Context: server config, virtual host Status: Core Module: core Compatibility: Moved in version 2.0 to the MPMs. RLimitCPU
RLimitNPROC
RLimitNPROC Directive
Description: Limits the number of processes that can be launched by
-processes launched by Apache children Syntax: Default: Unset; uses operating system defaults
Context: server config, virtual host Status: Core Module: core Compatibility: Moved in version 2.0 to the MPMs. RLimitNPROC Directive
Description: Limits the number of processes that can be launched by
+processes launched by Apache children Syntax: RLimitNPROC number|max [number|max] Default: Unset; uses operating system defaults
Context: server config, virtual host Status: Core Module: core Compatibility: Moved in version 2.0 to the MPMs. RLimitMEM
RLimitCPU
Satisfy Directive
Description: Configures how host-level access control and user authentication
-interact Syntax: Default: Satisfy all
Context: directory, .htaccess Status: Core Module: core Satisfy Directive
Description: Configures how host-level access control and user authentication
+interact Syntax: Satisfy any|all Default: Satisfy all
Context: directory, .htaccess Status: Core Module: core Allow
and Require
used. The parameter can be
either 'all' or 'any'. This directive is only
useful if access to a particular area is being restricted by both
@@ -1394,16 +1394,16 @@ interactSynt
valid username and password. This can be used to password restrict
an area, but to let clients from particular addresses in without
prompting for a password.
- ScriptInterpreterSource Directive
Description: Controls how the interpreter for CGI scripts is
-located Syntax: Default: ScriptInterpreterSource script
Context: directory, .htaccess Status: Core Module: core Compatibility: Win32 only ScriptInterpreterSource Directive
Description: Controls how the interpreter for CGI scripts is
+located Syntax: ScriptInterpreterSource registry|script Default: ScriptInterpreterSource script
Context: directory, .htaccess Status: Core Module: core Compatibility: Win32 only ScriptInterpreterSource registry
will
cause the Windows Registry to be searched using the script file
extension (e.g., .pl) as a search key.ServerAdmin Directive
Description: Sets the email address that the server includes in error
-messages sent to the client Syntax: Context: server config, virtual host Status: Core Module: core ServerAdmin Directive
Description: Sets the email address that the server includes in error
+messages sent to the client Syntax: ServerAdmin email-address Context: server config, virtual host Status: Core Module: core ServerAdmin
sets the e-mail address
that the server includes in any error messages it returns to the
client.ServerAdmin www-admin@foo.bar.com
ServerAlias Directive
Description: Sets alternate names for a host used when matching requests
-to name-virtual hosts Syntax: Context: virtual host Status: Core Module: core ServerAlias Directive
Description: Sets alternate names for a host used when matching requests
+to name-virtual hosts Syntax: ServerAlias hostname [hostname] ... Context: virtual host Status: Core Module: core ServerAlias
directive sets the
alternate names for a host, for use with name-based virtual hosts.
-
</VirtualHost>
ServerName Directive
Description: Sets the hostname and port that the server uses to identify
-itself Syntax: Context: server config, virtual host Status: Core Module: core Compatibility: In version 2.0, this
+ ServerName Directive
Description: Sets the hostname and port that the server uses to identify
+itself Syntax: ServerName fully-qualified-domain-name[:port] Context: server config, virtual host Status: Core Module: core Compatibility: In version 2.0, this
directive supersedes the functionality of the Port
- directive from version 1.3. ServerName
directive sets the hostname and
port that the server uses to identify itself. This is used when
creating redirection URLs. For example, if the name of the
@@ -1459,21 +1459,21 @@ itselfSyntax
mod_dir
module) will refer to the
specified port, or to the port number given in the client's request.
-ServerPath Directive
Description: Sets the legacy URL pathname for a name-virtual host that
-is accessed by an incompatible browser Syntax: Context: virtual host Status: Core Module: core Syntax: ServerPath directory-path Context: virtual host Status: Core Module: core ServerPath
directive sets the legacy
URL pathname for a host, for use with name-based virtual hosts.ServerRoot Directive
Description: Sets the base directory for the server installation Syntax: Default: ServerRoot /usr/local/apache
Context: server config Status: Core Module: core ServerRoot Directive
Description: Sets the base directory for the server installation Syntax: ServerRoot directory-path Default: ServerRoot /usr/local/apache
Context: server config Status: Core Module: core ServerRoot
directive sets the
directory in which the server lives. Typically it will contain the
subdirectories conf/
and logs/
. Relative
paths for other configuration files are taken as relative to this
directory.-d
+-d
option to httpd
ServerSignature Directive
Description: Configures the footer on server-generated documents Syntax: Default: ServerSignature Off
Context: server config, virtual host, directory, .htaccess Status: Core Module: core ServerSignature Directive
Description: Configures the footer on server-generated documents Syntax: ServerSignature On|Off|EMail Default: ServerSignature Off
Context: server config, virtual host, directory, .htaccess Status: Core Module: core ServerSignature
directive allows the
configuration of a trailing footer line under server-generated
documents (error messages, mod_proxy ftp directory listings,
@@ -1488,7 +1488,7 @@ is accessed by an incompatible browserServerAdmin
of the referenced
document.
-ServerTokens Directive
Description: Configures the Server HTTP response header Syntax: Default: ServerTokens Full
Context: server config Status: Core Module: core ServerTokens Directive
Description: Configures the Server HTTP response header Syntax: ServerTokens Minimal|ProductOnly|OS|Full Default: ServerTokens Full
Context: server config Status: Core Module: core Server
response
header field which is sent back to clients includes a
description of the generic OS-type of the server as well as
@@ -1518,8 +1518,8 @@ is accessed by an incompatible browserSetHandler Directive Description: Forces all matching files to be processed by a
-handler Syntax: Context: server config, virtual host, directory, .htaccess Status: Core Module: core Compatibility: Moved into the core in Apache 2.0 SetHandler Directive
Description: Forces all matching files to be processed by a
+handler Syntax: SetHandler handler-name Context: server config, virtual host, directory, .htaccess Status: Core Module: core Compatibility: Moved into the core in Apache 2.0 .htaccess
file or a
<Directory>
or
<Location>
@@ -1542,8 +1542,8 @@ handler
-Synta
SetHandler server-status
</Location>
SetInputFilter Directive
Description: Sets the filters that will process client requests and POST
-input Syntax: Context: server config, virtual host, directory, .htaccess Status: Core Module: core SetInputFilter Directive
Description: Sets the filters that will process client requests and POST
+input Syntax: SetInputFilter filter[;filter...] Context: server config, virtual host, directory, .htaccess Status: Core Module: core SetInputFilter
directive sets the
filter or filters which will process client requests and POST
input when they are received by the server. This is in addition to
@@ -1554,8 +1554,8 @@ inputSyntax:
SetOutputFilter Directive
Description: Sets the filters that will process responses from the
-server Syntax: Context: server config, virtual host, directory, .htaccess Status: Core Module: core SetOutputFilter Directive
Description: Sets the filters that will process responses from the
+server Syntax: SetOutputFilter filter [filter] ... Context: server config, virtual host, directory, .htaccess Status: Core Module: core SetOutputFilter
directive sets the filters
which will process responses from the server before they are
sent to the client. This is in addition to any filters defined
@@ -1575,8 +1575,8 @@ serverSyntax
TimeOut Directive
Description: Defines the amount of time the server will wait for
-certain events before failing a request Syntax: Default: TimeOut 300
Context: server config Status: Core Module: core TimeOut Directive
Description: Defines the amount of time the server will wait for
+certain events before failing a request Syntax: TimeOut number Default: TimeOut 300
Context: server config Status: Core Module: core TimeOut
directive currently defines
the amount of time Apache will wait for three things:UseCanonicalName Directive Description: Configures how the server determines its own name and
-port Syntax: Default: UseCanonicalName on
Context: server config, virtual host, directory, .htaccess Override: Options Status: Core Module: core UseCanonicalName Directive
Description: Configures how the server determines its own name and
+port Syntax: UseCanonicalName on|off|dns Default: UseCanonicalName on
Context: server config, virtual host, directory, .htaccess Override: Options Status: Core Module: core UseCanonicalName on
Apache will
@@ -1643,10 +1643,10 @@ portSyntax:<
they want as a hostname. But if the CGI is only using
SERVER_NAME
to construct self-referential URLs
then it should be just fine.
-<VirtualHost> Directive
Description: Contains directives that apply only to a specific
-hostname or IP address Syntax: <VirtualHost> Directive
Description: Contains directives that apply only to a specific
+hostname or IP address Syntax: <VirtualHost
addr[:port] [addr[:port]]
- ...> ... </VirtualHost> Context: server config Status: Core Module: core Context: server config Status: Core Module: core <VirtualHost>
and
</VirtualHost>
are used to enclose a group of
directives which will apply only to a particular virtual host. Any
@@ -1719,7 +1719,7 @@ hostname or IP address
cases. However, it is possible to restrict some methods, while
leaving other methods unrestricted, by enclosing the directives
in a NOTE: The use of <VirtualHost>
does not
affect what addresses Apache listens on. You may need to ensure
that Apache is listening on the correct addresses using Listen
.
-Apache HTTP Server Version 2.0
Directive Index
Apache HTTP Server Version 2.0
Directive Index
Apache HTTP Server Version 2.0
\ No newline at end of file
+
Apache HTTP Server Version 2.0
\ No newline at end of file
diff --git a/docs/manual/mod/index.html b/docs/manual/mod/index.html
index 42a5c9da4d..5ab5f67773 100644
--- a/docs/manual/mod/index.html
+++ b/docs/manual/mod/index.html
@@ -1,55 +1,55 @@
-
Apache HTTP Server Version 2.0
Module Index
Apache HTTP Server Version 2.0
Module Index
Core Features and Multi-Processing Modules
Core Features and Multi-Processing Modules
Other Modules
Other Modules
Expires
HTTP headers according to user-specified
- criteriaApache HTTP Server Version 2.0
\ No newline at end of file
+
Apache HTTP Server Version 2.0
\ No newline at end of file
diff --git a/docs/manual/mod/mod_access.html b/docs/manual/mod/mod_access.html
index 3d39bcd9af..a8437571d2 100644
--- a/docs/manual/mod/mod_access.html
+++ b/docs/manual/mod/mod_access.html
@@ -2,8 +2,8 @@
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
This file is generated from xml source: DO NOT EDIT
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
--->
Apache HTTP Server Version 2.0
Apache Module mod_access
Description: Status: Base Module Identifier: access_module Summary
Apache HTTP Server Version 2.0
Apache Module mod_access
Description: Provides access control based on client hostname, IP
+address, or other characteristics of the client request. Status: Base Module Identifier: access_module Summary
<Directory>
, <Files>
, and <Location>
sections as well as
.htaccess
files to control access to particular parts of the server. Access
@@ -26,10 +26,10 @@ address, or other characteristics of the client request.<Limit>
section.
See also
|
The Allow
directive affects which hosts can
access an area of the server. Access can be controlled by
@@ -120,17 +120,17 @@ SetEnvIf User-Agent ^KnockKnock/2.0 let_me_in
In this case, browsers with a user-agent string beginning
with KnockKnock/2.0
will be allowed access, and all
others will be denied.
|
This directive allows access to the server to be restricted
based on hostname, IP address, or environment variables. The
arguments for the Deny
directive are
identical to the arguments for the Allow
directive.
|
The Order
directive controls the default
access state and the order in which Allow
and Deny
directives are evaluated.
@@ -223,4 +223,4 @@ evaluated.
Order
directive. For details on the merging
of configuration sections, see the documentation on How Directory, Location and Files sections
work.
-