From c3dbc437a5922f7ac65c6ca1660f926416c5f347 Mon Sep 17 00:00:00 2001 From: Astrid Malo Date: Wed, 8 Jan 2003 06:46:45 +0000 Subject: [PATCH] - clarify somes mistakables - some markup improvement - other peanuts (typo, etc.) git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@98194 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html.en | 246 +++++++++++++++--------------- docs/manual/mod/core.xml | 282 ++++++++++++++++++----------------- 2 files changed, 268 insertions(+), 260 deletions(-) diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 6b916a8238..5a79aeb35f 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -168,7 +168,7 @@ available Status:Core Module:core -

When returning a document to the client the server looks for +

While processing a request the server looks for the first existing configuration file from this list of names in every directory of the path to the document, if distributed configuration files are enabled for that directory. For @@ -271,7 +271,7 @@ response without an explicit character set </Location>

-

Note:

+

Note

Enabling filters with AddOutputFilterByType may fail partially or completely in some cases. For expample, no filters are applied if the content type falls back to the DefaultType, even if the DefaultType is the same.

@@ -309,7 +309,7 @@ response without an explicit character set it needs to know which directives declared in that file can override earlier access information.

-

Only available in Directory sections

+

Only available in <Directory> sections

AllowOverride is valid only in <Directory> sections, not in <Location> or <Files> sections. @@ -335,14 +335,14 @@ response without an explicit character set Allow use of the authorization directives (AuthDBMGroupFile, AuthDBMUserFile, AuthGroupFile, - AuthName, + AuthName, AuthType, AuthUserFile, Require, etc.).
FileInfo
Allow use of the directives controlling document types (DefaultType, ErrorDocument, ForceType, LanguagePriority, - SetHandler, SetInputFilter, SetOutputFilter, and + SetHandler, SetInputFilter, SetOutputFilter, and mod_mime Add* and Remove* directives, etc.).
@@ -414,7 +414,7 @@ authentication

See also

@@ -430,7 +430,7 @@ authentication

This directive selects the type of user authentication for a directory. Only Basic and Digest are - currently implemented. + currently implemented. It must be accompanied by AuthName and Require directives, and directives such as AuthUserFile and @@ -459,8 +459,8 @@ scripts

This directive is used to control how Apache finds the interpreter used to run CGI scripts. For example, setting CGIMapExtension sys:\foo.nlm .foo will - cause all CGI script files with a .foo extension to be passed to the - FOO interpreter.

+ cause all CGI script files with a .foo extension to + be passed to the FOO interpreter.

top
@@ -533,7 +533,7 @@ server cannot determine a type in any other way

Note that unlike ForceType, this directive is only provides the default mime-type. All other mime-type definitions, including filename extensions, that might identify the media type - will override this default.

+ will override this default.

top
@@ -589,7 +589,7 @@ named file-system directory and sub-directories

would match directories in /www/ that consisted of three numbers.

-

If multiple (non-regular expression) directory sections +

