From 24f3b242dcc5b8a0d50612afa6860f5e46733763 Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Wed, 13 Nov 2002 18:20:32 +0000 Subject: [PATCH] A couple long-overdue changes to configuring: - Remove the over-detailed and out-of-date description of Include directories. - Link Rich's .htaccess tutorial. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97504 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/configuring.html.en | 32 +++++++++++-------------------- docs/manual/configuring.xml | 34 +++++++++++---------------------- 2 files changed, 22 insertions(+), 44 deletions(-) diff --git a/docs/manual/configuring.html.en b/docs/manual/configuring.html.en index 2353d49de79..2f360aebda0 100644 --- a/docs/manual/configuring.html.en +++ b/docs/manual/configuring.html.en @@ -12,24 +12,15 @@ HTTP server.

Related ModulesRelated Directives

Apache is configured by placing directives in plain text - configuration files. The main configuration file is usually - called httpd.conf. The location of this file is - set at compile-time, but may be overridden with the - -f command line flag. In addition, other - configuration files may be added using the Include directive. Any - directive may be placed in any of these configuration files. - Changes to the main configuration files are only recognized by - Apache when it is started or restarted.

- -

New with Apache 1.3.13 is a feature where if any - configuration file is actually a directory, Apache will enter - that directory and parse any files (and subdirectories) found - there as configuration files. One possible use for this would - be to add VirtualHosts by creating small configuration files - for each host, and placing them in such a configuration - directory. Thus, you can add or remove VirtualHosts without - editing any files at all, simply adding or deleting them. This - makes automating such processes much easier.

+ configuration files. The main configuration file is usually called + httpd.conf. The location of this file is set at + compile-time, but may be overridden with the -f + command line flag. In addition, other configuration files may be + added using the Include + directive, and wildcards can be used to include many configuration + files. Any directive may be placed in any of these configuration + files. Changes to the main configuration files are only + recognized by Apache when it is started or restarted.

The server also reads a file containing mime document types; the filename is set by the TypesConfig directive, @@ -45,7 +36,7 @@ HTTP server.

Directives in the configuration files are case-insensitive, but arguments to directives are often case sensitive. Lines - which begin with the hash character "#" are considered + that begin with the hash character "#" are considered comments, and are ignored. Comments may not be included on a line after a configuration directive. Blank lines and white space occurring before a directive are ignored, so @@ -127,6 +118,5 @@ HTTP server.

directive in the main configuration files.

For more information on .htaccess files, see - Ken Coar's tutorial on - Using .htaccess Files with Apache.

+ the .htaccess tutorial.

\ No newline at end of file diff --git a/docs/manual/configuring.xml b/docs/manual/configuring.xml index 93173ba3be7..199dee4718d 100644 --- a/docs/manual/configuring.xml +++ b/docs/manual/configuring.xml @@ -26,25 +26,15 @@ HTTP server.

Apache is configured by placing directives in plain text - configuration files. The main configuration file is usually - called httpd.conf. The location of this file is - set at compile-time, but may be overridden with the - -f command line flag. In addition, other - configuration files may be added using the Include directive. Any - directive may be placed in any of these configuration files. - Changes to the main configuration files are only recognized by - Apache when it is started or restarted.

- -

New with Apache 1.3.13 is a feature where if any - configuration file is actually a directory, Apache will enter - that directory and parse any files (and subdirectories) found - there as configuration files. One possible use for this would - be to add VirtualHosts by creating small configuration files - for each host, and placing them in such a configuration - directory. Thus, you can add or remove VirtualHosts without - editing any files at all, simply adding or deleting them. This - makes automating such processes much easier.

+ configuration files. The main configuration file is usually called + httpd.conf. The location of this file is set at + compile-time, but may be overridden with the -f + command line flag. In addition, other configuration files may be + added using the Include + directive, and wildcards can be used to include many configuration + files. Any directive may be placed in any of these configuration + files. Changes to the main configuration files are only + recognized by Apache when it is started or restarted.

The server also reads a file containing mime document types; the filename is set by the

Directives in the configuration files are case-insensitive, but arguments to directives are often case sensitive. Lines - which begin with the hash character "#" are considered + that begin with the hash character "#" are considered comments, and are ignored. Comments may not be included on a line after a configuration directive. Blank lines and white space occurring before a directive are ignored, so @@ -186,8 +176,6 @@ HTTP server.

directive in the main configuration files.

For more information on .htaccess files, see - Ken Coar's tutorial on - Using .htaccess Files with Apache.

+ the .htaccess tutorial.

\ No newline at end of file -- 2.47.3