Apache module mod

From 38d73313a919b4870d0672336c157c39da1c120b Mon Sep 17 00:00:00 2001 From: Ken Coar Date: Wed, 20 May 1998 14:13:00 +0000 Subject: [PATCH] Some of my semi-regular HTML cleanup (tag ordering, B/I replacement) and long-line (>80) shortening. No thirty.. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@81320 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html | 352 +++++++++++++++------------ docs/manual/mod/mod_access.html | 12 +- docs/manual/mod/mod_actions.html | 7 +- docs/manual/mod/mod_alias.html | 47 ++-- docs/manual/mod/mod_auth.html | 6 +- docs/manual/mod/mod_auth_anon.html | 36 +-- docs/manual/mod/mod_auth_db.html | 10 +- docs/manual/mod/mod_auth_dbm.html | 6 +- docs/manual/mod/mod_autoindex.html | 26 +- docs/manual/mod/mod_cern_meta.html | 6 +- docs/manual/mod/mod_cgi.html | 8 +- docs/manual/mod/mod_dir.html | 2 +- docs/manual/mod/mod_env.html | 6 +- docs/manual/mod/mod_expires.html | 21 +- docs/manual/mod/mod_headers.html | 8 +- docs/manual/mod/mod_imap.html | 6 +- docs/manual/mod/mod_include.html | 2 +- docs/manual/mod/mod_log_agent.html | 2 +- docs/manual/mod/mod_log_config.html | 16 +- docs/manual/mod/mod_log_referer.html | 4 +- docs/manual/mod/mod_mime.html | 32 +-- docs/manual/mod/mod_mime_magic.html | 2 +- docs/manual/mod/mod_mmap_static.html | 20 +- docs/manual/mod/mod_negotiation.html | 4 +- docs/manual/mod/mod_rewrite.html | 4 +- docs/manual/mod/mod_setenvif.html | 16 +- docs/manual/mod/mod_so.html | 6 +- docs/manual/mod/mod_speling.html | 7 +- docs/manual/mod/mod_status.html | 12 +- docs/manual/mod/mod_userdir.html | 8 +- docs/manual/mod/mod_usertrack.html | 4 +- 31 files changed, 391 insertions(+), 307 deletions(-) diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index 00c40dcd2c8..fbc9725e24b 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -88,7 +88,7 @@ always available.

AccessConfig directive

server config context.

AccessFileName directive

server config context. Compatibility: AccessFileName can accept more than one filename only in Apache 1.3 and later

+>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 in every directory of the path to @@ -154,7 +155,7 @@ for directives, unless they have been disabled with AllowOverride None
</Directory>

AddModule directive

Compatibility: AddModule is only available in Apache 1.2 and later

+>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 @@ -179,7 +181,7 @@ server comes with a pre-loaded list of active modules; this list can be cleared with the ClearModuleList directive.

AllowOverride directive

XBitHack).

AuthName directive

AuthType and AuthUserFile and AuthGroupFile to work.

AuthType directive

AuthName and AuthUserFile and AuthGroupFile to work.

BindAddress directive

<VirtualHost> sections.

BS2000AuthFile directive

<VirtualHost> sections. Compatibility: BS2000AuthFile is only available for BS2000 machines, as of Apache 1.3 and later.

+>Compatibility: BS2000AuthFile is only available for +BS2000 machines, as of Apache 1.3 and later.

The BS2000AuthFile directive is available for BS2000 hosts only. It must be used to define the password file which is used to @@ -396,7 +399,7 @@ Only one BS2000AuthFile directive can be used.

ClearModuleList directive

BS2000AuthFile directive can be used.

Compatibility: ClearModuleList is only available in Apache 1.2 and later

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

ContentDigest directive

AddModule directive.

Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, +.htaccess
AddModule directive.

Compatibility: ContentDigest is only available in Apache 1.1 and later

+>Compatibility: ContentDigest is only available in +Apache 1.1 and later

This directive enables the generation of Content-MD5 headers as defined in RFC1864 respectively RFC2068.

@@ -471,7 +477,7 @@ CGI scripts, and byte range responses do not have this header.

CoreDumpDirectory directive

DefaultType directive

Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, +.htaccess

<Directory> directive