If multiple (non-regular expression) <Directory> sections match the directory (or its parents) containing a document, then the directives are applied in the order of shortest match first, interspersed with the directives from the .htaccess files. For example, @@ -619,7 +619,7 @@ named file-system directory and sub-directories

  • Apply directive AllowOverride FileInfo (for directory /home/web).
    • -
  • Apply any FileInfo directives in +
  • Apply any FileInfo directives in /home/web/.htaccess
    • @@ -636,7 +636,7 @@ named file-system directory and sub-directories </Directory>

    -

    The regular expression section won't be considered until after +

    the regular expression section won't be considered until after all normal <Directory>s and .htaccess files have been applied. Then the regular expression will match on /home/abc/public_html/abc and be applied.

    @@ -666,8 +666,8 @@ named file-system directory and sub-directories

    See also

    @@ -675,7 +675,7 @@ named file-system directory and sub-directories
    top

    <DirectoryMatch> Directive

    -
    top
    @@ -783,7 +783,9 @@ Location

    <Directory "/path-to-nfs-files"> - EnableMMAP Off + + EnableMMAP Off + </Directory>

    @@ -809,16 +811,16 @@ Location

    This sendfile mechanism avoids seperate read and send operations, and buffer allocations. But on some platforms or within some - filesystems, it is better to disable this feature to avoid + filesystems, it is better to disable this feature to avoid operational problems:

    @@ -833,8 +835,10 @@ Location for the offending files by specifying:

    - <Directory "/path-to-nfs-files">
    - EnableSendfile Off
    + <Directory "/path-to-nfs-files"> + + EnableSendfile Off + </Directory>

    @@ -897,7 +901,7 @@ in case of an error URL in an ErrorDocument 401, the client will not know to prompt the user for a password since it will not receive the 401 status code. Therefore, if you use an - "ErrorDocument 401" directive then it must refer to a local + ErrorDocument 401 directive then it must refer to a local document.

    Microsoft Internet Explorer (MSIE) will by default ignore @@ -922,7 +926,7 @@ in case of an error

    Description:Enclose directives that apply to +
    Description:Enclose directives that apply to file-system directories matching a regular expression and their subdirectories
    Syntax:<DirectoryMatch regex> @@ -701,10 +701,10 @@ subdirectories
    - @@ -936,7 +940,7 @@ ErrorLog logs/error.log (Windows and OS/2)

    Example

    ErrorLog /var/log/httpd/error_log

    - +

    If the file-path begins with a pipe (|) then it is assumed to be a command to spawn to handle the error log.

    @@ -1056,8 +1060,8 @@ filenames <Files ~ "\.(gif|jpe?g|png)$">

    -

    would match most common Internet graphics formats. In Apache 1.3 - and later, <FilesMatch> is preferred, however.

    +

    would match most common Internet graphics formats. <FilesMatch> is preferred, + however.

    Note that unlike <Directory> and <Location> sections, <Files> sections can be used inside .htaccess files. This allows users to control access to @@ -1066,10 +1070,9 @@ filenames

    See also

    top
    @@ -1095,10 +1098,9 @@ filenames

    See also

    top
    @@ -1164,7 +1166,7 @@ MIME content-type

    This directive enables DNS lookups so that host names can be logged (and passed to CGIs/SSIs in REMOTE_HOST). The value Double refers to doing double-reverse - DNS. That is, after a reverse lookup is performed, a forward + DNS lookup. That is, after a reverse lookup is performed, a forward lookup is then performed on that result. At least one of the ip addresses in the forward lookup must match the original address. (In "tcpwrappers" terminology this is called @@ -1186,9 +1188,9 @@ MIME content-type don't have to suffer the extra latency that a lookup entails. Heavily loaded sites should leave this directive Off, since DNS lookups can take considerable - amounts of time. The utility logresolve, provided in - the /support directory, can be used to look up host - names from logged IP addresses offline.

    + amounts of time. The utility logresolve, compiled by default + to the bin subdirectory of your installation directory, can + be used to look up host names from logged IP addresses offline.

    top
    @@ -1346,7 +1348,7 @@ the server configuration files fail.

    The file path specified may be a fully qualified path (i.e. - starting with a slash), or may be relative to the + starting with a slash), or may be relative to the ServerRoot directory.

    Examples:

    @@ -1395,8 +1397,8 @@ the server configuration files which allow multiple requests to be sent over the same TCP connection. In some cases this has been shown to result in an almost 50% speedup in latency times for HTML documents with - many images. To enable Keep-Alive connections in Apache 1.2 and - later, set KeepAlive On.

    + many images. To enable Keep-Alive connections, set + KeepAlive On.

    For HTTP/1.0 clients, Keep-Alive connections will only be used if they are specifically requested by a client. In @@ -1458,11 +1460,10 @@ methods

    The purpose of the <Limit> directive is to restrict the effect of the access controls to the nominated HTTP methods. For all other methods, the access - restrictions that are enclosed in the <Limit> - bracket will have no effect. The following - example applies the access control only to the methods POST, - PUT, and DELETE, leaving all other methods - unprotected:

    + restrictions that are enclosed in the <Limit> bracket will have no + effect. The following example applies the access control + only to the methods POST, PUT, and + DELETE, leaving all other methods unprotected:

    <Limit POST PUT DELETE>
    @@ -1497,7 +1498,7 @@ except the named ones

    <LimitExcept> and </LimitExcept> are used to enclose a group of access control directives which will then apply to any - HTTP access method not listed in the arguments; + HTTP access method not listed in the arguments; i.e., it is the opposite of a <Limit> section and can be used to control both standard and nonstandard/unrecognized methods. See the documentation for <Limit> for more details.

    @@ -1540,8 +1541,8 @@ from the client response instead of servicing the request. The size of a normal request message body will vary greatly depending on the nature of the resource and the methods allowed on that resource. CGI scripts - typically use the message body for passing form information to the - server. Implementations of the PUT method will require + typically use the message body for retrieving form information. + Implementations of the PUT method will require a value at least as large as any representation that the server wishes to accept for that resource.

    @@ -1551,7 +1552,7 @@ from the client attacks.

    If, for example, you are permitting file upload to a particular - location, and wich to limit the size of the uploaded file to 100K, + location, and wish to limit the size of the uploaded file to 100K, you might use the following directive:

    @@ -1563,7 +1564,7 @@ from the client

    top

    LimitRequestFields Directive

    Description:Location where the server will log errors
    Syntax: ErrorLog file-path|syslog[:facility]
    Default:ErrorLog logs/error_log (Unix) +
    Default:ErrorLog logs/error_log (Unix)
    ErrorLog logs/error.log (Windows and OS/2)
    Context:server config, virtual host
    Status:Core
    - @@ -1619,7 +1620,7 @@ client distributed) that will be allowed in an HTTP request header.

    -

    The LimitRequestFieldsize directive +

    The LimitRequestFieldSize directive allows the server administrator to reduce the limit on the allowed size of an HTTP request header field below the normal input buffer size compiled with the server. A server needs this value to be @@ -1689,7 +1690,7 @@ from the client

    LimitXMLRequestBody Directive

    Description:Limits the number of HTTP request header fields that +
    Description:Limits the number of HTTP request header fields that will be accepted from the client
    Syntax:LimitRequestFields number
    Default:LimitRequestFields 100
    - + @@ -1727,8 +1728,8 @@ URLs .htaccess files are read, and after the <Files> sections.

    Note that URLs do not have to line up with the filesystem at - all, it should be emphasized that <Location> operates - completely outside the filesystem.

    + all, it should be emphasized that <Location> operates completely + outside the filesystem.

    For all origin (non-proxy) requests, the URL to be matched is a URL-path of the form /path/. No scheme, hostname, @@ -1737,7 +1738,7 @@ URLs scheme://servername/path, and you must include the prefix.

    -

    The URL may use wildcards In a wild-card string, ? matches +

    The URL may use wildcards. In a wild-card string, ? matches any single character, and * matches any sequences of characters.

    @@ -1750,10 +1751,8 @@ URLs

    would match URLs that contained the substring /extra/data - or /special/data. In Apache 1.3 and above, a new directive - <LocationMatch> - exists which behaves identical to the regex version of - <Location>.

    + or /special/data. The directive <LocationMatch> behaves + identical to the regex version of <Location>.

    The <Location> functionality is especially useful when combined with the @@ -1781,7 +1780,7 @@ URLs The <LocationMatch> directive and the regex version of <Location> require you to explicitly specify multiple slashes if that is your intention.

    - +

    For example, <LocationMatch ^/abc> would match the request URL /abc but not the request URL //abc. The (non-regex) <Location> directive behaves similarly when used for @@ -1793,16 +1792,15 @@ URLs

    See also

    top

    <LocationMatch> Directive

    Description:Limits the size of an XML-based request body
    Syntax:LimitXMLRequestBody number
    Syntax:LimitXMLRequestBody bytes
    Default:LimitXMLRequestBody 1000000
    Context:server config, virtual host, directory, .htaccess
    Override:All
    - @@ -1825,10 +1823,9 @@ matching URLs

    See also

    top
    @@ -1942,7 +1939,7 @@ matching URLs
    top

    MaxKeepAliveRequests Directive

    Description:Applies the enclosed directives only to regular-expression +
    Description:Applies the enclosed directives only to regular-expression matching URLs
    Syntax:<LocationMatch regex> ... </LocationMatch>
    - @@ -1994,11 +1991,14 @@ hosting servicing the requests. If you have multiple name-based hosts on multiple addresses, repeat the directive for each address.

    -

    Note: the "main server" and any _default_ servers will - never be served for a request to a - NameVirtualHost IP Address (unless for some - reason you specify NameVirtualHost but then - don't define any VirtualHosts for that address).

    +

    Note

    +

    Note, that the "main server" and any _default_ servers + will never be served for a request to a + NameVirtualHost IP Address (unless for some + reason you specify NameVirtualHost but then + don't define any VirtualHosts for that + address).

    +

    Optionally you can specify a port number on which the name-based virtual hosts should be used, e.g.

    @@ -2061,17 +2061,17 @@ directory the following:

    -
    All
    +
    All
    All options except for MultiViews. This is the default setting.
    -
    ExecCGI
    +
    ExecCGI
    Execution of CGI scripts is permitted.
    -
    FollowSymLinks
    +
    FollowSymLinks
    @@ -2084,12 +2084,12 @@ directory section.

    -
    Includes
    +
    Includes
    Server-side includes are permitted.
    -
    IncludesNOEXEC
    +
    IncludesNOEXEC
    @@ -2098,7 +2098,7 @@ directory #include virtual CGI scripts from ScriptAliase'd directories.
    -
    Indexes
    +
    Indexes
    If a URL which maps to a directory is requested, and the @@ -2106,13 +2106,13 @@ directory index.html) in that directory, then the server will return a formatted listing of the directory.
    -
    MultiViews
    +
    MultiViews
    Content negotiated "MultiViews" are allowed.
    -
    SymLinksIfOwnerMatch
    +
    SymLinksIfOwnerMatch
    @@ -2170,10 +2170,11 @@ directory Includes are set for the /web/docs/spec directory.

    - -

    Note: Using -IncludesNOEXEC or - -Includes disables server-side includes completely - regardless of the previous setting.

    +

    Note

    +

    Using -IncludesNOEXEC or + -Includes disables server-side includes completely + regardless of the previous setting.

    +

    The default in the absence of any other settings is All.

    @@ -2195,23 +2196,23 @@ a resource
    • - Require user userid [userid] ... + Require user userid [userid] ... -

      Only the named users can access the directory.

      +

      Only the named users can access the resource.

    • Require group group-name [group-name] ... - +

      Only users in the named groups can access the - directory.

      + resource.

    • - Require valid-user + Require valid-user -

      All valid users can access the directory.

      +

      All valid users can access the resource.

    @@ -2318,7 +2319,7 @@ by Apache children
    top

    RLimitNPROC Directive

    Description:Number of requests allowed on a persistent +
    Description:Number of requests allowed on a persistent connection
    Syntax:MaxKeepAliveRequests number
    Default:MaxKeepAliveRequests 100
    - @@ -2344,12 +2345,14 @@ processes launched by Apache children

    Process limits control the number of processes per user.

    -

    Note: If CGI processes are not running - under userids other than the web server userid, this directive - will limit the number of processes that the server itself can - create. Evidence of this situation will be indicated by - cannot fork messages in the - error_log.

    +

    Note

    +

    If CGI processes are not running + under userids other than the web server userid, this directive + will limit the number of processes that the server itself can + create. Evidence of this situation will be indicated by + cannot fork messages in the + error_log.

    +

    See also

      @@ -2598,7 +2601,7 @@ is accessed by an incompatible browser would want to enable such a footer line is that in a chain of proxies, the user often has no possibility to tell which of the chained servers actually produced a returned error message.
      The Off - setting, which is the default, suppresses the error line (and is + setting, which is the default, suppresses the footer line (and is therefore compatible with the behavior of Apache-1.2 and below). The On setting simply adds a line with the server version number and ServerName of the serving virtual host, @@ -2685,7 +2688,7 @@ handler
    Description:Limits the number of processes that can be launched by +
    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
    Compatibility:Moved into the core in Apache 2.0

    When placed into an .htaccess file or a - <Directory> or + <Directory> or <Location> section, this directive forces all matching files to be parsed through the handler given by @@ -2701,7 +2704,7 @@ handler

    Another example: if you wanted to have the server display a status report whenever a URL of http://servername/status was called, you might put - the following into httpd.conf:

    + the following into httpd.conf:

    <Location /status>
    @@ -2806,7 +2809,7 @@ certain events before failing a request

  • The amount of time between ACKs on transmissions of TCP packets in responses.
    • - +

    We plan on making these separately configurable at some point down the road. The timer used to default to 1200 before 1.2, but has been lowered to 300 which is still far more than @@ -2828,7 +2831,7 @@ port

    In many situations Apache must construct a self-referential URL -- that is, a URL that refers back to the same server. With - UseCanonicalName on Apache will use the hostname and port + UseCanonicalName On Apache will use the hostname and port specified in the ServerName directive to construct the canonical name for the server. This name is used in all self-referential URLs, and for the values of @@ -2839,7 +2842,7 @@ port the client if any are supplied (otherwise it will use the canonical name, as defined above). These values are the same that are used to implement name based virtual hosts, - and are available with the same clients. The CGI variables + and are available with the same clients. The CGI variables SERVER_NAME and SERVER_PORT will be constructed from the client supplied values as well.

    @@ -2864,7 +2867,7 @@ port reverse DNS lookup on the server IP address that the client connected to in order to work out self-referential URLs.

    -

    Warning:

    +

    Warning

    If CGIs make assumptions about the values of SERVER_NAME they may be broken by this option. The client is essentially free to give whatever value they want as a hostname. But if the CGI is @@ -2911,7 +2914,7 @@ hostname or IP address

  • The string _default_, which is used only with IP virtual hosting to catch unmatched IP addresses.
    • - +

    Example

    <VirtualHost 10.1.2.3>
    @@ -2924,7 +2927,7 @@ hostname or IP address </VirtualHost>

    - +

    IPv6 addresses must be specified in square brackets because the optional port number could not be determined otherwise. An IPv6 example is shown below:

    @@ -2939,14 +2942,14 @@ hostname or IP address TransferLog logs/host.example.com-access_log
    </VirtualHost> -

    +

    Each Virtual Host must correspond to a different IP address, different port number or a different host name for the server, in the former case the server machine must be configured to accept IP packets for multiple addresses. (If the machine does not have multiple network interfaces, then this can be - accomplished with the ifconfig alias command (if + accomplished with the ifconfig alias command -- if your OS supports it).

    Note

    @@ -2989,10 +2992,9 @@ hostname or IP address Apache
  • Setting which addresses and ports Apache uses
    • -
  • How - Directory, Location and Files sections work for an - explanation of how these different sections are combined when a - request is received
    • +
  • How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received
    • diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml index 78e7e6f222..1705f4478d 100644 --- a/docs/manual/mod/core.xml +++ b/docs/manual/mod/core.xml @@ -10,7 +10,7 @@ available AcceptPathInfo -Resources accept trailing pathname information +Resources accept trailing pathname information AcceptPathInfo On|Off|Default AcceptPathInfo Default server config @@ -90,7 +90,7 @@ available -

    When returning a document to the client the server looks for +

    While processing a request the server looks for the first existing configuration file from this list of names in every directory of the path to the document, if distributed configuration files are enabled for that directory. For @@ -193,7 +193,7 @@ response without an explicit character set </Location> - Note: + Note

    Enabling filters with AddOutputFilterByType may fail partially or completely in some cases. For expample, no filters are applied if the content type falls back to the AllowOverride Types of directives that are allowed in -.htaccess files +.htaccess files AllowOverride All|None|directive-type [directive-type] ... AllowOverride All @@ -230,7 +230,7 @@ response without an explicit character set it needs to know which directives declared in that file can override earlier access information.

    - Only available in Directory sections + Only available in <Directory> sections AllowOverride is valid only in Directory sections, not in module="mod_authn_dbm">AuthDBMGroupFile, AuthDBMUserFile, AuthGroupFile, - AuthName, + AuthName, AuthType, AuthUserFile, Require, etc.). @@ -275,7 +275,7 @@ response without an explicit character set module="mod_negotiation">LanguagePriority, SetHandler, SetInputFilter, SetOutputFilter, and + module="core">SetOutputFilter, and mod_mime Add* and Remove* directives, etc.). @@ -356,8 +356,8 @@ authentication

    The string provided for the AuthName is what will appear in the password dialog provided by most browsers.

     -Authentication, Authorization, and +Authentication, Authorization, and Access Control     @@ -372,7 +372,7 @@ authentication

    This directive selects the type of user authentication for a directory. Only Basic and Digest are - currently implemented. + currently implemented. It must be accompanied by AuthName and

    This directive is used to control how Apache finds the interpreter used to run CGI scripts. For example, setting CGIMapExtension sys:\foo.nlm .foo will - cause all CGI script files with a .foo extension to be passed to the - FOO interpreter.

    + cause all CGI script files with a .foo extension to + be passed to the FOO interpreter.

     ContentDigest -Enables the generation of Content-MD5 HTTP Response +Enables the generation of Content-MD5 HTTP Response headers ContentDigest On|Off ContentDigest Off @@ -478,7 +478,7 @@ server cannot determine a type in any other way module="core">ForceType, this directive is only provides the default mime-type. All other mime-type definitions, including filename extensions, that might identify the media type - will override this default.

    + will override this default.

     @@ -534,7 +534,8 @@ named file-system directory and sub-directories

    would match directories in /www/ that consisted of three numbers.

    -

    If multiple (non-regular expression) directory sections +

    If multiple (non-regular expression) Directory sections match the directory (or its parents) containing a document, then the directives are applied in the order of shortest match first, interspersed with the directives from the

  • Apply directive AllowOverride FileInfo (for directory /home/web).
    • -
  • Apply any FileInfo directives in +
  • Apply any FileInfo directives in /home/web/.htaccess
    • @@ -582,7 +583,7 @@ named file-system directory and sub-directories </Directory> -

    The regular expression section won't be considered until after +

    the regular expression section won't be considered until after all normal <Directory>s and .htaccess files have been applied. Then the regular expression will match on /home/abc/public_html/abc and be applied.

    @@ -613,15 +614,15 @@ named file-system directory and sub-directories type="section">Limit or LimitExcept section.

    -    How - Directory, Location and Files sections work for an +How <Directory>, + <Location> and <Files> sections work for an explanation of how these different sections are combined when a request is received DirectoryMatch -Enclose directives that apply to +Enclose directives that apply to file-system directories matching a regular expression and their subdirectories <DirectoryMatch regex> @@ -646,11 +647,11 @@ subdirectories Directory for a description of how regular expressions are mixed in with normal -<Directory>s +Directorys How Directory, Location and Files sections -work for an explanation of how these different sections are -combined when a request is received +href="../sections.html">How <Directory>, <Location> and +<Files> sections work for an explanation of how these different +sections are combined when a request is received @@ -727,7 +728,9 @@ Location <Directory "/path-to-nfs-files"> - EnableMMAP Off + + EnableMMAP Off + </Directory> @@ -754,17 +757,17 @@ Location

    This sendfile mechanism avoids seperate read and send operations, and buffer allocations. But on some platforms or within some - filesystems, it is better to disable this feature to avoid + filesystems, it is better to disable this feature to avoid operational problems:

    • Some platforms may have broken sendfile support that the build system did not detect, especially if the binaries were built on another box and moved to such a machine with broken sendfile - support.
      • + support.
    • With a network-mounted DocumentRoot (e.g., NFS or SMB), - the kernel may be unable to serve the network file through + module="core">DocumentRoot (e.g., NFS or SMB), + the kernel may be unable to serve the network file through its own cache.
    @@ -779,8 +782,10 @@ Location for the offending files by specifying:

    - <Directory "/path-to-nfs-files">
    - EnableSendfile Off
    + <Directory "/path-to-nfs-files"> + + EnableSendfile Off + </Directory>     @@ -844,7 +849,7 @@ in case of an error URL in an ErrorDocument 401, the client will not know to prompt the user for a password since it will not receive the 401 status code. Therefore, if you use an - "ErrorDocument 401" directive then it must refer to a local + ErrorDocument 401 directive then it must refer to a local document.

    Microsoft Internet Explorer (MSIE) will by default ignore @@ -867,9 +872,9 @@ in case of an error ErrorLog -Location where the server will log errors +Location where the server will log errors ErrorLog file-path|syslog[:facility] -ErrorLog logs/error_log (Unix) +ErrorLog logs/error_log (Unix)
    ErrorLog logs/error.log (Windows and OS/2)     server configvirtual host @@ -884,7 +889,7 @@ ErrorLog logs/error.log (Windows and OS/2)     Example ErrorLog /var/log/httpd/error_log - +

    If the file-path begins with a pipe (|) then it is assumed to be a command to spawn to handle the error log.

    @@ -1008,9 +1013,9 @@ filenames <Files ~ "\.(gif|jpe?g|png)$"> -

    would match most common Internet graphics formats. In Apache 1.3 - and later, FilesMatch is preferred, however.

    +

    would match most common Internet graphics formats. FilesMatch is preferred, + however.

    Note that unlike Directory and their own files, at a file-by-file level.

    -How - Directory, Location and Files sections work for an - explanation of how these different sections are combined when a - request is received +How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received     @@ -1048,11 +1052,9 @@ filenames

    would match most common Internet graphics formats.

    - -How - Directory, Location and Files sections work for an - explanation of how these different sections are combined when a - request is received +How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received     @@ -1117,7 +1119,7 @@ MIME content-type

    This directive enables DNS lookups so that host names can be logged (and passed to CGIs/SSIs in REMOTE_HOST). The value Double refers to doing double-reverse - DNS. That is, after a reverse lookup is performed, a forward + DNS lookup. That is, after a reverse lookup is performed, a forward lookup is then performed on that result. At least one of the ip addresses in the forward lookup must match the original address. (In "tcpwrappers" terminology this is called @@ -1140,9 +1142,9 @@ MIME content-type Heavily loaded sites should leave this directive Off, since DNS lookups can take considerable amounts of time. The utility logresolve, provided in - the /support directory, can be used to look up host - names from logged IP addresses offline.

    + href="../programs/logresolve.html">logresolve, compiled by default + to the bin subdirectory of your installation directory, can + be used to look up host names from logged IP addresses offline.

     @@ -1233,7 +1235,7 @@ if a test is true at startup Encloses directives that are processed conditional on the presence or absence of a specific module <IfModule [!]module-name> ... - </IfModule> + </IfModule> server configvirtual host directory.htaccess @@ -1306,7 +1308,7 @@ the server configuration files fail.

    The file path specified may be a fully qualified path (i.e. - starting with a slash), or may be relative to the + starting with a slash), or may be relative to the ServerRoot directory.

    Examples:

    @@ -1354,8 +1356,8 @@ the server configuration files which allow multiple requests to be sent over the same TCP connection. In some cases this has been shown to result in an almost 50% speedup in latency times for HTML documents with - many images. To enable Keep-Alive connections in Apache 1.2 and - later, set KeepAlive On.

    + many images. To enable Keep-Alive connections, set + KeepAlive On.

    For HTTP/1.0 clients, Keep-Alive connections will only be used if they are specifically requested by a client. In @@ -1398,7 +1400,7 @@ requests on a persistent connection Limit Restrict enclosed access controls to only certain HTTP -methods +methods <Limit method [method] ... > ... </Limit> server configvirtual host @@ -1416,11 +1418,11 @@ methods

    The purpose of the Limit directive is to restrict the effect of the access controls to the nominated HTTP methods. For all other methods, the access - restrictions that are enclosed in the <Limit> - bracket will have no effect. The following - example applies the access control only to the methods POST, - PUT, and DELETE, leaving all other methods - unprotected:

    + restrictions that are enclosed in the Limit bracket will have no + effect. The following example applies the access control + only to the methods POST, PUT, and + DELETE, leaving all other methods unprotected:

    <Limit POST PUT DELETE>
    @@ -1444,7 +1446,7 @@ methods LimitExcept Restrict access controls to all HTTP methods -except the named ones +except the named ones <LimitExcept method [method] ... > ... </LimitExcept> server configvirtual host @@ -1456,7 +1458,7 @@ except the named ones

    LimitExcept and </LimitExcept> are used to enclose a group of access control directives which will then apply to any - HTTP access method not listed in the arguments; + HTTP access method not listed in the arguments; i.e., it is the opposite of a Limit section and can be used to control both standard and nonstandard/unrecognized methods. See the @@ -1502,8 +1504,8 @@ from the client response instead of servicing the request. The size of a normal request message body will vary greatly depending on the nature of the resource and the methods allowed on that resource. CGI scripts - typically use the message body for passing form information to the - server. Implementations of the PUT method will require + typically use the message body for retrieving form information. + Implementations of the PUT method will require a value at least as large as any representation that the server wishes to accept for that resource.

    @@ -1513,7 +1515,7 @@ from the client attacks.

    If, for example, you are permitting file upload to a particular - location, and wich to limit the size of the uploaded file to 100K, + location, and wish to limit the size of the uploaded file to 100K, you might use the following directive:

    @@ -1525,7 +1527,7 @@ from the client LimitRequestFields -Limits the number of HTTP request header fields that +Limits the number of HTTP request header fields that will be accepted from the client LimitRequestFields number LimitRequestFields 100 @@ -1579,7 +1581,7 @@ client distributed) that will be allowed in an HTTP request header.

    -

    The LimitRequestFieldsize directive +

    The LimitRequestFieldSize directive allows the server administrator to reduce the limit on the allowed size of an HTTP request header field below the normal input buffer size compiled with the server. A server needs this value to be @@ -1648,7 +1650,7 @@ from the client LimitXMLRequestBody Limits the size of an XML-based request body -LimitXMLRequestBody number +LimitXMLRequestBody bytes LimitXMLRequestBody 1000000 server configvirtual host directory.htaccess @@ -1689,8 +1691,9 @@ URLs type="section" module="core">Files sections.

    Note that URLs do not have to line up with the filesystem at - all, it should be emphasized that <Location> operates - completely outside the filesystem.

    + all, it should be emphasized that Location operates completely + outside the filesystem.

    For all origin (non-proxy) requests, the URL to be matched is a URL-path of the form /path/. No scheme, hostname, @@ -1699,7 +1702,7 @@ URLs scheme://servername/path, and you must include the prefix.

    -

    The URL may use wildcards In a wild-card string, ? matches +

    The URL may use wildcards. In a wild-card string, ? matches any single character, and * matches any sequences of characters.

    @@ -1712,10 +1715,10 @@ URLs

    would match URLs that contained the substring /extra/data - or /special/data. In Apache 1.3 and above, a new directive - LocationMatch - exists which behaves identical to the regex version of - Location.

    + or /special/data. The directive LocationMatch behaves + identical to the regex version of Location.

    The Location functionality is especially useful when combined with the @@ -1744,7 +1747,7 @@ URLs directive and the regex version of Location require you to explicitly specify multiple slashes if that is your intention.

    - +

    For example, <LocationMatch ^/abc> would match the request URL /abc but not the request URL //abc. The (non-regex) request is to /abc//def then it will match.

    -How - Directory, Location and Files sections work for an - explanation of how these different sections are combined when a - request is received +How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received     LocationMatch -Applies the enclosed directives only to regular-expression +Applies the enclosed directives only to regular-expression matching URLs <LocationMatch regex> ... </LocationMatch> @@ -1786,10 +1788,9 @@ matching URLs or /special/data.

    -How - Directory, Location and Files sections work for an - explanation of how these different sections are combined when a - request is received +How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received     @@ -1903,7 +1904,7 @@ matching URLs MaxKeepAliveRequests -Number of requests allowed on a persistent +Number of requests allowed on a persistent connection MaxKeepAliveRequests number MaxKeepAliveRequests 100 @@ -1955,11 +1956,14 @@ hosting servicing the requests. If you have multiple name-based hosts on multiple addresses, repeat the directive for each address.

    -

    Note: the "main server" and any _default_ servers will - never be served for a request to a - NameVirtualHost IP Address (unless for some - reason you specify NameVirtualHost but then - don't define any VirtualHosts for that address).

    + Note +

    Note, that the "main server" and any _default_ servers + will never be served for a request to a + NameVirtualHost IP Address (unless for some + reason you specify NameVirtualHost but then + don't define any VirtualHosts for that + address).

    +

    Optionally you can specify a port number on which the name-based virtual hosts should be used, e.g.

    @@ -1982,10 +1986,10 @@ hosting NameVirtualHost *     - Argument to <directive><VirtualHost></directive> + <note><title>Argument to <directive type="section">VirtualHost</directive> directive

    Note that the argument to the <VirtualHost> directive must + type="section">VirtualHost directive must exactly match the argument to the NameVirtualHost directive.

    @@ -2024,17 +2028,17 @@ directory the following:

    -
    All
    +
    All
    All options except for MultiViews. This is the default setting.
    -
    ExecCGI
    +
    ExecCGI
    Execution of CGI scripts is permitted.
    -
    FollowSymLinks
    +
    FollowSymLinks
    @@ -2048,12 +2052,12 @@ directory section.

    -
    Includes
    +
    Includes
    Server-side includes are permitted.
    -
    IncludesNOEXEC
    +
    IncludesNOEXEC
    @@ -2062,7 +2066,7 @@ directory #include virtual CGI scripts from ScriptAliase'd directories.
    -
    Indexes
    +
    Indexes
    If a URL which maps to a directory is requested, and the @@ -2070,13 +2074,13 @@ directory index.html) in that directory, then the server will return a formatted listing of the directory.
    -
    MultiViews
    +
    MultiViews
    Content negotiated "MultiViews" are allowed.
    -
    SymLinksIfOwnerMatch
    +
    SymLinksIfOwnerMatch
    @@ -2135,10 +2139,11 @@ directory Includes are set for the /web/docs/spec directory.

    - -

    Note: Using -IncludesNOEXEC or - -Includes disables server-side includes completely - regardless of the previous setting.

    + Note +

    Using -IncludesNOEXEC or + -Includes disables server-side includes completely + regardless of the previous setting.

    +

    The default in the absence of any other settings is All.

    @@ -2148,7 +2153,7 @@ directory Require Selects which authenticated users can access -a resource +a resource Require entity-name [entity-name] ... directory.htaccess @@ -2160,23 +2165,23 @@ a resource
    • - Require user userid [userid] ... + Require user userid [userid] ... -

      Only the named users can access the directory.

      +

      Only the named users can access the resource.

    • Require group group-name [group-name] ... - +

      Only users in the named groups can access the - directory.

      + resource.

    • - Require valid-user + Require valid-user -

      All valid users can access the directory.

      +

      All valid users can access the resource.

    @@ -2275,7 +2280,7 @@ by Apache children RLimitNPROC -Limits the number of processes that can be launched by +Limits the number of processes that can be launched by processes launched by Apache children RLimitNPROC number|max [number|max] Unset; uses operating system defaults @@ -2301,12 +2306,14 @@ processes launched by Apache children

    Process limits control the number of processes per user.

    -

    Note: If CGI processes are not running - under userids other than the web server userid, this directive - will limit the number of processes that the server itself can - create. Evidence of this situation will be indicated by - cannot fork messages in the - error_log.

    + Note +

    If CGI processes are not running + under userids other than the web server userid, this directive + will limit the number of processes that the server itself can + create. Evidence of this situation will be indicated by + cannot fork messages in the + error_log.

    +     RLimitMEM RLimitCPU @@ -2541,7 +2548,7 @@ is accessed by an incompatible browser would want to enable such a footer line is that in a chain of proxies, the user often has no possibility to tell which of the chained servers actually produced a returned error message.
    The Off - setting, which is the default, suppresses the error line (and is + setting, which is the default, suppresses the footer line (and is therefore compatible with the behavior of Apache-1.2 and below). The On setting simply adds a line with the server version number and

    When placed into an .htaccess file or a - Directory or + Directory or Location section, this directive forces all matching files to be parsed through the handler given by @@ -2642,7 +2649,7 @@ handler

    Another example: if you wanted to have the server display a status report whenever a URL of http://servername/status was called, you might put - the following into httpd.conf:

    + the following into httpd.conf:

    <Location /status>
    @@ -2741,7 +2748,7 @@ certain events before failing a request
  • The amount of time between ACKs on transmissions of TCP packets in responses.
    • - +

    We plan on making these separately configurable at some point down the road. The timer used to default to 1200 before 1.2, but has been lowered to 300 which is still far more than @@ -2763,7 +2770,7 @@ port

    In many situations Apache must construct a self-referential URL -- that is, a URL that refers back to the same server. With - UseCanonicalName on Apache will use the hostname and port + UseCanonicalName On Apache will use the hostname and port specified in the ServerName directive to construct the canonical name for the server. This name is used in all self-referential URLs, and for the values of @@ -2773,9 +2780,9 @@ port self-referential URLs using the hostname and port supplied by the client if any are supplied (otherwise it will use the canonical name, as defined above). These values are the same - that are used to implement name based virtual hosts, - and are available with the same clients. The CGI variables + and are available with the same clients. The CGI variables SERVER_NAME and SERVER_PORT will be constructed from the client supplied values as well.

    @@ -2801,7 +2808,7 @@ port reverse DNS lookup on the server IP address that the client connected to in order to work out self-referential URLs.

    - Warning: + Warning

    If CGIs make assumptions about the values of SERVER_NAME they may be broken by this option. The client is essentially free to give whatever value they want as a hostname. But if the CGI is @@ -2816,7 +2823,7 @@ port VirtualHost Contains directives that apply only to a specific -hostname or IP address +hostname or IP address <VirtualHost addr[:port] [addr[:port]] ...> ... </VirtualHost> @@ -2844,7 +2851,7 @@ hostname or IP address

  • The string _default_, which is used only with IP virtual hosting to catch unmatched IP addresses.
    • - + Example <VirtualHost 10.1.2.3>
    @@ -2857,7 +2864,7 @@ hostname or IP address </VirtualHost>     - +

    IPv6 addresses must be specified in square brackets because the optional port number could not be determined otherwise. An IPv6 example is shown below:

    @@ -2872,14 +2879,14 @@ hostname or IP address TransferLog logs/host.example.com-access_log
    </VirtualHost> -     +

    Each Virtual Host must correspond to a different IP address, different port number or a different host name for the server, in the former case the server machine must be configured to accept IP packets for multiple addresses. (If the machine does not have multiple network interfaces, then this can be - accomplished with the ifconfig alias command (if + accomplished with the ifconfig alias command -- if your OS supports it).

    Note @@ -2921,10 +2928,9 @@ hostname or IP address Apache Setting which addresses and ports Apache uses -How - Directory, Location and Files sections work for an - explanation of how these different sections are combined when a - request is received +How <Directory>, <Location> + and <Files> sections work for an explanation of how these + different sections are combined when a request is received     - + \ No newline at end of file -- 2.50.1