From: Rich Bowen Date: Fri, 7 Sep 2001 01:49:03 +0000 (+0000) Subject: Ran w3c tidy with the -asxhtml flag. X-Git-Tag: 2.0.26~301 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=80aa275c73866bc20715d571e4f37f053bc3bbf2;p=apache Ran w3c tidy with the -asxhtml flag. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@90942 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index cb851c764c..a38fa95c4c 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -1,11 +1,16 @@ - + + + - Apache Core Features + + + Apache Core Features - +

Apache Core Features

@@ -74,13 +79,13 @@
  • LimitRequestFields
    • -
  • LimitRequestFieldsize
    • +
  • LimitRequestFieldsize
  • LimitRequestLine
    • -
  • LimitXMLRequestBody
    • +
  • LimitXMLRequestBody
  • <Location>
    • @@ -88,8 +93,8 @@
  • LogLevel
    • -
  • MaxKeepAliveRequests
    • +
  • MaxKeepAliveRequests
  • NameVirtualHost
    • @@ -107,8 +112,8 @@
  • Satisfy
    • -
  • ScriptInterpreterSource
    • +
  • ScriptInterpreterSource
  • ServerAdmin
    • @@ -136,24 +141,25 @@
  • <VirtualHost>
    • -
    +
    -

    AccessFileName directive

    +

    AccessFileName + directive

    - Syntax: AccessFileName - filename [filename] ...
    - Default: AccessFileName - .htaccess
    - Context: server config, virtual - host
    - Status: core
    - Compatibility: AccessFileName can - accept more than one filename only in Apache 1.3 and later + Syntax: AccessFileName + filename [filename] ...
    + Default: AccessFileName + .htaccess
    + Context: server config, virtual + host
    + Status: core
    + Compatibility: AccessFileName + can accept more than one filename only in Apache 1.3 and later

    When returning a document to the client the server looks for the first existing access control file from this list of names @@ -169,30 +175,30 @@ disabled with

    - <Directory />
    - AllowOverride None
    + <Directory />
    + AllowOverride None
    </Directory>
    -

    See Also: AllowOverride

    -
    - -

    AddDefaultCharset - directive

    - Syntax: AddDefaultCharset - On|Off|charset
    - Context: all
    - Status: core
    - Default: AddDefaultCharset - Off
    - Compatibility: AddDefaultCharset is - only available in Apache 1.3.12 and later +

    See Also: AllowOverride

    +
    + +

    AddDefaultCharset directive

    + Syntax: AddDefaultCharset + On|Off|charset
    + Context: all
    + Status: core
    + Default: + AddDefaultCharset Off
    + Compatibility: + AddDefaultCharset is only available in Apache 1.3.12 and later

    This directive specifies the name of the character set that will be added to any response that does not have any parameter @@ -204,41 +210,43 @@ iso-8859-1 as required by the directive. You can also specify an alternate charset to be used; e.g. AddDefaultCharset utf-8.

    -
    +
    -

    AddModule directive

    +

    AddModule + directive

    - Syntax: AddModule module - [module] ...
    - Context: server config
    - Status: core
    - Compatibility: AddModule is only - available in Apache 1.2 and later + Syntax: AddModule + module [module] ...
    + Context: server config
    + Status: core
    + Compatibility: AddModule is + only available in Apache 1.2 and later

    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 - active modules; this list can be cleared with the ClearModuleList directive.

    -
    + active modules; this list can be cleared with the ClearModuleList directive.

    +
    -

    AllowOverride directive

    +

    AllowOverride + directive

    - Syntax: AllowOverride + Syntax: AllowOverride All|None|directive-type [directive-type] - ...
    - Default: AllowOverride - All
    - Context: directory
    - Status: core + ...
    + Default: AllowOverride + All
    + Context: directory
    + Status: core

    When the server finds an .htaccess file (as specified by AccessFileName) it needs to know @@ -251,8 +259,8 @@ filesystem.

    When this directive is set to All, then any - directive which has the .htaccess Context is allowed in + directive which has the .htaccess Context is allowed in .htaccess files.

    The directive-type can be one of the following @@ -263,45 +271,46 @@

    - Allow use of the authorization directives (AuthDBMGroupFile, AuthDBMGroupFile, + AuthDBMUserFile, AuthGroupFile, AuthName, AuthType, AuthUserFile, Require, etc.).
    + href="#authname">AuthName, AuthType, AuthUserFile, Require, etc.).
    FileInfo
    Allow use of the directives controlling document types (DefaultType, ErrorDocument, ForceType, LanguagePriority, - SetHandler, SetInputFilter, SetOutputFilter, and mod_mime Add* and Remove* directives, - etc.).
    + href="#defaulttype">DefaultType, ErrorDocument, ForceType, LanguagePriority, + SetHandler, SetInputFilter, SetOutputFilter, and mod_mime Add* and Remove* + directives, etc.).
    Indexes
    Allow use of the directives controlling directory indexing - (AddDescription, AddIcon, AddIconByEncoding, + (AddDescription, + AddIcon, AddIconByEncoding, AddIconByType, DefaultIcon, DirectoryIndex, FancyIndexing, HeaderName, IndexIgnore, IndexOptions, ReadmeName, + href="mod_autoindex.html#headername">HeaderName, IndexIgnore, IndexOptions, ReadmeName, etc.).
    Limit
    @@ -314,25 +323,27 @@
    Allow use of the directives controlling specific directory - features (Options and XBitHack).
    + features (Options and XBitHack). -

    See Also: AccessFileName

    -
    +

    See Also: AccessFileName

    +
    -

    AuthName directive

    +

    AuthName + directive

    - Syntax: AuthName - auth-domain
    - Context: directory, .htaccess
    - Override: AuthConfig
    - Status: core + Syntax: AuthName + auth-domain
    + Context: directory, + .htaccess
    + Override: AuthConfig
    + Status: core

    This directive sets the name of the authorization realm for a directory. This realm is given to the client so that the user @@ -344,18 +355,21 @@ as AuthUserFile and AuthGroupFile to work.

    -
    +
    -

    AuthType directive

    +

    AuthType + directive

    - Syntax: AuthType Basic|Digest
    - Context: directory, .htaccess
    - Override: AuthConfig
    - Status: core + Syntax: AuthType + Basic|Digest
    + Context: directory, + .htaccess
    + Override: AuthConfig
    + Status: core

    This directive selects the type of user authentication for a directory. Only Basic and Digest are @@ -366,43 +380,45 @@ as AuthUserFile and AuthGroupFile to work.

    -
    +
    -

    ClearModuleList - directive

    +

    ClearModuleList directive

    - Syntax: ClearModuleList
    - Context: server config
    - Status: core
    - Compatibility: ClearModuleList is - only available in Apache 1.2 and later + Syntax: ClearModuleList
    + Context: server config
    + Status: core
    + Compatibility: ClearModuleList + is only available in Apache 1.2 and later

    The server comes with a built-in list of active modules. This directive clears the list. It is assumed that the list - will then be re-populated using the AddModule directive.

    -
    + will then be re-populated using the AddModule directive.

    +
    -

    ContentDigest directive

    +

    ContentDigest + directive

    - Syntax: ContentDigest on|off
    - Default: ContentDigest - off
    - Context: server config, virtual - host, directory, .htaccess
    - Override: Options
    - Status: experimental
    - Compatibility: ContentDigest is + Syntax: ContentDigest + on|off
    + Default: ContentDigest + off
    + Context: server config, virtual + host, directory, .htaccess
    + Override: Options
    + Status: experimental
    + Compatibility: ContentDigest is only available in Apache 1.1 and later

    This directive enables the generation of @@ -430,23 +446,24 @@ 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

    +

    DefaultType + directive

    - Syntax: DefaultType - MIME-type
    - Default: DefaultType - text/html
    - Context: server config, virtual - host, directory, .htaccess
    - Override: FileInfo
    - Status: core + Syntax: DefaultType + MIME-type
    + Default: DefaultType + text/html
    + Context: server config, virtual + host, directory, .htaccess
    + Override: FileInfo
    + Status: core

    There will be times when the server is asked to provide a document whose type cannot be determined by its MIME types @@ -466,18 +483,19 @@ 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.

    -
    +
    -

    <Directory> directive

    +

    <Directory> + directive

    - Syntax: <Directory - directory-path> ... </Directory>
    - Context: server config, virtual - host
    - Status: Core. + Syntax: <Directory + directory-path> ... </Directory>
    + Context: server config, virtual + host
    + Status: Core.

    <Directory> and </Directory> are used to enclose a group of directives which will apply only to the named @@ -488,8 +506,8 @@ single character, and `*' matches any sequences of characters. As of Apache 1.3, you may also use `[]' character ranges like in the shell. Also as of Apache 1.3 none of the wildcards match - a `/' character, which more closely mimics the behavior of - Unix shells. Example:

    + a `/' character, which more closely mimics the behavior of Unix + shells. Example:

        <Directory /usr/local/httpd/htdocs>
    Options Indexes FollowSymLinks
@@ -508,16 +526,17 @@
     
    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, with
    
+    first, interspersed with the directives from the .htaccess files. For example,
+    with
    
 
     
    
-      <Directory />
    
-       AllowOverride None
    
-       </Directory>
    
-      
    
-       <Directory /home/*>
    
-       AllowOverride FileInfo
    
+      <Directory />
    
+       AllowOverride None
    
+       </Directory>
    
+      
    
+       <Directory /home/*>
    
+       AllowOverride FileInfo
    
        </Directory>    
     
    
     for access to the document /home/web/dir/doc.html
@@ -545,9 +564,9 @@
     appeared in the configuration file. For example, with
    
 
     
    
-      <Directory ~ abc$>
    
-       ... directives here ...
    
-       </Directory>
    
+      <Directory ~ abc$>
    
+       ... directives here ...
    
+       </Directory>
    
           
     
    
     Suppose that the filename being accessed is
@@ -576,33 +595,34 @@

    and then override this for directories you - want accessible. See the Security Tips page for more - details.

    + want accessible. See the Security Tips page for + more details.

    The directory sections typically occur in the access.conf file, but they may appear in any configuration file. <Directory> directives cannot nest, and cannot appear in - a <Limit> or <LimitExcept> section. + a <Limit> or <LimitExcept> section.

    See also: How Directory, Location and Files sections work for an explanation of how these different sections are combined when a request is received

    -
    - -

    <DirectoryMatch>

    - Syntax: <DirectoryMatch - regex> ... </DirectoryMatch>
    - Context: server config, virtual - host
    - Status: Core.
    - Compatibility: Available in Apache - 1.3 and later +
    + +

    <DirectoryMatch>

    + Syntax: <DirectoryMatch + regex> ... </DirectoryMatch>
    + Context: server config, virtual + host
    + Status: Core.
    + Compatibility: Available in + Apache 1.3 and later

    <DirectoryMatch> and </DirectoryMatch> are used to enclose a group of directives which will apply only to the @@ -616,29 +636,30 @@

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

    -

    See Also: <Directory> for a description of how - regular expressions are mixed in with normal - <Directory>s.
    +

    See Also: <Directory> for a description of + how regular expressions are mixed in with normal + <Directory>s.
    See also: How Directory, Location and Files sections work for an explanation of how these different sections are combined when a request is received

    -
    +
    -

    DocumentRoot directive

    +

    DocumentRoot + directive

    - Syntax: DocumentRoot - directory-path
    - Default: DocumentRoot - /usr/local/apache/htdocs
    - Context: server config, virtual - host
    - Status: core + Syntax: DocumentRoot + directory-path
    + Default: DocumentRoot + /usr/local/apache/htdocs
    + Context: server config, virtual + host
    + Status: core

    This directive sets the directory from which httpd will serve files. Unless matched by a directive like Alias, the @@ -655,24 +676,25 @@

    There appears to be a bug in mod_dir which causes problems when the DocumentRoot has a trailing slash (i.e., "DocumentRoot /usr/web/") so please avoid that.

    -
    +
    -

    ErrorDocument directive

    +

    ErrorDocument + directive

    - Syntax: ErrorDocument - error-code document
    - Context: server config, virtual - host, directory, .htaccess
    - Status: core
    - Override: FileInfo
    - Compatibility: The directory and - .htaccess contexts are only available in Apache 1.1 and later. - The quoting syntax prior to Apache 2.0 was different. + Syntax: ErrorDocument + error-code document
    + Context: server config, virtual + host, directory, .htaccess
    + Status: core
    + Override: FileInfo
    + Compatibility: The directory + and .htaccess contexts are only available in Apache 1.1 and + later. The quoting syntax prior to Apache 2.0 was different.

    In the event of a problem or error, Apache can be configured to do one of four things,

    @@ -701,9 +723,9 @@
    ErrorDocument 500 - http://foo.example.com/cgi-bin/tester
    - ErrorDocument 404 /cgi-bin/bad_urls.pl
    - ErrorDocument 401 /subscription_info.html
    + http://foo.example.com/cgi-bin/tester
    + ErrorDocument 404 /cgi-bin/bad_urls.pl
    + ErrorDocument 401 /subscription_info.html
    ErrorDocument 403 "Sorry can't allow you access today"
    @@ -729,32 +751,33 @@

    See Also: documentation of customizable responses.

    -
    +
    -

    ErrorLog directive

    +

    ErrorLog + directive

    - Syntax: ErrorLog - file-path|syslog[:facility]
    - Default: ErrorLog - logs/error_log (Unix)
    - Default: ErrorLog - logs/error.log (Windows and OS/2)
    - Context: server config, virtual - host
    - Status: core + Syntax: ErrorLog + file-path|syslog[:facility]
    + Default: ErrorLog + logs/error_log (Unix)
    + Default: ErrorLog + logs/error.log (Windows and OS/2)
    + Context: server config, virtual + host
    + Status: core

    The error log 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 - assumed to be relative to the ServerRoot. If the file-path begins - with a pipe (|) then it is assumed to be a command to spawn to - handle the error log.

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

    Apache 1.3 and above: Using syslog instead of a filename enables logging via @@ -764,33 +787,33 @@ facility can be one of the names usually documented in syslog(1).

    -

    SECURITY: See the security tips +

    SECURITY: See the security tips document for details on why your security could be compromised if the directory where logfiles are stored is writable by anyone other than the user that starts the server.

    See also: LogLevel and Apache Log Files

    -
    - -

    <Files> directive

    - Syntax: <Files - filename> ... </Files>
    - Context: server config, virtual - host, .htaccess
    - Status: core
    - Compatibility: only available in - Apache 1.2 and above. +
    + +

    <Files> directive

    + Syntax: <Files + filename> ... </Files>
    + Context: server config, virtual + host, .htaccess
    + Status: core
    + Compatibility: only available + in Apache 1.2 and above.

    The <Files> directive provides for access control by - filename. It is comparable to the <Directory> directive and <Location> directives. It should be + filename. It is comparable to the <Directory> directive and <Location> directives. It should be matched with a </Files> directive. The directives given within this section will be applied to any object with a basename (last component of filename) matching the specified @@ -813,9 +836,9 @@ 1.3 and later, <FilesMatch> is preferred, however. -

    Note that unlike <Directory> and <Location> sections, +

    Note that unlike <Directory> and <Location> sections, <Files> sections can be used inside .htaccess files. This allows users to control access to their own files, at a file-by-file level.

    @@ -824,20 +847,21 @@ Directory, Location and Files sections work for an explanation of how these different sections are combined when a request is received

    -
    - -

    <FilesMatch>

    - Syntax: <FilesMatch - regex> ... </FilesMatch>
    - Context: server config, virtual - host, .htaccess
    - Status: core
    - Compatibility: only available in - Apache 1.3 and above. +
    + +

    <FilesMatch>

    + Syntax: <FilesMatch + regex> ... </FilesMatch>
    + Context: server config, virtual + host, .htaccess
    + Status: core
    + Compatibility: only available + in Apache 1.3 and above.

    The <FilesMatch> directive provides for access control by filename, just as the <Files> @@ -852,20 +876,22 @@ Directory, Location and Files sections work for an explanation of how these different sections are combined when a request is received -

    - -

    ForceType directive

    - Syntax: ForceType - mime-type
    - Context: directory, .htaccess
    - Status: Base
    - Module: core
    - Compatibility: ForceType was +
    + +

    ForceType + directive

    + Syntax: ForceType + mime-type
    + Context: directory, + .htaccess
    + Status: Base
    + Module: core
    + Compatibility: ForceType was introduced in mod_mime with Apache 1.1, and moved to the core in Apache 2.0. @@ -884,27 +910,28 @@

    Note that unlike DefaultType, this directive overrides all mime-type associations, including filename extensions, that might identify the media type.

    -
    +
    -

    HostNameLookups - directive

    +

    HostNameLookups directive

    - Syntax: HostNameLookups - on|off|double
    - Default: HostNameLookups - off
    - Context: server config, virtual - host, directory
    - Status: core
    - Compatibility: double - available only in Apache 1.3 and above.
    - Compatibility: Default was + Syntax: HostNameLookups + on|off|double
    + Default: HostNameLookups + off
    + Context: server config, virtual + host, directory
    + Status: core
    + Compatibility: + double available only in Apache 1.3 and + above.
    + Compatibility: Default was on prior to Apache 1.3.

    This directive enables DNS lookups so that host names can be @@ -916,10 +943,10 @@ address. (In "tcpwrappers" terminology this is called PARANOID.)

    -

    Regardless of the setting, when mod_access is used for controlling access - by hostname, a double reverse lookup will be performed. This is - necessary for security. Note that the result of this +

    Regardless of the setting, when mod_access is used for controlling + access by hostname, a double reverse lookup will be performed. + This is necessary for security. Note that the result of this double-reverse isn't generally available unless you set HostnameLookups double. For example, if only HostnameLookups on and a request is made to an @@ -936,24 +963,26 @@ 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, provided in + the /support directory, can be used to look up host + names from logged IP addresses offline.

    +
    -

    IdentityCheck directive

    +

    IdentityCheck + directive

    - Syntax: IdentityCheck on|off
    - Default: IdentityCheck - off
    - Context: server config, virtual - host, directory
    - Status: core + Syntax: IdentityCheck + on|off
    + Default: IdentityCheck + off
    + Context: server config, virtual + host, directory
    + Status: core

    This directive enables RFC1413-compliant logging of the remote user name for each connection, where the client machine @@ -970,22 +999,23 @@ 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

    - Syntax: <IfDefine +

    <IfDefine> + directive

    + Syntax: <IfDefine [!]parameter-name> ... - </IfDefine>
    - Default: None
    - Context: all
    - Status: Core
    - Compatibility: <IfDefine> is - only available in 1.3.1 and later. + </IfDefine>
    + Default: None
    + Context: all
    + Status: Core
    + Compatibility: <IfDefine> + is only available in 1.3.1 and later.

    The <IfDefine test>...</IfDefine> section is used to mark directives that are conditional. The @@ -1024,20 +1054,22 @@ LoadModule proxy_module modules/libproxy.so </IfDefine> -

    - -

    <IfModule> directive

    - Syntax: <IfModule - [!]module-name> ... </IfModule>
    - Default: None
    - Context: all
    - Status: Core
    - Compatibility: IfModule is only +
    + +

    <IfModule> + directive

    + Syntax: <IfModule + [!]module-name> ... + </IfModule>
    + Default: None
    + Context: all
    + Status: Core
    + Compatibility: IfModule is only available in 1.2 and later.

    The <IfModule test>...</IfModule> @@ -1067,17 +1099,17 @@

    <IfModule> sections are nest-able, which can be used to implement simple multiple-module tests.

    -
    +
    -

    Include directive

    +

    Include directive

    Syntax: Include - file-path|directory-path
    - Context: server config
    - Status: Core
    - Compatibility: Include is only + file-path|directory-path
    + Context: server config
    + Status: Core
    + Compatibility: Include is only available in Apache 1.3 and later.

    This directive allows inclusion of other configuration files @@ -1086,18 +1118,19 @@

    If Include points to a directory, rather than a file, Apache will read all files in that directory, and any subdirectory, and parse those as configuration files.

    -
    - -

    KeepAlive directive

    - Syntax: KeepAlive on/off
    - Default: KeepAlive On
    - Context: server config
    - Status: Core
    - Compatibility: KeepAlive is only - available in Apache 1.1 and later. +
    + +

    KeepAlive + directive

    + Syntax: KeepAlive on/off
    + Default: KeepAlive On
    + Context: server config
    + Status: Core
    + Compatibility: KeepAlive is + only available in Apache 1.1 and later.

    The Keep-Alive extension to HTTP/1.0 and the persistent connection feature of HTTP/1.1 provide long-lived HTTP sessions @@ -1119,46 +1152,47 @@ encoding will be used in order to send content of unknown length over persistent connections.

    -

    See also MaxKeepAliveRequests.

    -
    - -

    KeepAliveTimeout - directive

    - Syntax: KeepAliveTimeout - seconds
    - Default: KeepAliveTimeout - 15
    - Context: server config
    - Status: Core
    - Compatibility: KeepAliveTimeout is - only available in Apache 1.1 and later. +

    See also MaxKeepAliveRequests.

    +
    + +

    KeepAliveTimeout directive

    + Syntax: KeepAliveTimeout + seconds
    + Default: KeepAliveTimeout + 15
    + Context: server config
    + Status: Core
    + Compatibility: KeepAliveTimeout + is only available in Apache 1.1 and later.

    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 Timeout directive applies.

    + received, the timeout value specified by the Timeout directive applies.

    Setting KeepAliveTimeout to a high value 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.

    -
    +
    -

    <Limit> directive

    +

    <Limit> directive

    - Syntax: <Limit method - [method] ... > ... </Limit>
    - Context: any
    - Status: core + Syntax: <Limit + method [method] ... > ... + </Limit>
    + Context: any
    + Status: core

    Access controls are normally effective for all access methods, and this is the usual @@ -1175,8 +1209,8 @@ other methods unprotected:

    - <Limit POST PUT DELETE>
    - Require valid-user
    + <Limit POST PUT DELETE>
    + Require valid-user
    </Limit>
    The method names listed can be one or more of: GET, POST, PUT, @@ -1184,50 +1218,50 @@ MKCOL, COPY, MOVE, LOCK, and UNLOCK. The method name is case-sensitive. If GET is used it will also restrict HEAD requests. -
    +
    -

    <LimitExcept> +

    <LimitExcept> directive

    - Syntax: <LimitExcept + Syntax: <LimitExcept method [method] ... > ... - </LimitExcept>
    - Context: any
    - Status: core
    - Compatibility: Available in Apache - 1.3.5 and later + </LimitExcept>
    + Context: any
    + Status: core
    + Compatibility: Available in + Apache 1.3.5 and later

    <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; 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.

    -
    - -

    LimitRequestBody - directive

    + 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.

    +
    + +

    LimitRequestBody directive

    - Syntax: LimitRequestBody - bytes
    - Default: LimitRequestBody - 0
    - Context: server config, virtual - host, directory, .htaccess
    - Status: core
    - Compatibility: LimitRequestBody is - only available in Apache 1.3.2 and later. + Syntax: LimitRequestBody + bytes
    + Default: LimitRequestBody + 0
    + Context: server config, virtual + host, directory, .htaccess
    + Status: core
    + Compatibility: LimitRequestBody + is only available in Apache 1.3.2 and later.

    This directive specifies the number of bytes from 0 (meaning unlimited) to 2147483647 (2GB) that are allowed in a @@ -1252,24 +1286,25 @@ control over abnormal client request behavior, which may be useful for avoiding some forms of denial-of-service attacks.

    -
    +
    -

    LimitRequestFields - directive

    +

    LimitRequestFields directive

    - Syntax: LimitRequestFields - number
    - Default: LimitRequestFields - 100
    - Context: server config
    - Status: core
    - Compatibility: LimitRequestFields - is only available in Apache 1.3.2 and later. + Syntax: LimitRequestFields + number
    + Default: + LimitRequestFields 100
    + Context: server config
    + Status: core
    + Compatibility: + LimitRequestFields is only available in Apache 1.3.2 and later. +

    Number is an integer from 0 (meaning unlimited) to 32767. The default value is defined by the compile-time @@ -1293,23 +1328,24 @@ The value should be increased if normal clients see an error response from the server that indicates too many fields were sent in the request.

    -
    +
    -

    LimitRequestFieldsize +

    LimitRequestFieldsize directive

    - Syntax: LimitRequestFieldsize - bytes
    - Default: - LimitRequestFieldsize 8190
    - Context: server config
    - Status: core
    - Compatibility: + Syntax: LimitRequestFieldsize + bytes
    + Default: + LimitRequestFieldsize 8190
    + Context: server config
    + Status: core
    + Compatibility: LimitRequestFieldsize is only available in Apache 1.3.2 and later. @@ -1334,24 +1370,24 @@ useful for avoiding some forms of denial-of-service attacks. Under normal conditions, the value should not be changed from the default.

    -
    +
    -

    LimitRequestLine - directive

    +

    LimitRequestLine directive

    - Syntax: LimitRequestLine - bytes
    - Default: LimitRequestLine - 8190
    - Context: server config
    - Status: core
    - Compatibility: LimitRequestLine is - only available in Apache 1.3.2 and later. + Syntax: LimitRequestLine + bytes
    + Default: LimitRequestLine + 8190
    + Context: server config
    + Status: core
    + Compatibility: LimitRequestLine + is only available in Apache 1.3.2 and later.

    This directive sets the number of bytes from 0 to the value of the compile-time constant @@ -1374,42 +1410,44 @@ useful for avoiding some forms of denial-of-service attacks. Under normal conditions, the value should not be changed from the default.

    -
    +
    -

    LimitXMLRequestBody +

    LimitXMLRequestBody directive

    - Syntax: LimitXMLRequestBody - number
    - Default: LimitXMLRequestBody - 1000000
    - Context: server config
    - Status: core
    + Syntax: LimitXMLRequestBody + number
    + Default: + LimitXMLRequestBody 1000000
    + Context: server config
    + Status: core

    Limit (in bytes) on maximum size of an XML-based request body.

    -
    - -

    <Location> directive

    - Syntax: <Location - URL-path|URL> ... </Location>
    - Context: server config, virtual - host
    - Status: core
    - Compatibility: Location is only +
    + +

    <Location> + directive

    + Syntax: <Location + URL-path|URL> ... </Location>
    + Context: server config, virtual + host
    + Status: core
    + Compatibility: Location is only available in Apache 1.1 and later.

    The <Location> directive provides for access control - by URL. It is similar to the <Directory> directive, and starts a + by URL. It is similar to the <Directory> directive, and starts a subsection which is terminated with a </Location> directive. <Location> sections are processed in the order they appear in the configuration file, after the @@ -1445,10 +1483,10 @@ <Location>.

    The Location functionality is especially useful - when combined with the SetHandler directive. For - example, to enable status requests, but allow them only from - browsers at foo.com, you might use:

    + when combined with the SetHandler + directive. For example, to enable status requests, but allow + them only from browsers at foo.com, you might use:

         <Location /status>
     SetHandler server-status
@@ -1483,26 +1521,27 @@
     Directory, Location and Files sections work for an
     explanation of how these different sections are combined when a
     request is received
    
-    
    
-
-    
    <LocationMatch>
    
-    Syntax: <LocationMatch
-    regex> ... </LocationMatch>
    
-     Context: server config, virtual
-    host
    
-     Status: core
    
-     Compatibility: LocationMatch is
+    
    
+
+    
    <LocationMatch>
    
+    Syntax: <LocationMatch
+    regex> ... </LocationMatch>
    
+     Context: server config, virtual
+    host
    
+     Status: core
    
+     Compatibility: LocationMatch is
     only available in Apache 1.3 and later. 
 
     
    The <LocationMatch> directive provides for access
-    control by URL, in an identical manner to <Location>. However, it takes a regular
-    expression as an argument instead of a simple string. For
-    example:
    
+    control by URL, in an identical manner to <Location>. However, it takes a
+    regular expression as an argument instead of a simple string.
+    For example:
    
 
        <LocationMatch "/(extra|special)/data">
 
    
@@ -1513,21 +1552,23 @@
     Directory, Location and Files sections work for an
     explanation of how these different sections are combined when a
     request is received 
-    
    
-
-    
    LogLevel directive
    
-    Syntax: LogLevel level
    
-     Default: LogLevel
-    warn
    
-     Context: server config, virtual
-    host
    
-     Status: core
    
-     Compatibility: LogLevel is only
+    
    
+
+    
    LogLevel
+    directive
    
+    Syntax: LogLevel
+    level
    
+     Default: LogLevel
+    warn
    
+     Context: server config, virtual
+    host
    
+     Status: core
    
+     Compatibility: LogLevel is only
     available in 1.3 or later. 
 
     
    LogLevel adjusts the verbosity of the messages recorded in
@@ -1665,45 +1706,46 @@
 
     
    Using a level of at least crit is
     recommended.
    
-    
    
+    
    
 
-    
    MaxKeepAliveRequests
+    
    MaxKeepAliveRequests
     directive
    
-    Syntax: MaxKeepAliveRequests
-    number
    
-     Default: MaxKeepAliveRequests
-    100
    
-     Context: server config
    
-     Status: core
    
-     Compatibility: Only available in
-    Apache 1.2 and later. 
+    Syntax: MaxKeepAliveRequests
+    number
    
+     Default:
+    MaxKeepAliveRequests 100
    
+     Context: server config
    
+     Status: core
    
+     Compatibility: Only available
+    in Apache 1.2 and later. 
 
     
    The MaxKeepAliveRequests directive limits the number of
-    requests allowed per connection when KeepAlive is on. If it is set to
+    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
    
+    
    NameVirtualHost directive
    
     
-    Syntax: NameVirtualHost
-    addr[:port]
    
-     Context: server config
    
-     Status: core
    
-     Compatibility: NameVirtualHost is
-    only available in Apache 1.3 and later 
+    Syntax: NameVirtualHost
+    addr[:port]
    
+     Context: server config
    
+     Status: core
    
+     Compatibility: NameVirtualHost
+    is only available in Apache 1.3 and later 
 
     
    The NameVirtualHost directive is a required directive if you
     want to configure name-based virtual
@@ -1740,20 +1782,20 @@
     
     See also: Apache Virtual
     Host documentation 
-    
    
+    
    
 
-    
    Options directive
    
+    
    Options directive
    
     
-    Syntax: Options
-    [+|-]option [[+|-]option] ...
    
-     Context: server config, virtual
-    host, directory, .htaccess
    
-     Override: Options
    
-     Status: core 
+    Syntax: Options
+    [+|-]option [[+|-]option] ...
    
+     Context: server config, virtual
+    host, directory, .htaccess
    
+     Override: Options
    
+     Status: core 
 
     
    The Options directive controls which server features are
     available in a particular directory.
    
@@ -1777,10 +1819,11 @@
 
       
    
       
-      The server will follow symbolic links in this directory.
    
+      The server will follow symbolic links in this
+      directory.
    
        Note: even though the server follows the
       symlink it does not change the pathname used to
-      match against <Directory> sections.
    
+      match against <Directory> sections.
    
        Note: this option gets ignored if set
       inside a <Location> section.
    
 
@@ -1817,7 +1860,7 @@
       
       The server will only follow symbolic links for which the
       target file or directory is owned by the same user id as the
-      link.
    
+      link.
    
        Note: this option gets ignored if set
       inside a <Location> section.
     
@@ -1833,11 +1876,11 @@
     
    For example, without any + and - symbols:
    
 
     
    
-      <Directory /web/docs>
    
-       Options Indexes FollowSymLinks
    
-       </Directory>
    
-       <Directory /web/docs/spec>
    
-       Options Includes
    
+      <Directory /web/docs>
    
+       Options Indexes FollowSymLinks
    
+       </Directory>
    
+       <Directory /web/docs/spec>
    
+       Options Includes
    
        </Directory>    
     
    
     then only Includes will be set for the
@@ -1845,11 +1888,11 @@
     Options directive uses the + and - symbols: 
 
     
    
-      <Directory /web/docs>
    
-       Options Indexes FollowSymLinks
    
-       </Directory>
    
-       <Directory /web/docs/spec>
    
-       Options +Includes -Indexes
    
+      <Directory /web/docs>
    
+       Options Indexes FollowSymLinks
    
+       </Directory>
    
+       <Directory /web/docs/spec>
    
+       Options +Includes -Indexes
    
        </Directory>    
     
    
     then the options FollowSymLinks and
@@ -1862,18 +1905,20 @@
 
     
    The default in the absence of any other settings is
     All.
    
-    
    
+    
    
 
-    
    Port directive
    
+    
    Port directive
    
     
-    Syntax: Port number
    
-     Default: Port 80
    
-     Context: server config
    
-     Status: core 
+    Syntax: Port
+    number
    
+     Default: Port
+    80
    
+     Context: server config
    
+     Status: core 
 
     
    Number is a number from 0 to 65535; some port
     numbers (especially below 1024) are reserved for particular
@@ -1886,11 +1931,11 @@
     confusing in the context of Apache).
    
 
     
      
-      
    • In the absence of any Listen directives specifying a
-      port number, a Port directive given in the "main server"
-      (i.e., outside any <VirtualHost> section) sets the
+      
    • In the absence of any Listen directives
+      specifying a port number, a Port directive given in the "main
+      server" (i.e., outside any <VirtualHost> section) sets the
       network port on which the server listens. If there are any
       Listen directives specifying :number then Port
       has no effect on what address the server listens at.
      • 
@@ -1900,14 +1945,14 @@
       SSI), and is used when the
       server must generate a URL that refers to itself (for example
       when creating an external redirect to itself). This behaviour
-      is modified by UseCanonicalName.
+      is modified by UseCanonicalName.
     
    
-    The primary behavior of Port should be considered to be
-    similar to that of the ServerName
-    directive. The ServerName and Port together specify what you
-    consider to be the canonical address of the server.
-    (See also UseCanonicalName.) 
+    The primary behavior of Port should be considered to be similar
+    to that of the ServerName directive.
+    The ServerName and Port together specify what you consider to
+    be the canonical address of the server. (See also UseCanonicalName.) 
 
     
    Port 80 is one of Unix's special ports. All ports numbered
     below 1024 are reserved for system use, i.e., regular
@@ -1915,8 +1960,8 @@
     use higher port numbers. To use port 80, you must start the
     server from the root account. After binding to the port and
     before accepting requests, Apache will change to a low
-    privileged user as set by the User directive.
    
+    privileged user as set by the User directive.
    
 
     
    If you cannot use port 80, choose any other unused port.
     Non-root users will have to choose a port number higher than
@@ -1926,19 +1971,20 @@
     set User to root. If you run
     the server as root whilst handling connections, your site may
     be open to a major security attack.
    
-    
    
+    
    
 
-    
    Require directive
    
+    
    Require directive
    
     
-    Syntax: Require
-    entity-name [entity-name] ...
    
-     Context: directory, .htaccess
    
-     Override: AuthConfig
    
-     Status: core 
+    Syntax: Require
+    entity-name [entity-name] ...
    
+     Context: directory,
+    .htaccess
    
+     Override: AuthConfig
    
+     Status: core 
 
     
    This directive selects which authenticated users can access
     a directory. The allowed syntaxes are:
    
@@ -1965,50 +2011,50 @@
       
     
 
-    
    Require must be accompanied by AuthName and AuthType
-    directives, and directives such as AuthUserFile and AuthGroupFile (to define
+    
    Require must be accompanied by AuthName and AuthType directives, and directives such
+    as AuthUserFile and AuthGroupFile (to define
     users and groups) in order to work correctly. Example:
    
 
     
    
-      AuthType Basic
    
-       AuthName "Restricted Directory"
    
-       AuthUserFile /web/users
    
-       AuthGroupFile /web/groups
    
-       Require group admin
    
+      AuthType Basic
    
+       AuthName "Restricted Directory"
    
+       AuthUserFile /web/users
    
+       AuthGroupFile /web/groups
    
+       Require group admin
    
           
     
    
     Access controls which are applied in this way are effective for
     all methods. This is what is normally
     desired. If you wish to apply access controls only to
     specific methods, while leaving other methods unprotected, then
-    place the Require statement into a <Limit> section 
+    place the Require statement into a <Limit> section 
 
-    
    See also Satisfy and mod_access.
    
-    
    
+    
    See also Satisfy and mod_access.
    
+    
    
 
-    
    RLimitCPU directive
    
+    
    RLimitCPU directive
    
     
-    Syntax: RLimitCPU
-    number|max [number|max] 
    
-     Default: Unset; uses operating
-    system defaults 
    
-     Context: server config, virtual
-    host
    
-     Status: core
    
-     Compatibility: RLimitCPU is only
-    available in Apache 1.2 and later. Moved in version 2.0 to the
-    MPMs. 
+    Syntax: RLimitCPU
+    number|max [number|max] 
    
+     Default: Unset; uses
+    operating system defaults 
    
+     Context: server config, virtual
+    host
    
+     Status: core
    
+     Compatibility: RLimitCPU is
+    only available in Apache 1.2 and later. Moved in version 2.0 to
+    the MPMs. 
 
     
    Takes 1 or 2 parameters. The first parameter sets the soft
     resource limit for all processes and the second parameter sets
@@ -2028,27 +2074,28 @@
     
    CPU resource limits are expressed in seconds per
     process.
    
 
-    
    See also RLimitMEM or RLimitNPROC.
    
-    
    
+    
    See also RLimitMEM or RLimitNPROC.
    
+    
    
 
-    
    RLimitMEM directive
    
+    
    RLimitMEM
+    directive
    
     
-    Syntax: RLimitMEM
-    number|max [number|max]
    
-     Default: Unset; uses operating
-    system defaults 
    
-     Context: server config, virtual
-    host
    
-     Status: core
    
-     Compatibility: RLimitMEM is only
-    available in Apache 1.2 and later. Moved in version 2.0 to the
-    MPMs. 
+    Syntax: RLimitMEM
+    number|max [number|max]
    
+     Default: Unset; uses
+    operating system defaults 
    
+     Context: server config, virtual
+    host
    
+     Status: core
    
+     Compatibility: RLimitMEM is
+    only available in Apache 1.2 and later. Moved in version 2.0 to
+    the MPMs. 
 
     
    Takes 1 or 2 parameters. The first parameter sets the soft
     resource limit for all processes and the second parameter sets
@@ -2068,27 +2115,28 @@
     
    Memory resource limits are expressed in bytes per
     process.
    
 
-    
    See also RLimitCPU or RLimitNPROC.
    
-    
    
+    
    See also RLimitCPU or RLimitNPROC.
    
+    
    
 
-    
    RLimitNPROC directive
    
+    
    RLimitNPROC
+    directive
    
     
-    Syntax: RLimitNPROC
-    number|max [number|max]
    
-     Default: Unset; uses operating
-    system defaults 
    
-     Context: server config, virtual
-    host
    
-     Status: core
    
-     Compatibility: RLimitNPROC is only
-    available in Apache 1.2 and later. Moved in version 2.0 to the
-    MPMs. 
+    Syntax: RLimitNPROC
+    number|max [number|max]
    
+     Default: Unset; uses
+    operating system defaults 
    
+     Context: server config, virtual
+    host
    
+     Status: core
    
+     Compatibility: RLimitNPROC is
+    only available in Apache 1.2 and later. Moved in version 2.0 to
+    the MPMs. 
 
     
    Takes 1 or 2 parameters. The first parameter sets the soft
     resource limit for all processes and the second parameter sets
@@ -2114,22 +2162,23 @@
     cannot fork messages in the
     error_log.
    
 
-    
    See also RLimitMEM or RLimitCPU.
    
-    
    
+    
    See also RLimitMEM or RLimitCPU.
    
+    
    
 
-    
    Satisfy directive
    
+    
    Satisfy directive
    
     
-    Syntax: Satisfy any|all
    
-     Default: Satisfy all
    
-     Context: directory, .htaccess
    
-     Status: core
    
-     Compatibility: Satisfy is only
+    Syntax: Satisfy any|all
    
+     Default: Satisfy all
    
+     Context: directory,
+    .htaccess
    
+     Status: core
    
+     Compatibility: Satisfy is only
     available in Apache 1.2 and later 
 
     
    Access policy if both Allow and
@@ -2145,23 +2194,25 @@
     password restrict an area, but to let clients from particular
     addresses in without prompting for a password.
    
 
-    
    See also Require and mod_access.
    
-    
    
+    
    See also Require and mod_access.
    
+    
    
 
-    
    ScriptInterpreterSource
+    
    ScriptInterpreterSource
     directive
    
     
-    Syntax: ScriptInterpreterSource
-    registry|script
    
-     Default:
-    ScriptInterpreterSource script 
    
-     Context: directory, .htaccess
    
-     Status: core (Windows only) 
+    Syntax: ScriptInterpreterSource
+    registry|script
    
+     Default:
+    ScriptInterpreterSource script 
    
+     Context: directory,
+    .htaccess
    
+     Status: core (Windows only) 
 
     
    This directive is used to control how Apache 1.3.5 and later
     finds the interpreter used to run CGI scripts. The default
@@ -2169,18 +2220,19 @@
     in the script. Setting ScriptInterpreterSource registry will
     cause the Windows Registry to be searched using the script file
     extension (e.g., .pl) as a search key.
    
-    
    
+    
    
 
-    
    ServerAdmin directive
    
+    
    ServerAdmin
+    directive
    
     
-    Syntax: ServerAdmin
-    email-address
    
-     Context: server config, virtual
-    host
    
-     Status: core 
+    Syntax: ServerAdmin
+    email-address
    
+     Context: server config, virtual
+    host
    
+     Status: core 
 
     
    The ServerAdmin sets the e-mail address that the server
     includes in any error messages it returns to the client.
    
@@ -2193,38 +2245,41 @@
     
     as users do not always mention that they are talking about the
     server! 
-    
    
-
-    
    ServerAlias directive
    
-    Syntax: ServerAlias
-    hostname [hostname] ...
    
-     Context: virtual host
    
-     Status: core
    
-     Compatibility: ServerAlias is only
-    available in Apache 1.1 and later. 
+    
    
+
+    
    ServerAlias
+    directive
    
+    Syntax: ServerAlias
+    hostname [hostname] ...
    
+     Context: virtual host
    
+     Status: core
    
+     Compatibility: ServerAlias is
+    only available in Apache 1.1 and later. 
 
     
    The ServerAlias directive sets the alternate names for a
-    host, for use with name-based virtual hosts.
    
+    host, for use with name-based virtual
+    hosts.
    
 
     
    See also: Apache
     Virtual Host documentation
    
-    
    
+    
    
 
-    
    ServerName directive
    
+    
    ServerName
+    directive
    
     
-    Syntax: ServerName
-    fully-qualified-domain-name 
    
-     Context: server config, virtual
-    host
    
-     Status: core 
+    Syntax: ServerName
+    fully-qualified-domain-name 
    
+     Context: server config, virtual
+    host
    
+     Status: core 
 
     
    The ServerName directive sets the hostname of the server;
     this is used when creating redirection URLs. If it is not
@@ -2238,33 +2293,35 @@
     would be used if the canonical (main) name of the actual
     machine were simple.example.com. 
 
-    
    If you are using name-based virtual hosts, the
-    ServerName inside a <VirtualHost> section
-    specifies what hostname must appear in the request's
+    
    If you are using name-based virtual hosts,
+    the ServerName inside a <VirtualHost>
+    section specifies what hostname must appear in the request's
     Host: header to match this virtual host.
    
 
-    
    See Also:
    
-     DNS Issues
    
-     Apache virtual host documentation
    
-     UseCanonicalName
    
-     NameVirtualHost
    
-     ServerAlias
    
+    
    See Also:
    
+     DNS Issues
    
+     Apache virtual host
+    documentation
    
+     UseCanonicalName
    
+     NameVirtualHost
    
+     ServerAlias
    
     
    
-    
    
-
-    
    ServerPath directive
    
-    Syntax: ServerPath
-    directory-path
    
-     Context: virtual host
    
-     Status: core
    
-     Compatibility: ServerPath is only
-    available in Apache 1.1 and later. 
+    
    
+
+    
    ServerPath
+    directive
    
+    Syntax: ServerPath
+    directory-path
    
+     Context: virtual host
    
+     Status: core
    
+     Compatibility: ServerPath is
+    only available in Apache 1.1 and later. 
 
     
    The ServerPath directive sets the legacy URL pathname for a
     host, for use with name-based virtual
@@ -2272,20 +2329,21 @@
 
     
    See also: Apache
     Virtual Host documentation
    
-    
    
+    
    
 
-    
    ServerRoot directive
    
+    
    ServerRoot
+    directive
    
     
-    Syntax: ServerRoot
-    directory-path
    
-     Default: ServerRoot
-    /usr/local/apache
    
-     Context: server config
    
-     Status: core 
+    Syntax: ServerRoot
+    directory-path
    
+     Default: ServerRoot
+    /usr/local/apache
    
+     Context: server config
    
+     Status: core 
 
     
    The ServerRoot directive sets the directory in which the
     server lives. Typically it will contain the subdirectories
@@ -2299,25 +2357,25 @@
     
    See also the
     security tips for information on how to properly set
     permissions on the ServerRoot.
    
-    
    
+    
    
 
-    
    ServerSignature
-    directive
    
+    
    ServerSignature directive
    
     
-    Syntax: ServerSignature
-    On|Off|EMail
    
-     Default: ServerSignature
-    Off
    
-     Context: server config, virtual
-    host, directory, .htaccess
    
-     Status: core
    
-     Compatibility: ServerSignature is
-    only available in Apache 1.3 and later. 
+    Syntax: ServerSignature
+    On|Off|EMail
    
+     Default: ServerSignature
+    Off
    
+     Context: server config, virtual
+    host, directory, .htaccess
    
+     Status: core
    
+     Compatibility: ServerSignature
+    is only available in Apache 1.3 and later. 
 
     
    The ServerSignature directive allows the configuration of a
     trailing footer line under server-generated documents (error
@@ -2325,33 +2383,36 @@
     ...). The reason why you 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.
    
+    produced a returned error message.
    
      The Off setting, which is the default, suppresses
     the error 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, and
-    the EMail setting additionally creates a "mailto:"
-    reference to the ServerAdmin of the
-    referenced document.
    
-    
    
-
-    
    ServerTokens directive
    
+    adds a line with the server version number and ServerName of the serving virtual host,
+    and the EMail setting additionally creates a
+    "mailto:" reference to the ServerAdmin of the referenced
+    document.
    
+    
    
+
+    
    ServerTokens
+    directive
    
     
-    Syntax: ServerTokens
-    Minimal|ProductOnly|OS|Full
    
-     Default: ServerTokens
-    Full
    
-     Context: server config 
    
-     Status: core
    
-     Compatibility: ServerTokens is only
-    available in Apache 1.3 and later; the ProductOnly
-    keyword is only available in versions later than 1.3.12 
+    Syntax: ServerTokens
+    Minimal|ProductOnly|OS|Full
    
+     Default: ServerTokens
+    Full
    
+     Context: server config 
    
+     Status: core
    
+     Compatibility: ServerTokens is
+    only available in Apache 1.3 and later; the
+    ProductOnly keyword is only available in versions
+    later than 1.3.12 
 
     
    This directive controls whether Server response
     header field which is sent back to clients includes a
@@ -2382,21 +2443,22 @@
 
     
    This setting applies to the entire server, and cannot be
     enabled or disabled on a virtualhost-by-virtualhost basis.
    
-    
    
-
-    
    SetHandler directive
    
-    Syntax: SetHandler
-    handler-name
    
-     Context: directory, files,
-    location, .htaccess
    
-     Status: Base
    
-     Module: core
    
-     Compatibility: SetHandler was
+    
    
+
+    
    SetHandler
+    directive
    
+    Syntax: SetHandler
+    handler-name
    
+     Context: directory, files,
+    location, .htaccess
    
+     Status: Base
    
+     Module: core
    
+     Compatibility: SetHandler was
     introduced in mod_mime with Apache 1.1, and moved into the core
     with Apache 2.0 
 
@@ -2421,26 +2483,27 @@
     SetHandler server-status
     </Location>
    -
    +
    -

    SetInputFilter directive

    +

    SetInputFilter + directive

    -

    Syntax: SetInputFilter - filter[;filter...]
    - Default: none
    - Context: directory, files, - location, .htaccess
    - Status: core

    +

    Syntax: SetInputFilter + filter[;filter...]
    + Default: none
    + Context: directory, files, + location, .htaccess
    + Status: core

    The 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 any - filters defined elsewhere, including the AddInputFilter + filters defined elsewhere, including the AddInputFilter directive.

    If more than one filter is specified, they must be seperated @@ -2449,37 +2512,37 @@

    See also the Filters documentation.

    -
    - -

    SetOutputFilter - directive

    - -

    Syntax: SetOutputFilter - filter [filter] ...
    - Default: none
    - Context: directory, files, - location, .htaccess
    - Status: core

    +
    + +

    SetOutputFilter directive

    + +

    Syntax: SetOutputFilter + filter [filter] ...
    + Default: none
    + Context: directory, files, + location, .htaccess
    + Status: core

    The 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 - elsewhere, including the AddOutputFilter + elsewhere, including the AddOutputFilter directive.

    For example, the following configuration will process all files in the /www/data/ directory for server-side - includes.
    -
    + includes.
    +
    - <Directory /www/data/>
    -   SetOutputFilter INCLUDES
    + <Directory /www/data/>
    +   SetOutputFilter INCLUDES
    </Directory>
    @@ -2489,19 +2552,20 @@

    See also the Filters documentation.

    -
    +
    -

    TimeOut directive

    +

    TimeOut directive

    - Syntax: TimeOut number
    - Default: TimeOut - 300
    - Context: server config
    - Status: core + Syntax: TimeOut + number
    + Default: TimeOut + 300
    + Context: server config
    + Status: core

    The TimeOut directive currently defines the amount of time Apache will wait for three things:

    @@ -2522,31 +2586,31 @@ necessary in most situations. It is not set any lower by default because there may still be odd places in the code where the timer is not reset when a packet is sent. -
    +
    -

    UseCanonicalName - directive

    +

    UseCanonicalName directive

    - Syntax: UseCanonicalName - on|off|dns
    - Default: UseCanonicalName - on
    - Context: server config, virtual - host, directory
    - Override: Options
    - Compatibility: UseCanonicalName is - only available in Apache 1.3 and later + Syntax: UseCanonicalName + on|off|dns
    + Default: UseCanonicalName + on
    + Context: server config, virtual + host, directory
    + Override: Options
    + Compatibility: UseCanonicalName + is only available in Apache 1.3 and later

    In many situations Apache has to construct a self-referential URL. That is, a URL which refers back to the same server. With UseCanonicalName on (and - in all versions prior to 1.3) Apache will use the ServerName and Port + in all versions prior to 1.3) Apache will use the ServerName and Port directives to construct a canonical name for the server. This name is used in all self-referential URLs, and for the values of SERVER_NAME and SERVER_PORT in @@ -2589,26 +2653,27 @@ SERVER_NAME to construct self-referential URLs then it should be just fine.

    -

    See also: ServerName, Port

    -
    +

    See also: ServerName, Port

    +
    -

    <VirtualHost> +

    <VirtualHost> directive

    - Syntax: <VirtualHost + Syntax: <VirtualHost addr[:port] [addr[:port]] - ...> ... </VirtualHost>
    - Context: server config
    - Status: Core.
    - Compatibility: Non-IP address-based - Virtual Hosting only available in Apache 1.1 and later.
    - Compatibility: Multiple address + ...> ... </VirtualHost>
    + Context: server config
    + Status: Core.
    + Compatibility: Non-IP + address-based Virtual Hosting only available in Apache 1.1 and + later.
    + Compatibility: Multiple address support only available in Apache 1.2 and later.

    <VirtualHost> and </VirtualHost> are used to @@ -2628,12 +2693,12 @@ Example:

    - <VirtualHost 10.1.2.3>
    - ServerAdmin webmaster@host.foo.com
    - DocumentRoot /www/docs/host.foo.com
    - ServerName host.foo.com
    - ErrorLog logs/host.foo.com-error_log
    - TransferLog logs/host.foo.com-access_log
    + <VirtualHost 10.1.2.3>
    + ServerAdmin webmaster@host.foo.com
    + DocumentRoot /www/docs/host.foo.com
    + ServerName host.foo.com
    + ErrorLog logs/host.foo.com-error_log
    + TransferLog logs/host.foo.com-access_log
    </VirtualHost>
    Each VirtualHost must correspond to a different IP address, @@ -2642,8 +2707,8 @@ 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 - your OS supports it), or with kernel patches like VIF (for SunOS(TM) 4.1.x)). + your OS supports it), or with kernel patches like VIF (for SunOS(TM) 4.1.x)).

    The special name _default_ can be specified in which case this virtual host will match any IP address that is @@ -2659,24 +2724,25 @@ match all ports on that address. (This is recommended when used with _default_.)

    -

    SECURITY: See the security tips document for - details on why your security could be compromised if the +

    SECURITY: See the security tips document + for details on why your security could be compromised if the directory where logfiles are stored is writable by anyone other than the user that starts the server.

    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.

    + addresses using Listen.

    See also: Apache - Virtual Host documentation
    - See also: Warnings about DNS and Apache
    + Virtual Host documentation
    + See also: Warnings about DNS and + Apache
    See also: Setting - which addresses and ports Apache uses
    + which addresses and ports Apache uses
    See also: How Directory, Location and Files sections work for an explanation of how these different sections are combined when a diff --git a/docs/manual/mod/directive-dict.html b/docs/manual/mod/directive-dict.html index 79652bad12..deedf08aca 100644 --- a/docs/manual/mod/directive-dict.html +++ b/docs/manual/mod/directive-dict.html @@ -1,13 +1,17 @@ - - + + + + + Definitions of terms used to describe Apache directives - +

    Terms Used to Describe Apache @@ -18,22 +22,23 @@
    Syntax: - directive-name some args
    + directive-name some args
    Default: - directive-name default-value
    + directive-name default-value
    Context: - context-list
    - Override: override
    + context-list
    + Override: + override
    Status: - status
    + status
    Module: - module-name
    - Compatibility: compatibility - notes
    - Deprecated: see + module-name
    + Compatibility: + compatibility notes
    + Deprecated: see other
    @@ -59,9 +64,9 @@
  • Deprecated
    • -
    +
    -

    Syntax

    +

    Syntax

    This indicates the format of the directive as it would appear in a configuration file. This syntax is extremely @@ -145,13 +150,13 @@

    The name of an environment variable defined in the Apache configuration process. Note this is not necessarily the same as an operating system - environment variable. See the environment variable documentation for more - details.
    + environment variable. See the environment variable documentation for + more details. -
    +
    -

    Default

    +

    Default

    If the directive has a default value (i.e., if you omit it from your configuration entirely, the Apache Web server @@ -160,9 +165,9 @@ should say "None". Note that the default listed here is not necessarily the same as the value the directive takes in the default httpd.conf distributed with the server.

    -
    +
    -

    Context

    +

    Context

    This indicates where in the server's configuration files the directive is legal. It's a comma-separated list of one or more @@ -199,8 +204,8 @@

    If a directive is valid in this context, it means that it can appear inside per-directory .htaccess files. It may not be processed, though - depending upon the overrides currently active.
    + depending upon the overrides currently active.

    The directive is only allowed within the designated @@ -217,9 +222,9 @@ httpd.conf file and in .htaccess files, but not within any <Directory> or <VirtualHost> containers.

    -
    +
    -

    Override

    +

    Override

    This directive attribute indicates which configuration override must be active in order for the directive to be @@ -228,16 +233,17 @@ doesn't permit it to appear in .htaccess files, this attribute should say "Not applicable".

    -

    Overrides are activated by the AllowOverride directive, and apply to a - particular scope (such as a directory) and all descendants, - unless further modified by other AllowOverride - directives at lower levels. The documentation for that - directive also lists the possible override names available.

    -
    +

    Overrides are activated by the AllowOverride directive, and apply + to a particular scope (such as a directory) and all + descendants, unless further modified by other + AllowOverride directives at lower levels. The + documentation for that directive also lists the possible + override names available.

    +
    -

    Status

    +

    Status

    This indicates how tightly bound into the Apache Web server the directive is; in other words, you may need to recompile the @@ -257,8 +263,9 @@

    A directive labeled as having "MPM" status is provided by a Multi-Processing Module. This type of directive will be available if and only if you are - using one of the MPMs listed on the Module line of the directive definition.
    + using one of the MPMs listed on the Module line of the directive + definition.
    Base
    @@ -287,15 +294,16 @@ directive and its module to see if it remarks on the availability. -
    +
    -

    Module

    +

    Module

    This quite simply lists the name of the source module which defines the directive.

    -
    +
    -

    Compatibility

    +

    Compatibility

    If the directive wasn't part of the original Apache version 1 distribution, the version in which it was introduced should @@ -303,9 +311,9 @@ the NCSA HTTPd server, any inconsistencies in behavior between the two should also be mentioned. Otherwise, this attribute should say "No compatibility issues."

    -
    +
    -

    Deprecated

    +

    Deprecated

    If this directive is eliminated since the Apache version 1 distribution, the directive or option that replaces the diff --git a/docs/manual/mod/directive-dict.html.en b/docs/manual/mod/directive-dict.html.en index 79652bad12..deedf08aca 100644 --- a/docs/manual/mod/directive-dict.html.en +++ b/docs/manual/mod/directive-dict.html.en @@ -1,13 +1,17 @@ - - + + + + + Definitions of terms used to describe Apache directives - +

    Terms Used to Describe Apache @@ -18,22 +22,23 @@
    Syntax: - directive-name some args
    + directive-name some args
    Default: - directive-name default-value
    + directive-name default-value
    Context: - context-list
    - Override: override
    + context-list
    + Override: + override
    Status: - status
    + status
    Module: - module-name
    - Compatibility: compatibility - notes
    - Deprecated: see + module-name
    + Compatibility: + compatibility notes
    + Deprecated: see other
    @@ -59,9 +64,9 @@
  • Deprecated
    • -
    +
    -

    Syntax

    +

    Syntax

    This indicates the format of the directive as it would appear in a configuration file. This syntax is extremely @@ -145,13 +150,13 @@

    The name of an environment variable defined in the Apache configuration process. Note this is not necessarily the same as an operating system - environment variable. See the environment variable documentation for more - details.
    + environment variable. See the environment variable documentation for + more details. -
    +
    -

    Default

    +

    Default

    If the directive has a default value (i.e., if you omit it from your configuration entirely, the Apache Web server @@ -160,9 +165,9 @@ should say "None". Note that the default listed here is not necessarily the same as the value the directive takes in the default httpd.conf distributed with the server.

    -
    +
    -

    Context

    +

    Context

    This indicates where in the server's configuration files the directive is legal. It's a comma-separated list of one or more @@ -199,8 +204,8 @@

    If a directive is valid in this context, it means that it can appear inside per-directory .htaccess files. It may not be processed, though - depending upon the overrides currently active.
    + depending upon the overrides currently active.

    The directive is only allowed within the designated @@ -217,9 +222,9 @@ httpd.conf file and in .htaccess files, but not within any <Directory> or <VirtualHost> containers.

    -
    +
    -

    Override

    +

    Override

    This directive attribute indicates which configuration override must be active in order for the directive to be @@ -228,16 +233,17 @@ doesn't permit it to appear in .htaccess files, this attribute should say "Not applicable".

    -

    Overrides are activated by the AllowOverride directive, and apply to a - particular scope (such as a directory) and all descendants, - unless further modified by other AllowOverride - directives at lower levels. The documentation for that - directive also lists the possible override names available.

    -
    +

    Overrides are activated by the AllowOverride directive, and apply + to a particular scope (such as a directory) and all + descendants, unless further modified by other + AllowOverride directives at lower levels. The + documentation for that directive also lists the possible + override names available.

    +
    -

    Status

    +

    Status

    This indicates how tightly bound into the Apache Web server the directive is; in other words, you may need to recompile the @@ -257,8 +263,9 @@

    A directive labeled as having "MPM" status is provided by a Multi-Processing Module. This type of directive will be available if and only if you are - using one of the MPMs listed on the Module line of the directive definition.
    + using one of the MPMs listed on the Module line of the directive + definition.
    Base
    @@ -287,15 +294,16 @@ directive and its module to see if it remarks on the availability. -
    +
    -

    Module

    +

    Module

    This quite simply lists the name of the source module which defines the directive.

    -
    +
    -

    Compatibility

    +

    Compatibility

    If the directive wasn't part of the original Apache version 1 distribution, the version in which it was introduced should @@ -303,9 +311,9 @@ the NCSA HTTPd server, any inconsistencies in behavior between the two should also be mentioned. Otherwise, this attribute should say "No compatibility issues."

    -
    +
    -

    Deprecated

    +

    Deprecated

    If this directive is eliminated since the Apache version 1 distribution, the directive or option that replaces the diff --git a/docs/manual/mod/directives.html b/docs/manual/mod/directives.html index aa21281883..893802b22e 100644 --- a/docs/manual/mod/directives.html +++ b/docs/manual/mod/directives.html @@ -1,271 +1,657 @@ - - - -Apache directives - - - - - -

    Apache Directives

    -

    -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. -

    - - - - - + + + + + + + Apache directives + + + + + + +

    Apache Directives

    + +

    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.

    + + + + + + diff --git a/docs/manual/mod/mod_asis.html b/docs/manual/mod/mod_asis.html index 2b7e55cf92..c71ec725c1 100644 --- a/docs/manual/mod/mod_asis.html +++ b/docs/manual/mod/mod_asis.html @@ -1,14 +1,16 @@ - + - + - + + Apache module mod_asis - +

    Module mod_asis

    @@ -16,12 +18,13 @@

    This module provides for sending files which contain their own HTTP headers.

    -

    Status: Base
    - Source - File: mod_asis.c
    - Module Identifier: asis_module

    +

    Status: Base
    + Source File: mod_asis.c
    + Module Identifier: + asis_module

    Summary

    @@ -60,22 +63,22 @@ redirected.

    - Status: 301 Now where did I leave that URL
    - Location: http://xyz.abc.com/foo/bar.html
    - Content-type: text/html
    -
    - <HTML>
    - <HEAD>
    - <TITLE>Lame excuses'R'us</TITLE>
    - </HEAD>
    - <BODY>
    + Status: 301 Now where did I leave that URL
    + Location: http://xyz.abc.com/foo/bar.html
    + Content-type: text/html
    +
    + <HTML>
    + <HEAD>
    + <TITLE>Lame excuses'R'us</TITLE>
    + </HEAD>
    + <BODY>
    <H1>Fred's exceptionally wonderful page has moved - to
    + to
    <A HREF="http://xyz.abc.com/foo/bar.html">Joe's</A> - site.
    - </H1>
    - </BODY>
    + site.
    + </H1>
    + </BODY>
    </HTML>