Syntax: <Directory directory> ... </Directory>
+>Syntax: <Directory directory> + ... </Directory>
-

<DirectoryMatch>

Syntax: <DirectoryMatch regex> ... </DirectoryMatch>
+>Syntax: <DirectoryMatch regex> + ... </DirectoryMatch>
Compatibility: Available in Apache 1.3 and later -

<DirectoryMatch> and </DirectoryMatch> are used to enclose a group of +

<DirectoryMatch> and </DirectoryMatch> are used to enclose a +group of directives which will apply only to the named directory and sub-directories of that directory, the same as <Directory>. However, it takes as an @@ -729,7 +739,7 @@ please avoid that.

ErrorDocument directive

Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, +.htaccess
See Also: documentation of customizable responses.

ErrorLog directive

Syntax: ErrorLog filename|syslog
+>Syntax: ErrorLog filename|syslog +
syslog instead of a filename enables logging via syslogd(8) if the system supports it.

-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. @@ -831,7 +844,7 @@ than the user that starts the server.

See also: LogLevel

<Files> directive

<FilesMatch>

Group directive

SECURITY: See User for a discussion of the security considerations.

HostNameLookups directive

Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, +.htaccess

Compatibility: double available only in Apache +>Compatibility: double available only in +Apache 1.3 and above.
Compatibility: Default was on prior to Apache -1.3.

+>Compatibility: Default was on prior to +Apache 1.3.

This directive enables DNS lookups so that host names can be logged (and passed to CGIs/SSIs in REMOTE_HOST). @@ -1036,7 +1051,7 @@ 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.

IdentityCheck directive

Syntax: <IfModule [!]module-name> ... +>Syntax: <IfModule [!]module-name> + ... </IfModule>

Include directive

Syntax: (Apache 1.2) Include filename
Compatibility: Include is only available in Apache 1.3 and later. +>Compatibility: Include is only available in Apache 1.3 +and later.

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

KeepAlive directive

Syntax: (Apache 1.1) KeepAlive max-requests
Default: (Apache 1.1) KeepAlive 5
Syntax: (Apache 1.2) KeepAlive on/off
@@ -1176,7 +1194,7 @@ server resources. Set this to 0 to disable support. persistent connections, "Off" to disable. See also the MaxKeepAliveRequests directive.

KeepAliveTimeout directive

MaxKeepAliveRequests directive.

Compatibility: KeepAliveTimeout is only available in Apache -1.1 and later.

+>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 @@ -1206,7 +1224,7 @@ HREF="#timeout">Timeout directive applies.

<Limit> directive

If you wish to limit all methods, do not include any <Limit> directive at all.

Listen directive

+Known Bugs +

ListenBacklog directive

@@ -1334,7 +1353,7 @@ tuning is needed or desired, however on some systems it is desirable to increase this when under a TCP SYN flood attack. See the backlog parameter to the listen(2) system call.

<Location> directive

.htaccess files are read, and after the <Files> sections.

Note that URLs do not have to line up with the filesystem at all, +

Note that URLs do not have to line up with the filesystem at all, it should be emphasized that <Location> operates completely outside the filesystem. -

For all origin (non-proxy) requests, the URL to be matched is -of the form /path/, and you should not include any -http://servername prefix. For proxy requests, the URL -to be matched is of the form scheme://servername/path, +

For all origin (non-proxy) requests, the URL to be matched is +of the form /path/, and you should not include any +http://servername prefix. For proxy requests, the URL +to be matched is of the form scheme://servername/path, and you must include the prefix. -

The URL may use wildcards In a wild-card string, `?' matches any +

The URL may use wildcards In a wild-card string, `?' matches any single character, and `*' matches any sequences of characters.

Apache 1.2 and above: @@ -1391,11 +1410,12 @@ For example:

"/special/data". In Apache 1.3 and above, a new directive <LocationMatch> exists which behaves identical to the regex version of -<Location>. +<Location>.

The Location functionality is especially useful when combined with the SetHandler directive. For example, to enable status requests, but allow them only +HREF="mod_mime.html#sethandler">SetHandler directive. For example, +to enable status requests, but allow them only from browsers at foo.com, you might use:

@@ -1407,22 +1427,23 @@ from browsers at foo.com, you might use:
     </Location>

Apache 1.3 and above note about / (slash): The slash character has special +

