From: Joshua Slive Date: Sun, 10 Nov 2002 23:43:50 +0000 (+0000) Subject: A couple core docs fixes: X-Git-Tag: 2.0.44~91 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=50994254bf8ef587c48bb86058bdea69360625f3;p=apache A couple core docs fixes: 1. Document the fnmatch wildcards in Include. 2. Add a couple ServerSignature/ServerTokens markups. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97478 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index d0a97ca302..d14fc9c0e2 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -549,7 +549,7 @@ named file-system directory and sub-directoriesSyntax: <DirectoryMatch regex> -... </Directory>Context: +... </DirectoryMatch>Context: server config, virtual hostStatus: CoreModule: core @@ -1102,14 +1102,19 @@ the server configuration filesContext: server config, virtual host, directoryStatus: CoreModule: - core + coreCompatibility: + Wildcard matching available in 2.0.41 and later

This directive allows inclusion of other configuration files from within the server configuration files.

-

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

+

Shell-style (fnmatch) wildcard characters can be used to + include several files at once, in alphabetical order. In + addition, if Include points to a directory, + rather than a file, Apache will read all files in that directory + and any subdirectory. But including entire directories is not + recommended, because it is easy to accidentally leave temporary + files in a directory that can cause httpd to + fail.

The file path specified may be a fully qualified path (i.e. starting with a slash), or may be relative to the @@ -1118,36 +1123,28 @@ the server configuration files

- Include /usr/local/apache/conf/ssl.conf
- Include /usr/local/apache/conf/vhosts/ + Include /usr/local/apache2/conf/ssl.conf
+ Include /usr/local/apache2/conf/vhosts/*.conf

-

Or, providing paths relative to your ServerRoot - directory:

+

Or, providing paths relative to your ServerRoot directory:

Include conf/ssl.conf
- Include conf/vhosts/ + Include conf/vhosts/*.conf

-

Make sure that an included directory does not contain any stray - files, such as editor temporary files, for example, as Apache will - attempt to read them in and use the contents as configuration - directives, which may cause the server to fail on start up. - Running apachectl configtest will give you a list of - the files that are being processed during the configuration +

Running apachectl configtest will give you a list + of the files that are being processed during the configuration check:

root@host# apachectl configtest
- Processing config directory: /usr/local/apache/conf/vhosts
- Processing config file: /usr/local/apache/conf/vhosts/vhost1
- Processing config file: /usr/local/apache/conf/vhosts/vhost2
+ Processing config file: /usr/local/apache2/conf/ssl.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost1.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost2.conf
Syntax OK

- -

This will help in verifying that you are getting only the files - that you intended as part of your configuration.

See also

top

KeepAlive Directive

Description: Enables HTTP persistent connections
Syntax: KeepAlive on|off
Default: @@ -2167,7 +2164,7 @@ is accessed by an incompatible browser
ServerTokens directive.

See also

top

ServerTokens Directive

Description: Configures the Server HTTP response header
Syntax: ServerTokens Major|Minor|Minimal|ProductOnly|OS|Full
Default: @@ -2216,7 +2213,7 @@ is accessed by an incompatible browser
ServerSignature directive.

See also

top

SetHandler Directive

Description: Forces all matching files to be processed by a handler
Syntax: diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml index 7e6bb71505..a24957f317 100644 --- a/docs/manual/mod/core.xml +++ b/docs/manual/mod/core.xml @@ -603,7 +603,7 @@ named file-system directory and sub-directories file-system directories matching a regular expression and their subdirectories <DirectoryMatch regex> -... </Directory> +... </DirectoryMatch> server configvirtual host @@ -1264,15 +1264,20 @@ the server configuration files server configvirtual host directory +Wildcard matching available in 2.0.41 and later

This directive allows inclusion of other configuration files from within the server configuration files.

-

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

+

Shell-style (fnmatch) wildcard characters can be used to + include several files at once, in alphabetical order. In + addition, if Include points to a directory, + rather than a file, Apache will read all files in that directory + and any subdirectory. But including entire directories is not + recommended, because it is easy to accidentally leave temporary + files in a directory that can cause httpd to + fail.

The file path specified may be a fully qualified path (i.e. starting with a slash), or may be relative to the @@ -1281,36 +1286,29 @@ the server configuration files

Examples:

- Include /usr/local/apache/conf/ssl.conf
- Include /usr/local/apache/conf/vhosts/ + Include /usr/local/apache2/conf/ssl.conf
+ Include /usr/local/apache2/conf/vhosts/*.conf
-

Or, providing paths relative to your ServerRoot - directory:

+

Or, providing paths relative to your ServerRoot directory:

Include conf/ssl.conf
- Include conf/vhosts/ + Include conf/vhosts/*.conf
-

Make sure that an included directory does not contain any stray - files, such as editor temporary files, for example, as Apache will - attempt to read them in and use the contents as configuration - directives, which may cause the server to fail on start up. - Running apachectl configtest will give you a list of - the files that are being processed during the configuration +

Running apachectl configtest will give you a list + of the files that are being processed during the configuration check:

root@host# apachectl configtest
- Processing config directory: /usr/local/apache/conf/vhosts
- Processing config file: /usr/local/apache/conf/vhosts/vhost1
- Processing config file: /usr/local/apache/conf/vhosts/vhost2
+ Processing config file: /usr/local/apache2/conf/ssl.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost1.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost2.conf
Syntax OK
- -

This will help in verifying that you are getting only the files - that you intended as part of your configuration.

apachectl @@ -2514,7 +2512,8 @@ is accessed by an incompatible browser document.

After version 2.0.44, the details of the server version number - presented are controlled by the ServerTokens directive.

+ presented are controlled by the ServerTokens directive.

ServerTokens @@ -2568,7 +2567,8 @@ is accessed by an incompatible browser enabled or disabled on a virtualhost-by-virtualhost basis.

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

+ information presented by the ServerSignature directive.

ServerSignature