From: Vincent Deffontaines Date: Tue, 14 Dec 2010 20:03:01 +0000 (+0000) Subject: Removes the ":80" from the sole ServerName example of the documentation, as it is... X-Git-Tag: 2.3.11~376 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=46e97b76dff351c62d5e8e28d182b43f8c0d03e2;p=thirdparty%2Fapache%2Fhttpd.git Removes the ":80" from the sole ServerName example of the documentation, as it is a dumb "default". git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1049240 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 5a0cedf0625..250206ad333 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -122,11 +122,11 @@ On Windows from Apache httpd 2.3.3 and later. The basic premise is for the kernel to not send a socket to the server process until either data is received or an entire HTTP Request is buffered. Only - FreeBSD's Accept Filters, Linux's more primitive + FreeBSD's Accept Filters, Linux's more primitive TCP_DEFER_ACCEPT, and Windows' optimized AcceptEx() are currently supported.

-

Using none for an argument will disable any accept filters +

Using none for an argument will disable any accept filters for that protocol. This is useful for protocols that require a server send data first, such as ftp: or nntp:

AcceptFilter nntp none

@@ -142,12 +142,12 @@ On Windows from Apache httpd 2.3.3 and later. AcceptFilter http httpready
AcceptFilter https dataready

- +

The httpready accept filter buffers entire HTTP requests at - the kernel level. Once an entire request is received, the kernel then - sends it to the server. See the + the kernel level. Once an entire request is received, the kernel then + sends it to the server. See the - accf_http(9) man page for more details. Since HTTPS requests are + accf_http(9) man page for more details. Since HTTPS requests are encrypted only the accf_data(9) filter is used.

@@ -158,9 +158,9 @@ On Windows from Apache httpd 2.3.3 and later.

Linux's TCP_DEFER_ACCEPT does not support buffering http - requests. Any value besides none will enable + requests. Any value besides none will enable TCP_DEFER_ACCEPT on that listener. For more details - see the Linux + see the Linux tcp(7) man page.

@@ -185,7 +185,7 @@ On Windows from Apache httpd 2.3.3 and later. and will not recycle sockets between connections. This is useful for network adapters with broken driver support, as well as some virtual network providers such as vpn drivers, or spam, virus or spyware - filters.

+ filters.

See also

@@ -481,7 +481,7 @@ be passed through server error.

For security and performance reasons, do not set - AllowOverride to anything other than None + AllowOverride to anything other than None in your <Directory /> block. Instead, find (or create) the <Directory> block that refers to the directory where you're actually planning to place a @@ -618,7 +618,7 @@ named file-system directory, sub-directories, and their contents.

<Directory> and </Directory> are used to enclose a group of directives that will apply only to the named directory, - sub-directories of that directory, and the files within the respective + sub-directories of that directory, and the files within the respective directories. Any directive that is allowed in a directory context may be used. Directory-path is either the full path to a directory, or a wild-card string using @@ -757,9 +757,9 @@ the contents of file-system directories matching a regular expression.

<DirectoryMatch> and </DirectoryMatch> are used to enclose a group - of directives which will apply only to the named directory (and the files within), - the same as <Directory>. - However, it takes as an argument a + of directives which will apply only to the named directory (and the files within), + the same as <Directory>. + However, it takes as an argument a regular expression. For example:

@@ -778,8 +778,8 @@ the contents of file-system directories matching a regular expression.

Trailing Slash

- This directive applies to requests for directories that may or may - not end in a trailing slash, so expressions that are anchored to the + This directive applies to requests for directories that may or may + not end in a trailing slash, so expressions that are anchored to the end of line ($) must be written with care.
@@ -815,7 +815,7 @@ from the web

then an access to http://my.example.com/index.html refers to - /usr/web/index.html. If the directory-path is + /usr/web/index.html. If the directory-path is not absolute then it is assumed to be relative to the ServerRoot.

The DocumentRoot should be specified without @@ -1067,7 +1067,7 @@ in case of an error will be immediately halted and the internal error message returned. This is necessary to guard against security problems caused by bad requests.

- +

If you are using mod_proxy, you may wish to enable ProxyErrorOverride so that you can provide custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride, @@ -1091,7 +1091,7 @@ in case of an error