Apache 1.3 and above note about / (slash): The slash +character has special meaning depending on where in a URL it appears. People may be used to its behaviour in the filesystem where multiple adjacent slashes are -frequently collapsed to a single slash (i.e. /home///foo -is the same as /home/foo). In URL-space this is not -necessarily true. The <LocationMatch> directive -and the regex version of <Location> require you +frequently collapsed to a single slash (i.e. /home///foo +is the same as /home/foo). In URL-space this is not +necessarily true. The <LocationMatch> directive +and the regex version of <Location> require you to explicitly specify multiple slashes if that is your intention. -For example, <LocationMatch ^/abc> would match the -request URL /abc but not the request URL //abc. -The (non-regex) <Location> directive behaves +For example, <LocationMatch ^/abc> would match the +request URL /abc but not the request URL //abc. +The (non-regex) <Location> directive behaves similarly when used for proxy requests. But when (non-regex) -<Location> is used for non-proxy requests it will +<Location> is used for non-proxy requests it will implicitly match multiple slashes with a single slash. For example, -if you specify <Location /abc/def> and the request -is to /abc//def then it will match. +if you specify <Location /abc/def> and the request +is to /abc//def then it will match.

<LocationMatch>

Compatibility: LogLevel is only available in 1.3 or later. +>Compatibility: LogLevel is only available in 1.3 or +later.

LogLevel adjusts the verbosity of the messages recorded in the error logs (see ErrorLog directive). @@ -1555,7 +1577,8 @@ decreasing significance: "httpd: caught SIGBUS, attempting to dump core in ..." info Informational. - "Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..." + "Server seems busy, (you may need to increase StartServers, or + Min/MaxSpareServers)..." debug Debug-level messages "Opening config file ..." @@ -1569,7 +1592,7 @@ of higher significance will be reported as well. E.g., when Using a level of at least crit is recommended.

MaxClients directive

MaxKeepAliveRequests directive

0", unlimited requests will be allowed. We recommend that this setting be kept to a high value for maximum server performance.

MaxRequestsPerChild directive

MaxSpareServers directive

MinSpareServers and StartServers.

MinSpareServers directive

MaxSpareServers and StartServers.

NameVirtualHost directive

MaxSpareServers and Compatibility: NameVirtualHost is only available in Apache 1.3 and later

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

@@ -1754,10 +1778,10 @@ With the NameVirtualHost directive you specify the address to which your name-based virtual host names resolve. If you have multiple name-based hosts on multiple addresses, repeat the directive for each address.

-Note: the "main server" and any _default_ servers will never +Note: the "main server" and any _default_ servers will never be served for a request to a NameVirtualHost IP Address (unless for some reason you specify NameVirtualHost but then don't define any VirtualHosts -for that address).

+for that address).

Optionally you can specify a port number on which the name-based virtual hosts should be used, e.g. @@ -1767,7 +1791,7 @@ virtual hosts should be used, e.g. See also: Apache Virtual Host documentation -

Options directive

Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, +.htaccess
The server will follow symbolic links in this directory. -Note: even though the server follows the symlink it does not +Note: even though the server follows the symlink it +does not change the pathname used to match against <Directory> sections.

Includes @@ -1865,13 +1891,14 @@ Options +Includes -Indexes
then the options FollowSymLinks and Includes are set for the /web/docs/spec directory.

-Note: Using -IncludesNOEXEC or -Includes +Note: Using -IncludesNOEXEC or +-Includes disables server-side includes completely regardless of the previous setting.

The default in the absence of any other settings is All.

PidFile directive

Port directive

Status: core

-Number is a number from 0 to 65535; some port numbers (especially below +Number is a number from 0 to 65535; some port numbers +(especially below 1024) are reserved for particular protocols. See /etc/services for a list of some defined ports; the standard port for the http protocol is 80.

@@ -1978,7 +2006,7 @@ not to 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

AuthName and AuthGroupFile (to define users and groups) in order to work correctly.

ResourceConfig directive

AccessConfig.

RLimitCPU directive

Syntax: RLimitCPU # or 'max' [# or 'max']
+>Syntax: RLimitCPU # or 'max' + [# or 'max'] +
Default: Unset; uses operating system defaults
+>Default: Unset; uses operating system defaults +
AccessConfig.

Compatibility: RLimitCPU is only available in Apache 1.2 and later

+>Compatibility: RLimitCPU is only available in Apache 1.2 +and later

-Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all -processes and the second parameter sets the maximum resource limit. Either parameter -can be a number, or max to indicate to the server that the limit should -be set to the maximum allowed by the operating system configuration. Raising the -maximum resource limit requires that the server is running as root, or in the initial -startup phase.

+Takes 1 or 2 parameters. The first parameter sets the soft resource limit +for all processes and the second parameter sets the maximum resource limit. +Either parameter can be a number, or max to indicate to the server +that the limit should be set to the maximum allowed by the operating system +configuration. Raising the maximum resource limit requires that the server +is running as root, or in the initial startup phase.

CPU resource limits are expressed in seconds per process.

-See also RLimitMEM or RLimitNPROC.

+See also RLimitMEM or +RLimitNPROC.

RLimitMEM directive

Syntax: RLimitMEM # or 'max' [# or 'max']
+>Syntax: RLimitMEM # or 'max' + [# or 'max']
Default: Unset; uses operating system defaults
+>Default: Unset; uses operating system defaults +
RLimitMEM or RLimitNPRO Compatibility: RLimitMEM is only available in Apache 1.2 and later

+>Compatibility: RLimitMEM is only available in Apache 1.2 +and later

+Takes 1 or 2 parameters. The first parameter sets the soft resource limit for +all processes and the second parameter sets the maximum resource limit. Either +parameter can be a number, or max to indicate to the server that the +limit should be set to the maximum allowed by the operating system +configuration. Raising the maximum resource limit requires that the +server is running as root, or in the initial startup phase.

Memory resource limits are expressed in bytes per process.

-See also RLimitCPU or RLimitNPROC.

+See also RLimitCPU or +RLimitNPROC.

RLimitNPROC directive

Syntax: RLimitNPROC # or 'max' [# or 'max']
+>Syntax: RLimitNPROC # or 'max' + [# or 'max']
Default: Unset; uses operating system defaults
+>Default: Unset; uses operating system defaults +
RLimitCPU or RLimitNPRO Compatibility: RLimitNPROC is only available in Apache 1.2 and later

+>Compatibility: RLimitNPROC is only available in Apache +1.2 and later

Process limits control the number of processes per user.

-Note: If CGI processes are not running under userids other than the +Note: If CGI processes are not running under userids other +than the web server userid, this directive will limit the number of processes that the server itself can create. Evidence of this situation will be indicated by cannot fork messages in the error_log.

-See also RLimitMEM or RLimitCPU. +See also RLimitMEM or +RLimitCPU.

Satisfy directive

RLimitMEM or RLimitCPUCompatibility: Satisfy is only available in Apache 1.2 and later

+>Compatibility: Satisfy is only available in Apache 1.2 +and later

Access policy if both allow and require used. The parameter can be either 'all' or 'any'. This directive is only useful @@ -2204,7 +2247,7 @@ clients from particular addresses in without prompting for a password.

ScoreBoardFile directive

Default: ScoreBoardFile logs/apache_status
+>Default: ScoreBoardFile logs/apache_status +
HAVE_SHMGET would have sufficed.)

SendBufferSize directive

ServerAdmin directive

ServerAdmin www-admin@foo.bar.com as users do not always mention that they are talking about the server!

ServerAlias directive

ServerName directive

Syntax: ServerName fully-qualified domain name
+>Syntax: ServerName fully-qualified domain name +
monster.wibble.com.

ServerPath directive

name-based virtual hosts.

ServerRoot directive

Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, +.htaccess
Compatibility: ServerSignature is only available in Apache +>Compatibility: ServerSignature is only available in +Apache 1.3 and later.

The ServerSignature directive allows the configuration of a trailing @@ -2454,7 +2501,7 @@ referenced document.

ServerTokens directive

ServerTokens Full (or not specified)

Server sends (e.g.): Server: Apache/1.3.0 (UNIX) PHP/3.0 MyMod/1.2 +

Server sends (e.g.): Server: Apache/1.3.0 (UNIX) PHP/3.0 + MyMod/1.2

@@ -2504,7 +2552,7 @@ identity string.

ServerType directive

StartServers directive

ThreadsPerChild

TimeOut directive

UseCanonicalName directive

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

+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. @@ -2707,7 +2757,7 @@ self-referential URLs then it should be just fine.

User directive

Group) to root unless you know exactly what you are doing, and what the dangers are.

