From 3a1ce4ce3e2c129a3630d4a15629bf26cb975488 Mon Sep 17 00:00:00 2001 From: Erik Abele Date: Sun, 18 Aug 2002 19:24:17 +0000 Subject: [PATCH] New XML. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96438 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/server-wide.html.en | 188 ++++++++++---------------------- docs/manual/server-wide.xml | 100 +++++++++++++++++ 2 files changed, 157 insertions(+), 131 deletions(-) create mode 100644 docs/manual/server-wide.xml diff --git a/docs/manual/server-wide.html.en b/docs/manual/server-wide.html.en index 693b06a86c..5b6511b2bc 100644 --- a/docs/manual/server-wide.html.en +++ b/docs/manual/server-wide.html.en @@ -1,134 +1,60 @@ - - - - - - - Server-Wide Configuration - - - - - - -

Server-Wide Configuration

- -

This document explains some of the directives provided by - the core server which are used to - configure the basic operations of the server.

- - -
- -

Server - Identification

- - - - - -
Related Directives
-
- ServerName
- ServerAdmin
- ServerSignature
- ServerTokens
- UseCanonicalName
-
- -

The ServerAdmin and ServerTokens - directives control what information about the server will be - presented in server-generated documents such as error messages. - The ServerTokens directive sets the value of the - Server HTTP response header field.

- -

The ServerName and - UseCanonicalName directives are used by the server - to determine how to construct self-referential URLs. For - example, when a client requests a directory, but does not - include the trailing slash in the directory name, Apache must - redirect the client to the full name including the trailing - slash so that the client will correctly resolve relative - references in the document.

-
- -

File Locations

- - - - - -
Related Directives
-
- CoreDumpDirectory
- DocumentRoot
- ErrorLog
- Lockfile
- PidFile
- ScoreBoardFile
- ServerRoot
-
+Server-Wide Configuration - Apache HTTP Server
[APACHE DOCUMENTATION]

Apache HTTP Server Version 2.0

Server-Wide Configuration

+

This document explains some of the directives provided by +the core server which are used to configure +the basic operations of the server.

+

Server Identification

+ + +
Related Modules

Related Directives

ServerName
ServerAdmin
ServerSignature
ServerTokens
UseCanonicalName
+ +

The ServerAdmin and + ServerTokens directives + control what information about the server will be presented + in server-generated documents such as error messages. The + ServerTokens directive + sets the value of the Server HTTP response header field.

+ +

The ServerName and + UseCanonicalName + directives are used by the server to determine how to construct + self-referential URLs. For example, when a client requests a + directory, but does not include the trailing slash in the + directory name, Apache must redirect the client to the full + name including the trailing slash so that the client will + correctly resolve relative references in the document.

+

File Locations

+ + +
Related Modules

Related Directives

CoreDumpDirectory
DocumentRoot
ErrorLog
LockFile
PidFile
ScoreBoardFile
ServerRoot

These directives control the locations of the various files that Apache needs for proper operation. When the pathname used - does not begin with a slash "/", the files are located relative - to the ServerRoot. Be careful about locating files - in paths which are writable by non-root users. See the security tips documentation - for more details.

-
- -

Limiting Resource - Usage

- - - - - -
Related Directives
-
- LimitRequestBody
- LimitRequestFields
- LimitRequestFieldsize
- LimitRequestLine
- RLimitCPU
- RLimitMEM
- RLimitNPROC
- ThreadStackSize
-
- -

The LimitRequest* directives are used to place - limits on the amount of resources Apache will use in reading - requests from clients. By limiting these values, some kinds of - denial of service attacks can be mitigated.

- -

The RLimit* directives are used to limit the - amount of resources which can be used by processes forked off - from the Apache children. In particular, this will control - resources used by CGI scripts and SSI exec commands.

- -

The ThreadStackSize directive is used only on - Netware to control the stack size.

- - - - + does not begin with a slash (/), the files are located relative + to the ServerRoot. Be careful + about locating files in paths which are writable by non-root users. + See the security tips + documentation for more details.

+

Limiting Resource Usage

+ + +
Related Modules

Related Directives

LimitRequestBody
LimitRequestFields
LimitRequestFieldsize
LimitRequestLine
RLimitCPU
RLimitMEM
RLimitNPROC
ThreadStackSize
+ +

The LimitRequest* + directives are used to place limits on the amount of resources + Apache will use in reading requests from clients. By limiting + these values, some kinds of denial of service attacks can be + mitigated.

+ +

The RLimit* directives + are used to limit the amount of resources which can be used by + processes forked off from the Apache children. In particular, + this will control resources used by CGI scripts and SSI exec + commands.

+ +

The ThreadStackSize directive + is used only on Netware to control the stack size.

+

Apache HTTP Server Version 2.0

IndexHome \ No newline at end of file diff --git a/docs/manual/server-wide.xml b/docs/manual/server-wide.xml new file mode 100644 index 0000000000..85d81c1a6b --- /dev/null +++ b/docs/manual/server-wide.xml @@ -0,0 +1,100 @@ + + + + + + + Server-Wide Configuration + + +

This document explains some of the directives provided by +the core server which are used to configure +the basic operations of the server.

+ + +
+ Server Identification + + + + ServerName + ServerAdmin + ServerSignature + ServerTokens + UseCanonicalName + + + +

The ServerAdmin and + ServerTokens directives + control what information about the server will be presented + in server-generated documents such as error messages. The + ServerTokens directive + sets the value of the Server HTTP response header field.

+ +

The ServerName and + UseCanonicalName + directives are used by the server to determine how to construct + self-referential URLs. For example, when a client requests a + directory, but does not include the trailing slash in the + directory name, Apache must redirect the client to the full + name including the trailing slash so that the client will + correctly resolve relative references in the document.

+
+ +
+ File Locations + + + + CoreDumpDirectory + DocumentRoot + ErrorLog + LockFile + PidFile + ScoreBoardFile + ServerRoot + + + +

These directives control the locations of the various files + that Apache needs for proper operation. When the pathname used + does not begin with a slash (/), the files are located relative + to the ServerRoot. Be careful + about locating files in paths which are writable by non-root users. + See the security tips + documentation for more details.

+
+ +
+ Limiting Resource Usage + + + + LimitRequestBody + LimitRequestFields + LimitRequestFieldsize + LimitRequestLine + RLimitCPU + RLimitMEM + RLimitNPROC + ThreadStackSize + + + +

The LimitRequest* + directives are used to place limits on the amount of resources + Apache will use in reading requests from clients. By limiting + these values, some kinds of denial of service attacks can be + mitigated.

+ +

The RLimit* directives + are used to limit the amount of resources which can be used by + processes forked off from the Apache children. In particular, + this will control resources used by CGI scripts and SSI exec + commands.

+ +

The ThreadStackSize directive + is used only on Netware to control the stack size.

+
+ -- 2.40.0