The ErrorLog directive sets the name of the file to which the server will log any errors it encounters. If - the file-path is not absolute then it is assumed to be + the file-path is not absolute then it is assumed to be relative to the ServerRoot.

Example

@@ -1129,7 +1129,7 @@ in case of an error

Note

When entering a file path on non-Unix platforms, care should be taken to make sure that only forward slashes are used even though the platform - may allow the use of back slashes. In general it is a good idea to always + may allow the use of back slashes. In general it is a good idea to always use forward slashes throughout the configuration files.

@@ -1286,7 +1286,7 @@ in case of an error
top

ExtendedStatus Directive

- @@ -1295,8 +1295,8 @@ request
Description:Keep track of extended status information for each +
Description:Keep track of extended status information for each request
Syntax:ExtendedStatus On|Off
Default:ExtendedStatus Off[*]
Module:core

This option tracks additional data per worker about the - currently executing request, and a utilization summary; you - can see these variables during runtime by configuring + currently executing request, and a utilization summary; you + can see these variables during runtime by configuring mod_status. Note that other modules may rely on this scoreboard.

@@ -1307,7 +1307,7 @@ request during a graceful restart.

-

Note that loading mod_status will change +

Note that loading mod_status will change the default behavior to ExtendedStatus On, while other third party modules may do the same. Such modules rely on collecting detailed information about the state of all workers. @@ -1375,8 +1375,8 @@ HTTP response header for static files changed via FileETag.

Server Side Includes

- An ETag is not generated for responses parsed by mod_include, - since the response entity can change without a change of the INode, MTime, or Size + An ETag is not generated for responses parsed by mod_include, + since the response entity can change without a change of the INode, MTime, or Size of the static file with embedded SSI directives.
@@ -1411,7 +1411,7 @@ filenames

The filename argument should include a filename, or a wild-card string, where ? matches any single character, and * matches any sequences of characters. - Regular expressions + Regular expressions can also be used, with the addition of the ~ character. For example:

@@ -1448,7 +1448,7 @@ filenames

The <FilesMatch> directive limits the scope of the enclosed directives by filename, just as the <Files> directive - does. However, it accepts a regular + does. However, it accepts a regular expression. For example:

@@ -1515,8 +1515,8 @@ media type in the HTTP Content-Type header field

This directive primarily overrides the content types generated for - static files served out of the filesystem. For resources other than - static files, where the generator of the response typically specifies + static files served out of the filesystem. For resources other than + static files, where the generator of the response typically specifies a Content-Type, this directive has no effect.

@@ -1536,7 +1536,7 @@ media type in the HTTP Content-Type header field argument ends with a percent symbol ('%'), subdirectories are created for each process id.

-

This directive currently only works with the prefork +

This directive currently only works with the prefork MPM.

@@ -1796,7 +1796,7 @@ wildcard matching available in 2.3.6 and later Include directive will fail with an error saying the file or directory cannot be found.

-

The file path specified may be an absolute path, or may be relative +

The file path specified may be an absolute path, or may be relative to the ServerRoot directory.

Examples:

@@ -1817,7 +1817,7 @@ wildcard matching available in 2.3.6 and later path. In the following example, the server will fail to load if no directories match conf/vhosts/*, but will load successfully if no files match *.conf.

- +

Include conf/vhosts/*/vhost.conf
Include conf/vhosts/*/*.conf @@ -1829,7 +1829,7 @@ wildcard matching available in 2.3.6 and later

Include strict conf/vhosts/*/*.conf

- +