<VirtualHost> directive

Syntax: <VirtualHost addr[:port] ...> ... +>Syntax: <VirtualHost addr[:port] + ...> ... </VirtualHost>
</VirtualHost> -Each VirtualHost must correspond to a different IP address, different port number or a +Each VirtualHost must correspond to a different IP address, different port +number or a different host name for the server, in the latter case the server machine must be configured to accept IP packets for multiple addresses. (If the machine does not have multiple network interfaces, diff --git a/docs/manual/mod/mod_access.html b/docs/manual/mod/mod_access.html index c004dd1936b..3e5675b3d65 100644 --- a/docs/manual/mod/mod_access.html +++ b/docs/manual/mod/mod_access.html @@ -31,7 +31,7 @@ hostname or IP address.

allow directive

deny, order, and

-Syntax: allow from env=variablename
+Syntax: allow from + env=variablename
order.

deny directive

allow and order.

-Syntax: deny from env=variablename
+Syntax: deny from + env=variablename
order.

order directive

Action directive

Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, + .htaccess

Script directive

Alias directive

Alias /icons/ /usr/local/apache/icons/ then the url /icons will not be aliased.

Note that you may need to specify additional -<Directory> sections -which cover the destination of aliases. Aliasing occurs -before <Directory> sections are checked, so only +<Directory> sections +which cover the destination of aliases. Aliasing occurs +before <Directory> sections are checked, so only the destination of aliases are affected. (Note however -<Location> +<Location> sections are run through once before aliases are performed, so they will apply.)

@@ -88,7 +88,7 @@ See also ScriptAlias.

AliasMatch

/icons directory, one might use:

Redirect directive

Syntax: Redirect [ status ] url-path url
+>Syntax: Redirect [ status ] + url-path url
Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, + .htaccess
send_error_response in http_protocol.c).

