From: pcs Date: Sat, 30 Nov 1996 17:06:40 +0000 (+0000) Subject: Fix various typos. Put directives in alphabetic order. Put
's between X-Git-Tag: APACHE_1_2b1~19 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0a31e3f807fd1ce06c08ec5f491b72f5f710e8f8;p=apache Fix various typos. Put directives in alphabetic order. Put
's between directives. Remove documentation about %s in ErrorDocument ". Update default MaxClients to 256. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77094 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index 4ac63447db..3728e25a92 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -14,9 +14,6 @@ always available.
-

SendBufferSize

 - -Syntax: SendBufferSize bytes
-Context: server config, virtual host
-Status: core

- -The server will set the TCP buffer size to the number of bytes -specified. Very useful to increase past standard OS defaults on high -speed high latency (i.e. 100ms or so, such as transcontinental -fast pipes) - -

- -

<Files>

 -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 matched with a </Files> directive. Directives that -apply to the filename given should be listed -within. <Files> sections are processed in the -order they appear in the configuration file, after the -<Directory> sections and .htaccess files are -read, but before <Location> sections.

- -

The filename argument should include a filename, or a -wildcard string, where `?' matches any single character, and `*' matches any -sequences of characters. Extended regular expressions can also be used, with the addition of -the ~ character. For example:

- -
-   <Files ~ "\.(gif|jpe?g|png)$">
-
- -would match most common Internet graphics formats. - -

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. When used in an .htaccess file, if the -filename does not begin with a / character, -the directory being applied will be prefixed automatically. - -

- -

<IfModule>

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

- -

- -The <IfModule test>...</IfModule> -section is used to mark directives that are conditional. The -directives within an IfModule section are only -processed if the test is true. If test -is false, everything between the start and end markers -is ignored.

- -The test in the <IfModule> section directive -can be one of two forms: - -

- -

In the former case, the directives between the start and end markers -are only processed if the module named module name is compiled -in to Apache. The second format reverses the test, and only processes -the directives if module name is not compiled in. - -

The module name argument is a module name as given as the file -name of the module, at the time it was compiled. For example, -mod_rewrite.c. - -

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

-

AccessConfig directive

 Syntax: AccessConfig filename
@@ -431,8 +337,7 @@ is followed by the HTTP response code and a message or URL.

Messages in this context, begin with a single quote ("), which does not form part of the message itself. Apache will -sometime offer additional information regarding the problem/error. This can be -embedded into the message using %s +sometime offer additional information regarding the problem/error.

URLs will begin with a slash (/) for local URLs, or will be a full URL which the client can resolve. Examples: @@ -460,6 +365,47 @@ Example:

ErrorLog /dev/null
This effectively turns off error logging.

+

<Files>

 +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 matched with a </Files> directive. Directives that +apply to the filename given should be listed +within. <Files> sections are processed in the +order they appear in the configuration file, after the +<Directory> sections and .htaccess files are +read, but before <Location> sections.

+ +

The filename argument should include a filename, or a +wildcard string, where `?' matches any single character, and `*' matches any +sequences of characters. Extended regular expressions can also be used, with the addition of +the ~ character. For example:

+ +
+   <Files ~ "\.(gif|jpe?g|png)$">
+
+ +would match most common Internet graphics formats. + +

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. When used in an .htaccess file, if the +filename does not begin with a / character, +the directory being applied will be prefixed automatically. + +

+

Group directive

 Syntax: Group unix-group
@@ -503,6 +449,46 @@ This information is logged in the access log. Boolean is either The information should not trusted in any way except for rudimentary usage tracking.

+

<IfModule>

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

+ +

+ +The <IfModule test>...</IfModule> +section is used to mark directives that are conditional. The +directives within an IfModule section are only +processed if the test is true. If test +is false, everything between the start and end markers +is ignored.

+ +The test in the <IfModule> section directive +can be one of two forms: + +

+ +

In the former case, the directives between the start and end markers +are only processed if the module named module name is compiled +in to Apache. The second format reverses the test, and only processes +the directives if module name is not compiled in. + +

The module name argument is a module name as given as the file +name of the module, at the time it was compiled. For example, +mod_rewrite.c. + +

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

+

KeepAlive

Syntax: KeepAlive max-requests
Default: KeepAlive 5
@@ -531,7 +517,7 @@ closing the connection. Once a request has been received, the timeout value specified by the Timeout directive applies. - +

Listen

 Syntax: @@ -548,6 +534,7 @@ directive.

See Also: Setting which addresses and ports Apache uses

+

<Limit> directive

 @@ -623,12 +610,12 @@ from browsers at foo.com, you might use: </Location> - +

MaxClients directive

 Syntax: MaxClients number
-Default: MaxClients 150
+Default: MaxClients 256
Context: server config
Status: core

@@ -744,11 +731,11 @@ file or directory is owned by the same user id as the link. Normally, if multiple Options could apply to a directory, then the most specific one is taken complete; the options are not -merged. However if all the options on the Options directive are -preceeded by a + or - symbol, the options are merged. Any options -preceeded by a + are added to the options currently in force, and any -options preceeded by a - are removed from the options currently in -force.

+merged. However if all the options on the Options +directive are preceeded by a + or - symbol, the options are +merged. Any options preceeded by a + are added to the options +currently in force, and any options preceeded by a - are removed from +the options currently in force.

For example, without any + and - symbols: @@ -774,6 +761,7 @@ Options +Includes -Indexes
then the options FollowSymLinks and Includes are set for the /web/docs/spec directory. +

PidFile directive

 @@ -877,6 +865,18 @@ sections; in fact it can now contain any server directive allowed in the See also AccessConfig.

+

SendBufferSize

 + +Syntax: SendBufferSize bytes
+Context: server config, virtual host
+Status: core

+ +The server will set the TCP buffer size to the number of bytes +specified. Very useful to increase past standard OS defaults on high +speed high latency (i.e. 100ms or so, such as transcontinental +fast pipes) +

+

ServerAdmin directive

 Syntax: ServerAdmin email-address
@@ -928,6 +928,7 @@ were monster.wibble.com.

The ServerAlias directive sets the legacy URL pathname for a host, for use with Host-header based virtual hosts. +

ServerRoot directive