In this example, the server load successfully if either conf/vhosts/* matches no directories, or if *.conf matches no files:

@@ -1892,7 +1892,7 @@ requests on a persistent connection Context:server config, virtual host Status:Core Module:core -Compatibility:Specifying a value in milliseconds is available in +Compatibility:Specifying a value in milliseconds is available in Apache httpd 2.3.2 and later

The number of seconds Apache httpd will wait for a subsequent @@ -1905,7 +1905,7 @@ Apache httpd 2.3.2 and later may cause performance problems in heavily loaded servers. The higher the timeout, the more server processes will be kept occupied waiting on connections with idle clients.

- +

In a name-based virtual host context, the value of the first defined virtual host (the default host) in a set of NameVirtualHost will be used. The other values will be ignored.

@@ -1983,12 +1983,12 @@ methods <LimitExcept GET> Require valid-user - + </LimitExcept>
<Limit POST> Require group editors - + </Limit>

@@ -2101,8 +2101,8 @@ from the client

LimitRequestBody 102400

- -

For a full description of how this directive is interpreted by + +

For a full description of how this directive is interpreted by proxy requests, see the mod_proxy documentation.

@@ -2149,7 +2149,7 @@ will be accepted from the client

Warning

-

When name-based virtual hosting is used, the value for this +

When name-based virtual hosting is used, the value for this directive is taken from the default (first-listed) virtual host for the NameVirtualHost the connection was mapped to.

@@ -2171,11 +2171,11 @@ client that will be allowed in an HTTP request header.

The LimitRequestFieldSize directive - allows the server administrator to reduce or increase the limit + allows the server administrator to reduce or increase the limit on the allowed size of an HTTP request header field. A server - needs this value to be large enough to hold any one header field - from a normal client request. The size of a normal request header - field will vary greatly among different client implementations, + needs this value to be large enough to hold any one header field + from a normal client request. The size of a normal request header + field will vary greatly among different client implementations, often depending upon the extent to which a user has configured their browser to support detailed content negotiation. SPNEGO authentication headers can be up to 12392 bytes.

@@ -2194,7 +2194,7 @@ client the default.

Warning

-

When name-based virtual hosting is used, the value for this +

When name-based virtual hosting is used, the value for this directive is taken from the default (first-listed) virtual host for the NameVirtualHost the connection was mapped to.

@@ -2212,7 +2212,7 @@ from the client Status:Core Module:core -

This directive sets the number of bytes that will be +

This directive sets the number of bytes that will be allowed on the HTTP request-line.

The LimitRequestLine directive allows @@ -2239,7 +2239,7 @@ from the client the default.

Warning

-

When name-based virtual hosting is used, the value for this +

When name-based virtual hosting is used, the value for this directive is taken from the default (first-listed) virtual host for the NameVirtualHost the connection was mapped to.

@@ -2300,26 +2300,26 @@ URLs

- In the example below, where no trailing slash is used, requests to + In the example below, where no trailing slash is used, requests to /private1, /private1/ and /private1/file.txt will have the enclosed - directives applied, but /private1other would not. + directives applied, but /private1other would not.

<Location /private1> ...

- In the example below, where a trailing slash is used, requests to + In the example below, where a trailing slash is used, requests to /private2/ and /private2/file.txt will have the enclosed - directives applied, but /private2 and /private2other would not. + directives applied, but /private2 and /private2other would not.

<Location /private2/> @@ -2331,7 +2331,7 @@ URLs

Use <Location> to apply directives to content that lives outside the filesystem. For content that lives in the filesystem, use <Directory> and <Files>. An exception is - <Location />, which is an easy way to + <Location />, which is an easy way to apply a configuration to the entire server.

@@ -2347,7 +2347,7 @@ URLs characters. Neither wildcard character matches a / in the URL-path.

Regular expressions - can also be used, with the addition of the ~ + can also be used, with the addition of the ~ character. For example:

@@ -2709,7 +2709,7 @@ or specified mutexes

  • default | yes

    This selects the default locking implementation, as determined by APR. The default locking implementation can - be displayed by running httpd with the + be displayed by running httpd with the -V option.

  • none | no @@ -2730,7 +2730,7 @@ or specified mutexes

    This is a mutex variant based on a SystemV IPC semaphore.

    Warning

    -

    It is possible to "leak" SysV semaphores if processes crash +

    It is possible to "leak" SysV semaphores if processes crash before the semaphore is removed.

    @@ -2765,7 +2765,7 @@ or specified mutexes
  • fcntl:/path/to/mutex -

    This is a mutex variant where a physical (lock-)file and the +

    This is a mutex variant where a physical (lock-)file and the fcntl() function are used as the mutex.

    Warning

    @@ -2787,10 +2787,10 @@ or specified mutexes order.

    • -

    Most mechanisms are only available on selected platforms, where the +

    Most mechanisms are only available on selected platforms, where the underlying platform and APR support it. Mechanisms which aren't available on all platforms are posixsem, - sysvsem, sem, pthread, fcntl, + sysvsem, sem, pthread, fcntl, flock, and file.

    With the file-based mechanisms fcntl and flock, @@ -2800,12 +2800,12 @@ or specified mutexes filesystem for /path/to/mutex and never a directory residing on a NFS- or AFS-filesystem. The basename of the file will be the mutex type, an optional instance string provided by the module, and unless the - OmitPID keyword is specified, the process id of the httpd + OmitPID keyword is specified, the process id of the httpd parent process will be appended to to make the file name unique, avoiding conflicts when multiple httpd instances share a lock file directory. For example, if the mutex name is mpm-accept and the lock file directory is /var/httpd/locks, the lock file name for the - httpd instance with parent process id 12345 would be + httpd instance with parent process id 12345 would be /var/httpd/locks/mpm-accept.12345.

    Security

    @@ -2896,15 +2896,15 @@ hosting Module:core -

    A single NameVirtualHost directive -identifies a set of identical virtual hosts on which the server will -further select from on the basis of the hostname +

    A single NameVirtualHost directive +identifies a set of identical virtual hosts on which the server will +further select from on the basis of the hostname requested by the client. The NameVirtualHost -directive is a required directive if you want to configure +directive is a required directive if you want to configure name-based virtual hosts.

    This directive, and the corresponding VirtualHost, -must be qualified with a port number if the server supports both HTTP +must be qualified with a port number if the server supports both HTTP and HTTPS connections.

    Although addr can be a hostname, it is recommended @@ -2912,16 +2912,16 @@ that you always use an IP address or a wildcard. A wildcard NameVirtualHost matches only virtualhosts that also have a literal wildcard as their argument.

    -

    In cases where a firewall or other proxy receives the requests and +

    In cases where a firewall or other proxy receives the requests and forwards them on a different IP address to the server, you must specify the IP address of the physical interface on the machine which will be servicing the requests.

    -

    In the example below, requests received on interface 192.0.2.1 and port 80 +

    In the example below, requests received on interface 192.0.2.1 and port 80 will only select among the first two virtual hosts. Requests received on port 80 on any other interface will only select among the third and fourth -virtual hosts. In the common case where the interface isn't important -to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives +virtual hosts. In the common case where the interface isn't important +to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives are necessary.

    @@ -3365,7 +3365,7 @@ of a request or the last 63, assuming the request itself is greater than Compatibility:Available in Apache httpd 2.2.7 and later.

    mod_status with ExtendedStatus On - displays the actual request being handled. + displays the actual request being handled. For historical purposes, only 63 characters of the request are actually stored for display purposes. This directive controls whether the 1st 63 characters are stored (the previous @@ -3467,7 +3467,7 @@ itself

    Additionally, ServerName is used (possibly in conjunction with ServerAlias) to uniquely identify a virtual host, when using name-based virtual hosts.

    - +

    For example, if the name of the machine hosting the web server is simple.example.com, but the machine also has the DNS alias www.example.com @@ -3475,7 +3475,7 @@ itself directive should be used:

    - ServerName www.example.com:80 + ServerName www.example.com

    The ServerName directive @@ -3503,7 +3503,7 @@ itself https:// scheme and the port number to which the clients connect in the ServerName directive to make sure that the server generates the correct - self-referential URLs. + self-referential URLs.

    See the description of the @@ -3569,7 +3569,7 @@ is accessed by an incompatible browser

    The ServerRoot directive sets the directory in which the server lives. Typically it will contain the subdirectories conf/ and logs/. Relative - paths in other configuration directives (such as Include or LoadModule, for example) are taken as + paths in other configuration directives (such as Include or LoadModule, for example) are taken as relative to this directory.

    Example

    @@ -3676,7 +3676,7 @@ header

    After version 2.0.44, this directive also controls the information presented by the ServerSignature directive.

    - +
    Setting ServerTokens to less than minimal is not recommended because it makes it more difficult to debug interoperational problems. Also note that @@ -3862,7 +3862,7 @@ certain events before failing a request allowed) error to the client.

    Finally, for testing and diagnostic purposes only, request - bodies may be allowed using the non-compliant TraceEnable + bodies may be allowed using the non-compliant TraceEnable extended directive. The core (as an origin server) will restrict the request body to 64k (plus 8k for chunk headers if Transfer-Encoding: chunked is used). The core will @@ -3985,7 +3985,7 @@ port

  • Port provided in Servername
  • Default port
    • - +

    With UseCanonicalPhysicalPort Off, the physical ports are removed from the ordering.

    diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml index 2a7e82f72ad..19597a8d72d 100644 --- a/docs/manual/mod/core.xml +++ b/docs/manual/mod/core.xml @@ -41,11 +41,11 @@ On Windows from Apache httpd 2.3.3 and later. The basic premise is for the kernel to not send a socket to the server process until either data is received or an entire HTTP Request is buffered. Only - FreeBSD's Accept Filters, Linux's more primitive + FreeBSD's Accept Filters, Linux's more primitive TCP_DEFER_ACCEPT, and Windows' optimized AcceptEx() are currently supported.

    -

    Using none for an argument will disable any accept filters +

    Using none for an argument will disable any accept filters for that protocol. This is useful for protocols that require a server send data first, such as ftp: or nntp:

    AcceptFilter nntp none @@ -61,12 +61,12 @@ On Windows from Apache httpd 2.3.3 and later. AcceptFilter http httpready
    AcceptFilter https dataready - +

    The httpready accept filter buffers entire HTTP requests at - the kernel level. Once an entire request is received, the kernel then - sends it to the server. See the + the kernel level. Once an entire request is received, the kernel then + sends it to the server. See the - accf_http(9) man page for more details. Since HTTPS requests are + accf_http(9) man page for more details. Since HTTPS requests are encrypted only the accf_data(9) filter is used.

    @@ -77,9 +77,9 @@ On Windows from Apache httpd 2.3.3 and later.

    Linux's TCP_DEFER_ACCEPT does not support buffering http - requests. Any value besides none will enable + requests. Any value besides none will enable TCP_DEFER_ACCEPT on that listener. For more details - see the Linux + see the Linux tcp(7) man page.

    @@ -104,7 +104,7 @@ On Windows from Apache httpd 2.3.3 and later. and will not recycle sockets between connections. This is useful for network adapters with broken driver support, as well as some virtual network providers such as vpn drivers, or spam, virus or spyware - filters.

    + filters.

    Protocol @@ -425,7 +425,7 @@ be passed through server error.

    For security and performance reasons, do not set - AllowOverride to anything other than None + AllowOverride to anything other than None in your <Directory /> block. Instead, find (or create) the <Directory> block that refers to the directory where you're actually planning to place a @@ -564,7 +564,7 @@ named file-system directory, sub-directories, and their contents.

    Directory and </Directory> are used to enclose a group of directives that will apply only to the named directory, - sub-directories of that directory, and the files within the respective + sub-directories of that directory, and the files within the respective directories. Any directive that is allowed in a directory context may be used. Directory-path is either the full path to a directory, or a wild-card string using @@ -705,9 +705,9 @@ the contents of file-system directories matching a regular expression.

    DirectoryMatch and </DirectoryMatch> are used to enclose a group - of directives which will apply only to the named directory (and the files within), - the same as Directory. - However, it takes as an argument a + of directives which will apply only to the named directory (and the files within), + the same as Directory. + However, it takes as an argument a regular expression. For example:

    @@ -726,8 +726,8 @@ the contents of file-system directories matching a regular expression. Trailing Slash - This directive applies to requests for directories that may or may - not end in a trailing slash, so expressions that are anchored to the + This directive applies to requests for directories that may or may + not end in a trailing slash, so expressions that are anchored to the end of line ($) must be written with care. @@ -762,8 +762,8 @@ from the web

    then an access to http://my.example.com/index.html refers to - /usr/web/index.html. If the directory-path is - not absolute then it is assumed to be relative to the /usr/web/index.html. If the directory-path is + not absolute then it is assumed to be relative to the ServerRoot.

    The DocumentRoot should be specified without @@ -1019,7 +1019,7 @@ in case of an error will be immediately halted and the internal error message returned. This is necessary to guard against security problems caused by bad requests.

    - +

    If you are using mod_proxy, you may wish to enable ProxyErrorOverride so that you can provide custom error messages on behalf of your Origin servers. If you don't enable ProxyErrorOverride, @@ -1041,7 +1041,7 @@ in case of an error

    The ErrorLog directive sets the name of the file to which the server will log any errors it encounters. If - the file-path is not absolute then it is assumed to be + the file-path is not absolute then it is assumed to be relative to the ServerRoot.

    Example @@ -1080,7 +1080,7 @@ in case of an error Note

    When entering a file path on non-Unix platforms, care should be taken to make sure that only forward slashes are used even though the platform - may allow the use of back slashes. In general it is a good idea to always + may allow the use of back slashes. In general it is a good idea to always use forward slashes throughout the configuration files.

     @@ -1258,7 +1258,7 @@ in case of an error ExtendedStatus -Keep track of extended status information for each +Keep track of extended status information for each request ExtendedStatus On|Off ExtendedStatus Off[*] @@ -1266,8 +1266,8 @@ request

    This option tracks additional data per worker about the - currently executing request, and a utilization summary; you - can see these variables during runtime by configuring + currently executing request, and a utilization summary; you + can see these variables during runtime by configuring mod_status. Note that other modules may rely on this scoreboard.

    @@ -1278,7 +1278,7 @@ request during a graceful restart.

    -

    Note that loading mod_status will change +

    Note that loading mod_status will change the default behavior to ExtendedStatus On, while other third party modules may do the same. Such modules rely on collecting detailed information about the state of all workers. @@ -1348,8 +1348,8 @@ HTTP response header for static files changed via FileETag. Server Side Includes - An ETag is not generated for responses parsed by mod_include, - since the response entity can change without a change of the INode, MTime, or Size + An ETag is not generated for responses parsed by mod_include, + since the response entity can change without a change of the INode, MTime, or Size of the static file with embedded SSI directives. @@ -1388,7 +1388,7 @@ filenames

    The filename argument should include a filename, or a wild-card string, where ? matches any single character, and * matches any sequences of characters. - Regular expressions + Regular expressions can also be used, with the addition of the ~ character. For example:

    @@ -1427,7 +1427,7 @@ filenames

    The FilesMatch directive limits the scope of the enclosed directives by filename, just as the Files directive - does. However, it accepts a regular + does. However, it accepts a regular expression. For example:

    @@ -1492,8 +1492,8 @@ media type in the HTTP Content-Type header field

    This directive primarily overrides the content types generated for - static files served out of the filesystem. For resources other than - static files, where the generator of the response typically specifies + static files served out of the filesystem. For resources other than + static files, where the generator of the response typically specifies a Content-Type, this directive has no effect.

     @@ -1512,7 +1512,7 @@ media type in the HTTP Content-Type header field argument ends with a percent symbol ('%'), subdirectories are created for each process id.

    -

    This directive currently only works with the prefork +

    This directive currently only works with the prefork MPM.

     @@ -1779,7 +1779,7 @@ wildcard matching available in 2.3.6 and later Include directive will fail with an error saying the file or directory cannot be found.

    -

    The file path specified may be an absolute path, or may be relative +

    The file path specified may be an absolute path, or may be relative to the ServerRoot directory.

    Examples:

    @@ -1801,7 +1801,7 @@ wildcard matching available in 2.3.6 and later path. In the following example, the server will fail to load if no directories match conf/vhosts/*, but will load successfully if no files match *.conf.

    - + Include conf/vhosts/*/vhost.conf
    Include conf/vhosts/*/*.conf @@ -1813,7 +1813,7 @@ wildcard matching available in 2.3.6 and later Include strict conf/vhosts/*/*.conf - +

    In this example, the server load successfully if either conf/vhosts/* matches no directories, or if *.conf matches no files:

    @@ -1825,7 +1825,7 @@ wildcard matching available in 2.3.6 and later apachectl - + KeepAlive Enables HTTP persistent connections @@ -1872,7 +1872,7 @@ requests on a persistent connection KeepAliveTimeout 5 server configvirtual host -Specifying a value in milliseconds is available in +Specifying a value in milliseconds is available in Apache httpd 2.3.2 and later @@ -1886,7 +1886,7 @@ Apache httpd 2.3.2 and later may cause performance problems in heavily loaded servers. The higher the timeout, the more server processes will be kept occupied waiting on connections with idle clients.

    - +

    In a name-based virtual host context, the value of the first defined virtual host (the default host) in a set of NameVirtualHost will be used. @@ -1970,12 +1970,12 @@ methods <LimitExcept GET> Require valid-user - + </LimitExcept>
    <Limit POST> Require group editors - + </Limit> @@ -2092,8 +2092,8 @@ from the client LimitRequestBody 102400 - -

    For a full description of how this directive is interpreted by + +

    For a full description of how this directive is interpreted by proxy requests, see the mod_proxy documentation.

    @@ -2139,7 +2139,7 @@ will be accepted from the client     Warning -

    When name-based virtual hosting is used, the value for this +

    When name-based virtual hosting is used, the value for this directive is taken from the default (first-listed) virtual host for the NameVirtualHost the connection was mapped to.

     @@ -2160,11 +2160,11 @@ client that will be allowed in an HTTP request header.

    The LimitRequestFieldSize directive - allows the server administrator to reduce or increase the limit + allows the server administrator to reduce or increase the limit on the allowed size of an HTTP request header field. A server - needs this value to be large enough to hold any one header field - from a normal client request. The size of a normal request header - field will vary greatly among different client implementations, + needs this value to be large enough to hold any one header field + from a normal client request. The size of a normal request header + field will vary greatly among different client implementations, often depending upon the extent to which a user has configured their browser to support detailed content negotiation. SPNEGO authentication headers can be up to 12392 bytes.

    @@ -2183,7 +2183,7 @@ client the default. Warning -

    When name-based virtual hosting is used, the value for this +

    When name-based virtual hosting is used, the value for this directive is taken from the default (first-listed) virtual host for the NameVirtualHost the connection was mapped to.

     @@ -2200,7 +2200,7 @@ from the client server configvirtual host -

    This directive sets the number of bytes that will be +

    This directive sets the number of bytes that will be allowed on the HTTP request-line.

    The LimitRequestLine directive allows @@ -2227,7 +2227,7 @@ from the client the default. Warning -

    When name-based virtual hosting is used, the value for this +

    When name-based virtual hosting is used, the value for this directive is taken from the default (first-listed) virtual host for the NameVirtualHost the connection was mapped to.

    @@ -2291,33 +2291,33 @@ URLs
    • The specified location matches exactly the path component of the URL.
      • -
    • The specified location, which ends in a forward slash, is a prefix +
    • The specified location, which ends in a forward slash, is a prefix of the path component of the URL (treated as a context root).
      • -
    • The specified location, with the addition of a trailing slash, is a +
    • The specified location, with the addition of a trailing slash, is a prefix of the path component of the URL (also treated as a context root).

    - In the example below, where no trailing slash is used, requests to + In the example below, where no trailing slash is used, requests to /private1, /private1/ and /private1/file.txt will have the enclosed - directives applied, but /private1other would not. + directives applied, but /private1other would not.

    <Location /private1> ...

    - In the example below, where a trailing slash is used, requests to + In the example below, where a trailing slash is used, requests to /private2/ and /private2/file.txt will have the enclosed - directives applied, but /private2 and /private2other would not. + directives applied, but /private2 and /private2other would not.

    <Location /private2/> ... - When to use <directive + <note><title>When to use <directive type="section">Location</directive>

    Use Location to apply @@ -2325,7 +2325,7 @@ URLs content that lives in the filesystem, use Directory and Files. An exception is - <Location />, which is an easy way to + <Location />, which is an easy way to apply a configuration to the entire server.

     @@ -2341,7 +2341,7 @@ URLs characters. Neither wildcard character matches a / in the URL-path.

    Regular expressions - can also be used, with the addition of the ~ + can also be used, with the addition of the ~ character. For example:

    @@ -2705,7 +2705,7 @@ or specified mutexes
  • default | yes

    This selects the default locking implementation, as determined by APR. The default locking implementation can - be displayed by running httpd with the + be displayed by running httpd with the -V option.

  • none | no @@ -2726,7 +2726,7 @@ or specified mutexes

    This is a mutex variant based on a SystemV IPC semaphore.

    Warning -

    It is possible to "leak" SysV semaphores if processes crash +

    It is possible to "leak" SysV semaphores if processes crash before the semaphore is removed.

     @@ -2761,7 +2761,7 @@ or specified mutexes
  • fcntl:/path/to/mutex -

    This is a mutex variant where a physical (lock-)file and the +

    This is a mutex variant where a physical (lock-)file and the fcntl() function are used as the mutex.

    Warning @@ -2783,10 +2783,10 @@ or specified mutexes order.

    • -

    Most mechanisms are only available on selected platforms, where the +

    Most mechanisms are only available on selected platforms, where the underlying platform and APR support it. Mechanisms which aren't available on all platforms are posixsem, - sysvsem, sem, pthread, fcntl, + sysvsem, sem, pthread, fcntl, flock, and file.

    With the file-based mechanisms fcntl and flock, @@ -2796,12 +2796,12 @@ or specified mutexes filesystem for /path/to/mutex and never a directory residing on a NFS- or AFS-filesystem. The basename of the file will be the mutex type, an optional instance string provided by the module, and unless the - OmitPID keyword is specified, the process id of the httpd + OmitPID keyword is specified, the process id of the httpd parent process will be appended to to make the file name unique, avoiding conflicts when multiple httpd instances share a lock file directory. For example, if the mutex name is mpm-accept and the lock file directory is /var/httpd/locks, the lock file name for the - httpd instance with parent process id 12345 would be + httpd instance with parent process id 12345 would be /var/httpd/locks/mpm-accept.12345.

    Security @@ -2892,15 +2892,15 @@ hosting -

    A single NameVirtualHost directive -identifies a set of identical virtual hosts on which the server will -further select from on the basis of the hostname +

    A single NameVirtualHost directive +identifies a set of identical virtual hosts on which the server will +further select from on the basis of the hostname requested by the client. The NameVirtualHost -directive is a required directive if you want to configure +directive is a required directive if you want to configure name-based virtual hosts.

    This directive, and the corresponding VirtualHost, -must be qualified with a port number if the server supports both HTTP +must be qualified with a port number if the server supports both HTTP and HTTPS connections.

    Although addr can be a hostname, it is recommended @@ -2908,16 +2908,16 @@ that you always use an IP address or a wildcard. A wildcard NameVirtualHost matches only virtualhosts that also have a literal wildcard as their argument.

    -

    In cases where a firewall or other proxy receives the requests and +

    In cases where a firewall or other proxy receives the requests and forwards them on a different IP address to the server, you must specify the IP address of the physical interface on the machine which will be servicing the requests.

    -

    In the example below, requests received on interface 192.0.2.1 and port 80 +

    In the example below, requests received on interface 192.0.2.1 and port 80 will only select among the first two virtual hosts. Requests received on port 80 on any other interface will only select among the third and fourth -virtual hosts. In the common case where the interface isn't important -to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives +virtual hosts. In the common case where the interface isn't important +to the mapping, only the "*:80" NameVirtualHost and VirtualHost directives are necessary.

    @@ -3355,7 +3355,7 @@ of a request or the last 63, assuming the request itself is greater than

    mod_status with ExtendedStatus On - displays the actual request being handled. + displays the actual request being handled. For historical purposes, only 63 characters of the request are actually stored for display purposes. This directive controls whether the 1st 63 characters are stored (the previous @@ -3457,7 +3457,7 @@ itself in conjunction with ServerAlias) to uniquely identify a virtual host, when using name-based virtual hosts.

    - +

    For example, if the name of the machine hosting the web server is simple.example.com, but the machine also has the DNS alias www.example.com @@ -3465,7 +3465,7 @@ itself directive should be used:

    - ServerName www.example.com:80 + ServerName www.example.com

    The ServerName directive @@ -3494,7 +3494,7 @@ itself https:// scheme and the port number to which the clients connect in the ServerName directive to make sure that the server generates the correct - self-referential URLs. + self-referential URLs.

    See the description of the @@ -3556,7 +3556,7 @@ is accessed by an incompatible browser subdirectories conf/ and logs/. Relative paths in other configuration directives (such as Include or LoadModule, for example) are taken as + module="mod_so">LoadModule, for example) are taken as relative to this directory.

    Example @@ -3661,7 +3661,7 @@ header

    After version 2.0.44, this directive also controls the information presented by the ServerSignature directive.

    - + Setting ServerTokens to less than minimal is not recommended because it makes it more difficult to debug interoperational problems. Also note that @@ -3838,7 +3838,7 @@ certain events before failing a request allowed) error to the client.

    Finally, for testing and diagnostic purposes only, request - bodies may be allowed using the non-compliant TraceEnable + bodies may be allowed using the non-compliant TraceEnable extended directive. The core (as an origin server) will restrict the request body to 64k (plus 8k for chunk headers if Transfer-Encoding: chunked is used). The core will @@ -3960,7 +3960,7 @@ port

  • Port provided in Servername
  • Default port
    • - +

    With UseCanonicalPhysicalPort Off, the physical ports are removed from the ordering.