RedirectMatch

Syntax: RedirectMatch [status regex url
+>Syntax: RedirectMatch [status regex url +
-

RedirectTemp directive

Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, + .htaccess
.

RedirectPermanent directive

. Context: server config, virtual host, directory, .htaccess
+>Context: server config, virtual host, directory, + .htaccess

ScriptAlias directive

Syntax: ScriptAlias url-path directory-filename
+>Syntax: ScriptAlias url-path directory-filename +
-

ScriptAliasMatch

Syntax: ScriptAliasMatch regex directory-filename
+>Syntax: ScriptAliasMatch + regex directory-filename
AuthName, Syntax: AuthAuthoritative < on(default) | off >
+>Syntax: AuthAuthoritative < + on(default) | off >
Default: By default; control is not passed on; and an unknown +>Default: By default; control is not passed on; and an + unknown userID or rule will result in an Authorization Required reply. Not setting it thus keeps the system secure; and forces an NSCA compliant behaviour. diff --git a/docs/manual/mod/mod_auth_anon.html b/docs/manual/mod/mod_auth_anon.html index e97787e08ef..3ab8b2cef25 100644 --- a/docs/manual/mod/mod_auth_anon.html +++ b/docs/manual/mod/mod_auth_anon.html @@ -40,7 +40,7 @@ allows users to share URLs. Sourcecode

Directives

Anonymous
Anonymous_Authoritative @@ -52,7 +52,7 @@ allows users to share URLs.
-
Anonymous directive
+
Anonymous directive
-
Anonymous_Authoritative directive
+
Anonymous_Authoritative directive
-
Anonymous_LogEmail directive
+
Anonymous_LogEmail directive
-
Anonymous_MustGiveEmail directive
+
Anonymous_MustGiveEmail directive
Syntax: Anonymous_MustGiveEmail on | off
+>Syntax: Anonymous_MustGiveEmail on + | off
-
Anonymous_NoUserID directive
+
Anonymous_NoUserID directive
-
Anonymous_VerifyEmail directive
+
Anonymous_VerifyEmail directive
Auth_LogEmail).
-
Example
+
Example
The example below (when combined with the Auth directives of a htpasswd-file based (or GDM, mSQL etc.) base access @@ -271,10 +272,11 @@ following properties:
It insists that the user enters a userId. (Anonymous_NoUserId)
-It insists that the user enters a password. (Anonymous_MustGiveEmail) +It insists that the user enters a password. +(Anonymous_MustGiveEmail)
-The password entered must be a valid email address, ie. contain at least one '@' and a '.'. -(Anonymous_VerifyEmail) +The password entered must be a valid email address, ie. contain at least one +'@' and a '.'. (Anonymous_VerifyEmail)
The userID must be one of anonymous guest www test welcome and comparison is not case sensitive. @@ -309,12 +311,12 @@ require valid-user

-
Compile Time Options
+
Compile Time Options
Currently there are no Compile options.
-
Revision History
+
Revision History
This version: 23 Nov 1995, 24 Feb 1996, 16 May 1996. @@ -332,11 +334,13 @@ This version: 23 Nov 1995, 24 Feb 1996, 16 May 1996.
-
Contact/person to blame
+
Contact/person to blame
This module was written for the European Wide Service Exchange by -<Dirk.vanGulik@jrc.it>. +<Dirk.vanGulik@jrc.it>. Feel free to contact me if you have any problems, ice-creams or bugs. This documentation, courtesy of Nick Himba, <himba@cs.utwente.nl>. diff --git a/docs/manual/mod/mod_auth_db.html b/docs/manual/mod/mod_auth_db.html index 111865a28ee..707e4586b91 100644 --- a/docs/manual/mod/mod_auth_db.html +++ b/docs/manual/mod/mod_auth_db.html @@ -26,8 +26,8 @@ On some BSD systems (e.g. FreeBSD and NetBSD) dbm is automatically mapped to Berkeley DB. You can use either mod_auth_dbm or mod_auth_db. The latter makes it more obvious that it's Berkeley DB. On other platforms where you want to use the DB library you usually have to -install it first. See http://www.sleepycat.com/ for the +install it first. See +http://www.sleepycat.com/ for the distribution. The interface this module uses is the one from DB version 1.85 and 1.86, but DB version 2.x can also be used when compatibility mode is enabled. @@ -157,7 +157,8 @@ See also AuthName, Syntax: AuthDBAuthoritative < on(default) | off >
+>Syntax: AuthDBAuthoritative < + on(default) | off >
Default: By default; control is not passed on; and an unknown +>Default: By default; control is not passed on; and an +unknown userID or rule will result in an Authorization Required reply. Not setting it thus keeps the system secure; and forces an NSCA compliant behaviour.
diff --git a/docs/manual/mod/mod_auth_dbm.html b/docs/manual/mod/mod_auth_dbm.html index 41f105bda19..cf194ce149d 100644 --- a/docs/manual/mod/mod_auth_dbm.html +++ b/docs/manual/mod/mod_auth_dbm.html @@ -29,7 +29,7 @@ DBM files.
-
AuthDbmGroupFile
+
AuthDbmGroupFile
AuthName, AuthType and AuthDBMUserFile.
-
AuthDBMUserFile
+
AuthDBMUserFile
AuthName, AuthDBMGroupFile.

-
AuthDBMAuthoritative
+
AuthDBMAuthoritative

-
AddAlt
+
AddAlt
String is enclosed in double quotes image-incapable or has image loading disabled.
-
AddAltByEncoding
+
AddAltByEncoding
x-compress. image-incapable or has image loading disabled.
-
AddAltByType
+
AddAltByType
-
AddDescription
+
AddDescription
String is enclosed in double quotes
AddDescription "The planet Mars" /web/pics/mars.gif
-
AddIcon
+
AddIcon
AddIconByType should be used in preference to AddIcon, when possible.
-
AddIconByEncoding
+
AddIconByEncoding

-
AddIconByType
+
AddIconByType

-
DefaultIcon
+
DefaultIcon
FancyIndexing. DefaultIcon /icon/unknown.xbm
-
FancyIndexing
+
FancyIndexing

-
HeaderName
+
HeaderName
/web/HEADER, if it exists.
See also ReadmeName.
-
IndexIgnore
+
IndexIgnore
.'. Example: IndexIgnore README .htaccess *~
-
IndexOptions
+
IndexOptions
then only ScanHTMLTitles will be set for the /web/docs/spec directory.
-
ReadmeName
+
ReadmeName
-
MetaFiles
+
MetaFiles
Turns on/off Meta file processing on a per-directory basis. This option was introduced in Apache 1.3. -
MetaDir
+
MetaDir
." to look in the same directory as the file. -
MetaSuffix
+
MetaSuffix
-
CGI Debugging
+
CGI Debugging
Debugging CGI scripts has traditionally been difficult, mainly because it has @@ -113,7 +113,7 @@ anything on standard output or standard error).
Directives
-
ScriptLog
+
ScriptLog
-
ScriptLogLength
+
ScriptLogLength
ScriptLogBuffer +
ScriptLogBuffer
mod_dir issues a redirect to
-
DirectoryIndex
+
DirectoryIndex
-
PassEnv
+
PassEnv
-
SetEnv
+
SetEnv
-
UnsetEnv
+
UnsetEnv
Apache module mod_expires - + Context: server config, virtual host, directory, .htaccess + >Context: server config, virtual host, directory, + .htaccess
Syntax: ExpiresByType mime-type <code>seconds + >Syntax: ExpiresByType mime-type + <code>seconds
Context: server config, virtual host, directory, .htaccess + >Context: server config, virtual host, directory, + .htaccess
Context: server config, virtual host, directory, .htaccess + >Context: server config, virtual host, directory, + .htaccess

ExpiresDefault "<base> [plus] {<num> <type>}*" - ExpiresByType type/encoding "<base> [plus] {<num> <type>}*" + ExpiresByType type/encoding "<base> [plus] + {<num> <type>}*"

@@ -302,8 +307,8 @@
- The expiry time can be fine-tuned by adding several '<num> <type>' - clauses: + The expiry time can be fine-tuned by adding several '<num> + <type>' clauses:
ExpiresByType text/html "access plus 1 month 15 days 2 hours" diff --git a/docs/manual/mod/mod_headers.html b/docs/manual/mod/mod_headers.html index 9d34c3bbefa..7d62d5d1fd3 100644 --- a/docs/manual/mod/mod_headers.html +++ b/docs/manual/mod/mod_headers.html @@ -29,11 +29,12 @@ compiled with mod_headers.c. -Header +Header Syntax: Header [ set | append | add ] header value +>Syntax: Header [ set | append | add ] + header value mod_headers.c. Context: server config, virtual host, access.conf, .htaccess +>Context: server config, virtual host, access.conf, + .htaccess -ImapMenu +ImapMenu -ImapDefault +ImapDefault -ImapBase +ImapBase -XBitHack +XBitHack -AgentLog +AgentLog "%h %l extending for format if desired (e.g. to add extra fields at the end). NCSA's extended/combined log format would be "%h %l %u %t \"%r\" %s %b \"%{Referer}i\" \"%{User-agent}i\"". - + -Note that the canonical ServerName -and Port of the server serving the request -are used for %v and %p respectively. This +Note that the canonical ServerName +and Port of the server serving the request +are used for %v and %p respectively. This happens regardless of the -UseCanonicalName setting because +UseCanonicalName setting because otherwise log analysis programs would have to duplicate the entire vhost matching algorithm in order to decide what host really served the request. @@ -201,7 +201,7 @@ the user that starts the server. -CookieLog +CookieLog -LogFormat +LogFormat -TransferLog +TransferLog -RefererIgnore +RefererIgnore -RefererLog +RefererLog -AddEncoding +AddEncoding -Old clients expect x-gzip and x-compress, -however the standard dictates that they're equivalent to gzip -and compress respectively. Apache does content encoding -comparisons by ignoring any leading x-. When responding -with an encoding Apache will use whatever form (i.e. x-foo -or foo) the client requested. If the client didn't +Old clients expect x-gzip and x-compress, +however the standard dictates that they're equivalent to gzip +and compress respectively. Apache does content encoding +comparisons by ignoring any leading x-. When responding +with an encoding Apache will use whatever form (i.e. x-foo +or foo) the client requested. If the client didn't specifically request a particular form Apache will use the form given by -the AddEncoding directive. To make this long story short, -you should always use x-gzip and x-compress +the AddEncoding directive. To make this long story short, +you should always use x-gzip and x-compress for these two specific encodings. More recent encodings, such as -deflate should be specified without the x-. +deflate should be specified without the x-. -AddHandler +AddHandler .cgi" will be treated as a CGI program.

-
AddLanguage
+
AddLanguage

-
AddType
+
AddType
TypesConfig file.
Note that, unlike the NCSA httpd, this directive cannot be used to set the type of particular files.
-
ForceType
+
ForceType
Note that this will override any filename extensions that might determine the media type.
-
SetHandler
+
SetHandler

-
TypesConfig
+
TypesConfig

-
Notes
+
Notes
The following notes apply to the mod_mime_magic module and are included here for compliance with contributors' copyright restrictions diff --git a/docs/manual/mod/mod_mmap_static.html b/docs/manual/mod/mod_mmap_static.html index 57b1273b597..77100488eaf 100644 --- a/docs/manual/mod/mod_mmap_static.html +++ b/docs/manual/mod/mod_mmap_static.html @@ -30,7 +30,7 @@ This is an experimental module and should be used with care. You can easily create a broken site using this module, read this document carefully. - mod_mmap_static maps a list of statically configured files (via + mod_mmap_static maps a list of statically configured files (via MMapFile directives in the main server configuration) into memory through the system call mmap(). This system call is available on most modern Unix derivates, but not on all. There @@ -41,7 +41,7 @@ This mmap()ing is done once at server start or restart, only. So whenever one of the mapped files changes on the filesystem you have to restart the server by at least sending it a HUP or USR1 signal (see the - Stopping and Restarting documentation). To + Stopping and Restarting documentation). To reiterate that point: if the files are modified in place without restarting the server you may end up serving requests that are completely bogus. You should update files by unlinking the old copy and putting a new @@ -110,8 +110,8 @@ create. We cannot compare inodes or other stuff to match paths through symbolic links etc. because that again would cost extra stat() system calls which is not acceptable. This module may or may not work - with filenames rewritten by mod_alias or - mod_rewrite... it is an experiment after all. + with filenames rewritten by mod_alias or + mod_rewrite... it is an experiment after all.

@@ -127,13 +127,15 @@
- Note: don't bother asking for a for a MMapDir directive which + Note: don't bother asking for a for a MMapDir + directive which recursively maps all the files in a directory. Use Unix the way it was meant to be used. For example, see the - Include directive, and consider this command: -
```
-  find /www/htdocs -type f -print | sed -e 's/.*/mmapfile &/' > /www/conf/mmap.conf
-  
```
+ Include directive, and consider this command: +
```
+  find /www/htdocs -type f -print \
+  | sed -e 's/.*/mmapfile &/' > /www/conf/mmap.conf
+  
```
diff --git a/docs/manual/mod/mod_negotiation.html b/docs/manual/mod/mod_negotiation.html index 4102fc49967..e2578bd27db 100644 --- a/docs/manual/mod/mod_negotiation.html +++ b/docs/manual/mod/mod_negotiation.html @@ -94,7 +94,7 @@ requirements, and returns that document.

-
CacheNegotiatedDocs
+
CacheNegotiatedDocs
LanguagePriority +
LanguagePriority
Quantifiers: ? 0 or 1 of the preceding text - * 0 or N of the preceding text (N > 1) - + 1 or N of the preceding text (N > 1) + * 0 or N of the preceding text (N > 1) + + 1 or N of the preceding text (N > 1) Grouping: (text) Grouping of text diff --git a/docs/manual/mod/mod_setenvif.html b/docs/manual/mod/mod_setenvif.html index 46a91d5db85..4d2b26fac74 100644 --- a/docs/manual/mod/mod_setenvif.html +++ b/docs/manual/mod/mod_setenvif.html @@ -26,15 +26,15 @@ regular expressions you specify. These envariables can be used by other parts of the server to make decisions about actions to be taken.
-
The directives are considered in the order they appear in the +
The directives are considered in the order they appear in the configuration files. So more complex sequences can be used, such - as this example, which sets netscape if the browser + as this example, which sets netscape if the browser is mozilla but not MSIE. -
+
BrowserMatch ^Mozilla netscape BrowserMatch MSIE !netscape -
-
+
+

Directives