From a63f6aae96f9b45c7ef596e6d45bfc14c702a67a Mon Sep 17 00:00:00 2001 From: Erik Abele Date: Thu, 5 Sep 2002 23:15:34 +0000 Subject: [PATCH] Updated XML plus transformations. Whhups, this is a big one :-) git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96655 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html.en | 1548 +++++++++++---------- docs/manual/mod/directives.html.en | 8 +- docs/manual/mod/directives.html.ja.jis | 12 +- docs/manual/mod/directives.xml | 13 + docs/manual/mod/index.html.en | 12 +- docs/manual/mod/index.html.ja.jis | 28 +- docs/manual/mod/mod_access.html.en | 182 +-- docs/manual/mod/mod_access.html.ja.jis | 204 +-- docs/manual/mod/mod_actions.html.en | 90 +- docs/manual/mod/mod_alias.html.en | 198 +-- docs/manual/mod/mod_asis.html.en | 48 +- docs/manual/mod/mod_auth.html.en | 114 +- docs/manual/mod/mod_auth.html.ja.jis | 116 +- docs/manual/mod/mod_auth_anon.html.en | 170 +-- docs/manual/mod/mod_auth_dbm.html.en | 108 +- docs/manual/mod/mod_auth_digest.html.en | 172 +-- docs/manual/mod/mod_auth_ldap.html.en | 425 +++--- docs/manual/mod/mod_autoindex.html.en | 444 +++--- docs/manual/mod/mod_autoindex.html.ja.jis | 454 +++--- docs/manual/mod/mod_cache.html.en | 267 ++-- docs/manual/mod/mod_cache.xml | 41 +- docs/manual/mod/mod_cern_meta.html.en | 72 +- docs/manual/mod/mod_cgi.html.en | 114 +- docs/manual/mod/mod_cgid.html.en | 44 +- docs/manual/mod/mod_charset_lite.html.en | 110 +- docs/manual/mod/mod_dav.html.en | 126 +- docs/manual/mod/mod_dav.html.ja.jis | 132 +- docs/manual/mod/mod_deflate.html.en | 88 +- docs/manual/mod/mod_deflate.html.ja.jis | 92 +- docs/manual/mod/mod_dir.html.en | 50 +- docs/manual/mod/mod_dir.html.ja.jis | 58 +- docs/manual/mod/mod_disk_cache.html.en | 316 ++--- docs/manual/mod/mod_echo.html.en | 38 +- docs/manual/mod/mod_env.html.en | 72 +- docs/manual/mod/mod_env.html.ja.jis | 74 +- docs/manual/mod/mod_example.html.en | 56 +- docs/manual/mod/mod_expires.html.en | 111 +- docs/manual/mod/mod_ext_filter.html.en | 211 ++- docs/manual/mod/mod_ext_filter.xml | 154 +- docs/manual/mod/mod_file_cache.html.en | 90 +- docs/manual/mod/mod_headers.html.en | 108 +- docs/manual/mod/mod_imap.html.en | 134 +- docs/manual/mod/mod_include.html.en | 281 ++-- docs/manual/mod/mod_info.html.en | 66 +- docs/manual/mod/mod_info.xml | 4 +- docs/manual/mod/mod_isapi.html.en | 144 +- docs/manual/mod/mod_ldap.html.en | 153 +- docs/manual/mod/mod_log_config.html.en | 146 +- docs/manual/mod/mod_mem_cache.html.en | 144 +- docs/manual/mod/mod_mime.html.en | 544 ++++---- docs/manual/mod/mod_mime.xml | 41 +- docs/manual/mod/mod_mime_magic.html.en | 66 +- docs/manual/mod/mod_negotiation.html.en | 114 +- docs/manual/mod/mod_proxy.html.en | 506 +++---- docs/manual/mod/mod_rewrite.html.en | 664 +++++---- docs/manual/mod/mod_rewrite.xml | 160 +-- docs/manual/mod/mod_setenvif.html.en | 174 +-- docs/manual/mod/mod_so.html.en | 66 +- docs/manual/mod/mod_so.html.ja.jis | 72 +- docs/manual/mod/mod_speling.html.en | 38 +- docs/manual/mod/mod_ssl.html.en | 804 +++++------ docs/manual/mod/mod_ssl.xml | 94 +- docs/manual/mod/mod_status.html.en | 72 +- docs/manual/mod/mod_suexec.html.en | 38 +- docs/manual/mod/mod_suexec.html.ja.jis | 36 +- docs/manual/mod/mod_unique_id.html.en | 18 +- docs/manual/mod/mod_userdir.html.en | 52 +- docs/manual/mod/mod_userdir.html.ja.jis | 58 +- docs/manual/mod/mod_usertrack.html.en | 106 +- docs/manual/mod/mod_vhost_alias.html.en | 124 +- docs/manual/mod/mpm_common.html.en | 418 +++--- docs/manual/mod/mpm_common.html.ja.jis | 424 +++--- docs/manual/mod/mpm_netware.html.en | 48 +- docs/manual/mod/mpm_winnt.html.en | 16 +- docs/manual/mod/mpm_winnt.html.ja.jis | 18 +- docs/manual/mod/perchild.html.en | 68 +- docs/manual/mod/prefork.html.en | 84 +- docs/manual/mod/prefork.html.ja.jis | 96 +- docs/manual/mod/worker.html.en | 50 +- docs/manual/mod/worker.html.ja.jis | 62 +- 80 files changed, 6467 insertions(+), 6506 deletions(-) diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 2f58cad7a7..ca839940b0 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -1,19 +1,21 @@ -core - Apache HTTP Server
[APACHE DOCUMENTATION]

Apache HTTP Server Version 2.0

Apache Module core

Description: - Core Apache HTTP Server features that are always -available
Status: - Core

Directives

AcceptPathInfo Directive

Description: - Resources accept trailing pathname information
Syntax: - AcceptPathInfo On|Off|Default
Default: - AcceptPathInfo Default
Context: - server config, virtual host, directory, .htaccess
Override: - FileInfo
Status: - Core
Module: - core
Compatibility: - Available in Apache 2.0.30 and later
+ -->core - Apache HTTP Server

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.0

<-

Apache Module core

Description: + Core Apache HTTP Server features that are always +available
Status: + Core
top

AcceptPathInfo Directive

Description: + Resources accept trailing pathname information
Syntax: + AcceptPathInfo On|Off|Default
Default: + AcceptPathInfo Default
Context: + server config, virtual host, directory, .htaccess
Override: + FileInfo
Status: + Core
Module: + core
Compatibility: + Available in Apache 2.0.30 and later

This directive controls whether requests that contain trailing pathname information that follows an actual filename (or @@ -57,29 +59,29 @@ available -

-<Files "mypaths.shtml">
- Options +Includes
- SetOutputFilter INCLUDES
- AcceptPathInfo on
+

+<Files "mypaths.shtml">
+ Options +Includes
+ SetOutputFilter INCLUDES
+ AcceptPathInfo on
</Files> -

-

AccessFileName Directive

Description: - Name of the distributed configuration file
Syntax: - AccessFileName filename [filename] ...
Default: - AccessFileName .htaccess
Context: - server config, virtual host
Status: - Core
Module: - core
+

+
top

AccessFileName Directive

Description: + Name of the distributed configuration file
Syntax: + AccessFileName filename [filename] ...
Default: + AccessFileName .htaccess
Context: + server config, virtual host
Status: + Core
Module: + core

When returning a document to the client the server looks for the first existing configuration file from this list of names in every directory of the path to the document, if distributed configuration files are enabled for that directory. For example:

-
+

AccessFileName .acl -

+

before returning the document /usr/local/web/index.html, the server will read @@ -87,20 +89,20 @@ AccessFileName .acl /usr/local/.acl and /usr/local/web/.acl for directives, unless they have been disabled with

-
-<Directory />
-  AllowOverride None
+

+<Directory />
+  AllowOverride None
</Directory> -

-

See also

AddDefaultCharset Directive

Description: - Default character set to be added for a -response without an explicit character set
Syntax: - AddDefaultCharset On|Off|charset
Default: - AddDefaultCharset Off
Context: - server config, virtual host, directory, .htaccess
Override: - FileInfo
Status: - Core
Module: - core
+

+

See also

top

AddDefaultCharset Directive

Description: + Default character set to be added for a +response without an explicit character set
Syntax: + AddDefaultCharset On|Off|charset
Default: + AddDefaultCharset Off
Context: + server config, virtual host, directory, .htaccess
Override: + FileInfo
Status: + Core
Module: + core

This directive specifies the name of the character set that will be added to any response that does not have any parameter on @@ -113,19 +115,19 @@ response without an explicit character setcharset to be used. For example:

-
+

AddDefaultCharset utf-8 -

-

AllowOverride Directive

Description: - Types of directives that are allowed in -.htaccess files
Syntax: - AllowOverride All|None|directive-type -[directive-type] ...
Default: - AllowOverride All
Context: - directory
Status: - Core
Module: - core
-

When the server finds an .htaccess file (as specified by AccessFileName) it needs to know +

+
top

AllowOverride Directive

Description: + Types of directives that are allowed in +.htaccess files
Syntax: + AllowOverride All|None|directive-type +[directive-type] ...
Default: + AllowOverride All
Context: + directory
Status: + Core
Module: + core
+

When the server finds an .htaccess file (as specified by AccessFileName) it needs to know which directives declared in that file can override earlier access information.

@@ -146,109 +148,109 @@ response without an explicit character set - Allow use of the authorization directives (AuthDBMGroupFile, - AuthDBMUserFile, - AuthGroupFile, - AuthName, - AuthType, AuthUserFile, Require, etc.). + Allow use of the authorization directives (AuthDBMGroupFile, + AuthDBMUserFile, + AuthGroupFile, + AuthName, + AuthType, AuthUserFile, Require, etc.).
FileInfo
- Allow use of the directives controlling document types (DefaultType, ErrorDocument, ForceType, LanguagePriority, - SetHandler, SetInputFilter, SetOutputFilter, and - mod_mime Add* and Remove* + Allow use of the directives controlling document types (DefaultType, ErrorDocument, ForceType, LanguagePriority, + SetHandler, SetInputFilter, SetOutputFilter, and + mod_mime Add* and Remove* directives, etc.).
Indexes
Allow use of the directives controlling directory indexing - (AddDescription, - AddIcon, AddIconByEncoding, - AddIconByType, - DefaultIcon, DirectoryIndex, FancyIndexing, HeaderName, IndexIgnore, IndexOptions, ReadmeName, + (AddDescription, + AddIcon, AddIconByEncoding, + AddIconByType, + DefaultIcon, DirectoryIndex, FancyIndexing, HeaderName, IndexIgnore, IndexOptions, ReadmeName, etc.).
Limit
- Allow use of the directives controlling host access (Allow, Deny and Order).
+ Allow use of the directives controlling host access (Allow, Deny and Order).
Options
Allow use of the directives controlling specific directory - features (Options and - XBitHack).
+ features (Options and + XBitHack).

Example:

-
AllowOverride AuthConfig Indexes
-

See also

AuthName Directive

Description: - Authorization realm for use in HTTP -authentication
Syntax: - AuthName auth-domain
Context: - directory, .htaccess
Override: - AuthConfig
Status: - Core
Module: - core
+

AllowOverride AuthConfig Indexes

+

See also

top

AuthName Directive

Description: + Authorization realm for use in HTTP +authentication
Syntax: + AuthName auth-domain
Context: + directory, .htaccess
Override: + AuthConfig
Status: + Core
Module: + core

This directive sets the name of the authorization realm for a directory. This realm is given to the client so that the user knows which username and password to send. AuthName takes a single argument; if the realm name contains spaces, it must be enclosed in quotation - marks. It must be accompanied by AuthType and Require directives, and directives such - as AuthUserFile and - AuthGroupFile to + marks. It must be accompanied by AuthType and Require directives, and directives such + as AuthUserFile and + AuthGroupFile to work.

For example:

-
AuthName "Top Secret"
+

AuthName "Top Secret"

The string provided for the AuthRealm is what will appear in the password dialog provided by most browsers.

-

See also

AuthType Directive

Description: - Type of user authentication
Syntax: - AuthType Basic|Digest
Context: - directory, .htaccess
Override: - AuthConfig
Status: - Core
Module: - core
+

See also

top

AuthType Directive

Description: + Type of user authentication
Syntax: + AuthType Basic|Digest
Context: + directory, .htaccess
Override: + AuthConfig
Status: + Core
Module: + core

This directive selects the type of user authentication for a directory. Only Basic and Digest are currently implemented. - It must be accompanied by AuthName and Require directives, and directives such - as AuthUserFile and - AuthGroupFile to + It must be accompanied by AuthName and Require directives, and directives such + as AuthUserFile and + AuthGroupFile to work.

-

See also

CGIMapExtension Directive

Description: - Technique for locating the interpreter for CGI -scripts
Syntax: - CGIMapExtension cgi-path .extension
Default: - None
Context: - directory, .htaccess
Override: - FileInfo
Status: - Core
Module: - core
Compatibility: - NetWare only
+

See also

top

CGIMapExtension Directive

Description: + Technique for locating the interpreter for CGI +scripts
Syntax: + CGIMapExtension cgi-path .extension
Default: + None
Context: + directory, .htaccess
Override: + FileInfo
Status: + Core
Module: + core
Compatibility: + NetWare only

This directive is used to control how Apache finds the interpreter used to run CGI scripts. For example, setting CGIMapExtension sys:\foo.nlm .foo will cause all CGI script files with a .foo extension to be passed to the FOO interpreter.

-

ContentDigest Directive

Description: - Enables the generation of Content-MD5 HTTP Response -headers
Syntax: - ContentDigest on|off
Default: - ContentDigest off
Context: - server config, virtual host, directory, .htaccess
Override: - Options
Status: - Core
Module: - core
+
top

ContentDigest Directive

Description: + Enables the generation of Content-MD5 HTTP Response +headers
Syntax: + ContentDigest on|off
Default: + ContentDigest off
Context: + server config, virtual host, directory, .htaccess
Override: + Options
Status: + Core
Module: + core

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

@@ -262,9 +264,9 @@ headers -
+

Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA== -

+

Note that this can cause performance problems on your server since the message digest is computed on every request (the @@ -274,15 +276,15 @@ headers -

DefaultType Directive

Description: - MIME content-type that will be sent if the -server cannot determine a type in any other way
Syntax: - DefaultType MIME-type
Default: - DefaultType text/plain
Context: - server config, virtual host, directory, .htaccess
Override: - FileInfo
Status: - Core
Module: - core
+
top

DefaultType Directive

Description: + MIME content-type that will be sent if the +server cannot determine a type in any other way
Syntax: + DefaultType MIME-type
Default: + DefaultType text/plain
Context: + server config, virtual host, directory, .htaccess
Override: + FileInfo
Status: + Core
Module: + core

There will be times when the server is asked to provide a document whose type cannot be determined by its MIME types mappings.

@@ -291,24 +293,24 @@ server cannot determine a type in any other wayDefaultType. For example:

-
+

DefaultType image/gif -

+

would be appropriate for a directory which contained many gif images with filenames missing the .gif extension.

-

Note that unlike ForceType, this directive is only +

Note that unlike ForceType, this directive is only provides the default mime-type. All other mime-type definitions, including filename extensions, that might identify the media type will override this default.

-

<Directory> Directive

Description: - Enclose a group of directives that apply only to the -named file-system directory and sub-directories
Syntax: - <Directory directory-path> -... </Directory>
Context: - server config, virtual host
Status: - Core
Module: - core
+
top

<Directory> Directive

Description: + Enclose a group of directives that apply only to the +named file-system directory and sub-directories
Syntax: + <Directory directory-path> +... </Directory>
Context: + server config, virtual host
Status: + Core
Module: + core

<Directory> and </Directory> are used to enclose a group of directives that will apply only to the named directory and @@ -322,26 +324,26 @@ named file-system directory and sub-directories will not match /home/user/public_html, but <Directory /home/*/public_html> will match. Example:

-
- <Directory /usr/local/httpd/htdocs>
-  Options Indexes FollowSymLinks
- </Directory>
-
+

+ <Directory /usr/local/httpd/htdocs>
+  Options Indexes FollowSymLinks
+ </Directory>
+

-
+

Be careful with the directory-path arguments: They have to literally match the filesystem path which Apache uses to access the files. Directives applied to a particular <Directory> will not apply to files accessed from that same directory via a different path, such as via different symbolic links.

-
+

Extended regular expressions can also be used, with the addition of the ~ character. For example:

-
+

<Directory ~ "^/www/.*/[0-9]{3}"> -

+

would match directories in /www/ that consisted of three numbers.

@@ -351,15 +353,15 @@ such as via different symbolic links.

first, interspersed with the directives from the .htaccess files. For example, with

-
- <Directory />
-   AllowOverride None
- </Directory>
-
- <Directory /home/>
-   AllowOverride FileInfo
+

+ <Directory />
+   AllowOverride None
+ </Directory>
+
+ <Directory /home/>
+   AllowOverride FileInfo
</Directory> -

+

for access to the document /home/web/dir/doc.html the steps are:

@@ -379,10 +381,10 @@ such as via different symbolic links.

expressions are tested in the order they appeared in the configuration file. For example, with

-
<Directory ~ abc$>
- ... directives here ...
- </Directory>
-
+

<Directory ~ abc$>
+ ... directives here ...
+ </Directory>
+

The regular expression section won't be considered until after all normal <Directory>s and .htaccess files @@ -395,12 +397,12 @@ such as via different symbolic links.

recommended that you change this with a block such as

-
- <Directory />
-   Order Deny,Allow
-   Deny from All
+

+ <Directory />
+   Order Deny,Allow
+   Deny from All
</Directory> -

+

and then override this for directories you want accessible. See the Security Tips page for more @@ -409,69 +411,69 @@ such as via different symbolic links.

The directory sections typically occur in the access.conf file, but they may appear in any configuration file. <Directory> directives - cannot nest, and cannot appear in a <Limit> or <LimitExcept> section.

-

See also

EnableMMAP DocumentRoot, +
  • With an NFS-mounted DocumentRoot, the httpd may crash due tof a segmentation fault if a file is deleted or truncated while the httpd has it memory-mapped.
    • @@ -490,19 +492,19 @@ Location

    EnableMMAP +

    EnableMMAP off -

    -

    ErrorDocument Directive

    Description: - What the server will return to the client -in case of an error
    Syntax: - ErrorDocument error-code document
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Core
    Module: - core
    Compatibility: - Quoting syntax for text messages is different in Apache -2.0
    +

    +
    top

    ErrorDocument Directive

    Description: + What the server will return to the client +in case of an error
    Syntax: + ErrorDocument error-code document
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Core
    Module: + core
    Compatibility: + Quoting syntax for text messages is different in Apache +2.0

    In the event of a problem or error, Apache can be configured to do one of four things,

    @@ -528,14 +530,14 @@ in case of an error +

    ErrorDocument 500 - http://foo.example.com/cgi-bin/tester
    - ErrorDocument 404 /cgi-bin/bad_urls.pl
    - ErrorDocument 401 /subscription_info.html
    + http://foo.example.com/cgi-bin/tester
    + ErrorDocument 404 /cgi-bin/bad_urls.pl
    + ErrorDocument 401 /subscription_info.html
    ErrorDocument 403 "Sorry can't allow you access today" -     +

    Note that when you specify an ErrorDocument that points to a remote URL (ie. anything with a method such as @@ -563,19 +565,19 @@ in case of an errordocumentation of - customizable responses

    ErrorLog Directive

    Description: - Location where the server will log errors
    Syntax: - ErrorLog file-path|syslog[:facility]
    Default: - ErrorLog logs/error_log (Unix) -ErrorLog logs/error.log (Windows and OS/2)
    Context: - server config, virtual host
    Status: - Core
    Module: - core
    +

    See also

    top

    ErrorLog Directive

    Description: + Location where the server will log errors
    Syntax: + ErrorLog file-path|syslog[:facility]
    Default: + ErrorLog logs/error_log (Unix) +ErrorLog logs/error.log (Windows and OS/2)
    Context: + server config, virtual host
    Status: + Core
    Module: + core

    The ErrorLog directive sets the name of the file to which the server will log any errors it encounters. If the file-path does not begin with a slash (/) then it is - assumed to be relative to the ServerRoot. If the file-path + assumed to be relative to the ServerRoot. If the file-path begins with a pipe (|) then it is assumed to be a command to spawn to handle the error log.

    @@ -590,15 +592,15 @@ ErrorLog logs/error.log (Windows and OS/2)LogLevel
  • Apache Log Files

    • FileETag Directive

    Description: - File attributes used to create the ETag -HTTP response header
    Syntax: - FileETag component ...
    Default: - FileETag INode MTime Size
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Core
    Module: - core
    +

    See also

    top

    FileETag Directive

    Description: + File attributes used to create the ETag +HTTP response header
    Syntax: + FileETag component ...
    Default: + FileETag INode MTime Size
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Core
    Module: + core

    The FileETag directive configures the file attributes that are used to create the ETag (entity tag) response @@ -618,7 +620,7 @@ HTTP response header<Files> Directive
    Description: - Contains directives that apply to matched -filenames
    Syntax: - <Files filename> ... </Files>
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    +

    top

    <Files> Directive

    Description: + Contains directives that apply to matched +filenames
    Syntax: + <Files filename> ... </Files>
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    The <Files> directive provides for access control by filename. It is comparable to the - Directory - directive and Location directives. It should be + Directory + directive and Location directives. It should be matched with a </Files> directive. The directives given within this section will be applied to any object with a basename (not a full path) matching the specified filename. <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. Note + configuration file, after the <Directory> sections and + .htaccess files are read, but before <Location> sections. Note that <Files> can be nested - inside <Directory> sections to restrict the + inside <Directory> sections to restrict the portion of the filesystem they apply to.

    The filename argument should include a filename, or @@ -666,70 +668,70 @@ filenames~ character. For example:

    -
    +

    <Files ~ "\.(gif|jpe?g|png)$"> -

    +

    would match most common Internet graphics formats. In Apache 1.3 - and later, <FilesMatch> is preferred, however.

    + and later, <FilesMatch> is preferred, however.

    -

    Note that unlike <Directory> and <Location> sections, <Files> sections can be used inside +

    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.

    -

    See also

    top

    <FilesMatch> Directive

    Description: + Contains directives that apply to regular-expression matched +filenames
    Syntax: + <FilesMatch regex> ... </FilesMatch>
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    The <FilesMatch> directive - provides for access control by filename, just as the <Files> directive + provides for access control by filename, just as the <Files> directive does. However, it accepts a regular expression. For example:

    -
    +

    <FilesMatch "\.(gif|jpe?g|png)$"> -

    +

    would match most common Internet graphics formats.

    -

    See also

    top

    ForceType Directive

    Description: + Forces all matching files to be served with the specified +MIME content-type
    Syntax: + ForceType mime-type
    Context: + directory, .htaccess
    Override: + FileInfo
    Status: + Core
    Module: + core
    Compatibility: + Moved to the core in Apache 2.0

    When placed into an .htaccess file or a - <Directory>, or - <Location> or - <Files> + <Directory>, or + <Location> or + <Files> section, this directive forces all matching files to be served with the content type identification given by mime-type. For example, if you had a directory full of GIF files, but did not want to label them all with ".gif", you might want to use:

    -
    +

    ForceType image/gif -

    +

    -

    Note that unlike DefaultType, +

    Note that unlike DefaultType, this directive overrides all mime-type associations, including filename extensions, that might identify the media type.

    -

    HostnameLookups Directive

    Description: - Enables DNS lookups on client IP addresses
    Syntax: - HostnameLookups on|off|double
    Default: - HostnameLookups off
    Context: - server config, virtual host, directory
    Status: - Core
    Module: - core
    +
    top

    HostnameLookups Directive

    Description: + Enables DNS lookups on client IP addresses
    Syntax: + HostnameLookups on|off|double
    Default: + HostnameLookups off
    Context: + server config, virtual host, directory
    Status: + Core
    Module: + core

    This directive enables DNS lookups so that host names can be logged (and passed to CGIs/SSIs in REMOTE_HOST). The value double refers to doing double-reverse @@ -739,7 +741,7 @@ MIME content-typePARANOID.)

    -

    Regardless of the setting, when mod_access is +

    Regardless of the setting, when mod_access is used for controlling access by hostname, a double reverse lookup will be performed. This is necessary for security. Note that the result of this double-reverse isn't generally available unless you @@ -758,14 +760,14 @@ MIME content-typelogresolve, provided in the /support directory, can be used to look up host names from logged IP addresses offline.

    -

    IdentityCheck Directive

    Description: - Enables logging of the RFC1413 identity of the remote -user
    Syntax: - IdentityCheck on|off
    Default: - IdentityCheck off
    Context: - server config, virtual host, directory
    Status: - Core
    Module: - core
    +
    top

    IdentityCheck Directive

    Description: + Enables logging of the RFC1413 identity of the remote +user
    Syntax: + IdentityCheck on|off
    Default: + IdentityCheck off
    Context: + server config, virtual host, directory
    Status: + Core
    Module: + core

    This directive enables RFC1413-compliant logging of the remote user name for each connection, where the client machine runs identd or something similar. This information is logged in @@ -780,15 +782,15 @@ user -

    <IfDefine> Directive

    Description: - Encloses directives that will be processed only -if a test is true at startup
    Syntax: - <IfDefine [!]parameter-name> ... - </IfDefine>
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    +
    top

    <IfDefine> Directive

    Description: + Encloses directives that will be processed only +if a test is true at startup
    Syntax: + <IfDefine [!]parameter-name> ... + </IfDefine>
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    The <IfDefine test>...</IfDefine> section is used to mark directives that are conditional. The directives within an @@ -819,7 +821,7 @@ if a test is true at startup<IfDefine> sections are nest-able, which can be used to implement simple multiple-parameter tests. Example:

    -
    +
       $ httpd -DReverseProxy ...
 
   # httpd.conf
@@ -827,17 +829,17 @@ if a test is true at startup
    <IfModule> Directive
    Description: - Encloses directives that are processed conditional on the -presence of absence of a specific module
    Syntax: - <IfModule [!]module-name> ... - </IfModule>
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    + + +
    top

    <IfModule> Directive

    Description: + Encloses directives that are processed conditional on the +presence of absence of a specific module
    Syntax: + <IfModule [!]module-name> ... + </IfModule>
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    The <IfModule test>...</IfModule> section is used to mark directives that are conditional. The directives within an @@ -857,7 +859,7 @@ presence of absence of a specific module

    In the former case, the directives between the start and end markers are only processed if the module named module name is included in Apache -- either compiled in or - dynamically loaded using LoadModule. The second format + dynamically loaded using LoadModule. The second format reverses the test, and only processes the directives if module name is not included.

    @@ -868,13 +870,13 @@ presence of absence of a specific module
    <IfModule> sections are nest-able, which can be used to implement simple multiple-module tests.

    -

    Include Directive

    Description: - Includes other configuration files from within -the server configuration files
    Syntax: - Include file-path|directory-path
    Context: - server config, virtual host, directory
    Status: - Core
    Module: - core
    +
    top

    Include Directive

    Description: + Includes other configuration files from within +the server configuration files
    Syntax: + Include file-path|directory-path
    Context: + server config, virtual host, directory
    Status: + Core
    Module: + core

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

    @@ -885,22 +887,22 @@ the server configuration files
    ServerRoot directory.

    + ServerRoot directory.

    Examples:

    -
    - Include /usr/local/apache/conf/ssl.conf
    +

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

    +

    Or, providing paths relative to your ServerRoot directory:

    -
    - Include conf/ssl.conf
    +

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

    +

    Make sure that an included directory does not contain any stray files, such as editor temporary files, for example, as Apache will @@ -910,23 +912,23 @@ the server configuration files

    +
      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
  Syntax OK
-
    +

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

    -

    See also

    KeepAlive Directive

    Description: - Enables HTTP persistent connections
    Syntax: - KeepAlive on|off
    Default: - KeepAlive On
    Context: - server config, virtual host
    Status: - Core
    Module: - core
    +

    See also

    top

    KeepAlive Directive

    Description: + Enables HTTP persistent connections
    Syntax: + KeepAlive on|off
    Default: + KeepAlive On
    Context: + server config, virtual host
    Status: + Core
    Module: + core

    The Keep-Alive extension to HTTP/1.0 and the persistent connection feature of HTTP/1.1 provide long-lived HTTP sessions which allow multiple requests to be sent over the same TCP @@ -946,32 +948,32 @@ the server configuration filesMaxKeepAliveRequests

    KeepAliveTimeout Directive

    Description: - Amount of time the server will wait for subsequent -requests on a persistent connection
    Syntax: - KeepAliveTimeout seconds
    Default: - KeepAliveTimeout 15
    Context: - server config, virtual host
    Status: - Core
    Module: - core
    +

    See also

    top

    KeepAliveTimeout Directive

    Description: + Amount of time the server will wait for subsequent +requests on a persistent connection
    Syntax: + KeepAliveTimeout seconds
    Default: + KeepAliveTimeout 15
    Context: + server config, virtual host
    Status: + Core
    Module: + core

    The number of seconds Apache will wait for a subsequent request before closing the connection. Once a request has been received, the timeout value specified by the - Timeout directive applies.

    + Timeout directive applies.

    Setting KeepAliveTimeout to a high value may cause performance problems in heavily loaded servers. The higher the timeout, the more server processes will be kept occupied waiting on connections with idle clients.

    -

    <Limit> Directive

    Description: - Restrict enclosed access controls to only certain HTTP -methods
    Syntax: - <Limit method [method] ... > ... - </Limit>
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    +
    top

    <Limit> Directive

    Description: + Restrict enclosed access controls to only certain HTTP +methods
    Syntax: + <Limit method [method] ... > ... + </Limit>
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    Access controls are normally effective for all access methods, and this is the usual desired behavior. In the general case, access control @@ -986,50 +988,50 @@ methods -

    - <Limit POST PUT DELETE>
    -   Require valid-user
    +

    + <Limit POST PUT DELETE>
    +   Require valid-user
    </Limit>     -

    +

    The method names listed can be one or more of: GET, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, PATCH, PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, LOCK, and UNLOCK. The method name is case-sensitive. If GET is used it will also restrict HEAD requests.

    -

    <LimitExcept> Directive

    Description: - Restrict access controls to all HTTP methods -except the named ones
    Syntax: - <LimitExcept method [method] ... > ... - </LimitExcept>
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    +
    top

    <LimitExcept> Directive

    Description: + Restrict access controls to all HTTP methods +except the named ones
    Syntax: + <LimitExcept method [method] ... > ... + </LimitExcept>
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    <LimitExcept> and </LimitExcept> are used to enclose a group of access control directives which will then apply to any HTTP access method not listed in the arguments; - i.e., it is the opposite of a <Limit> section and can be used to control + i.e., it is the opposite of a <Limit> section and can be used to control both standard and nonstandard/unrecognized methods. See the - documentation for <Limit> for more details.

    + documentation for <Limit> for more details.

    For example:

    -
    - <LimitExcept POST GET>
    - Require valid-user
    +

    + <LimitExcept POST GET>
    + Require valid-user
    <LimitExcept> -

    - -

    LimitRequestBody Directive

    Description: - Restricts the total size of the HTTP request body sent -from the client
    Syntax: - LimitRequestBody bytes
    Default: - LimitRequestBody 0
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    +

    + +
    top

    LimitRequestBody Directive

    Description: + Restricts the total size of the HTTP request body sent +from the client
    Syntax: + LimitRequestBody bytes
    Default: + LimitRequestBody 0
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    This directive specifies the number of bytes from 0 (meaning unlimited) to 2147483647 (2GB) that are allowed in a request body. The default value is defined by the compile-time @@ -1058,18 +1060,18 @@ from the client +

    LimitRequestBody 102400 - - -

    LimitRequestFields Directive

    Description: - Limits the number of HTTP request header fields that -will be accepted from the client
    Syntax: - LimitRequestFields number
    Default: - LimitRequestFields 100
    Context: - server config
    Status: - Core
    Module: - core
    +

    + +
    top

    LimitRequestFields Directive

    Description: + Limits the number of HTTP request header fields that +will be accepted from the client
    Syntax: + LimitRequestFields number
    Default: + LimitRequestFields 100
    Context: + server config
    Status: + Core
    Module: + core

    Number is an integer from 0 (meaning unlimited) to 32767. The default value is defined by the compile-time constant DEFAULT_LIMIT_REQUEST_FIELDS (100 as @@ -1095,18 +1097,18 @@ will be accepted from the client +

    LimitRequestFields 50 - - -

    LimitRequestFieldSize Directive

    Description: - Limits the size of the HTTP request header allowed from the -client
    Syntax: - LimitRequestFieldsize bytes
    Default: - LimitRequestFieldsize 8190
    Context: - server config
    Status: - Core
    Module: - core
    +

    + +
    top

    LimitRequestFieldSize Directive

    Description: + Limits the size of the HTTP request header allowed from the +client
    Syntax: + LimitRequestFieldsize bytes
    Default: + LimitRequestFieldsize 8190
    Context: + server config
    Status: + Core
    Module: + core

    This directive specifies the number of bytes from 0 to the value of the compile-time constant DEFAULT_LIMIT_REQUEST_FIELDSIZE (8190 as @@ -1129,21 +1131,21 @@ clientFor example:

    -
    +

    LimitRequestFieldSize 16380 -

    - -
    Under normal conditions, the value should not be changed from - the default.
    - -

    LimitRequestLine Directive

    Description: - Limit the size of the HTTP request line that will be accepted -from the client
    Syntax: - LimitRequestLine bytes
    Default: - LimitRequestLine 8190
    Context: - server config
    Status: - Core
    Module: - core
    +

    + +
    Under normal conditions, the value should not be changed from + the default.
    + +
    top

    LimitRequestLine Directive

    Description: + Limit the size of the HTTP request line that will be accepted +from the client
    Syntax: + LimitRequestLine bytes
    Default: + LimitRequestLine 8190
    Context: + server config
    Status: + Core
    Module: + core

    This directive sets the number of bytes from 0 to the value of the compile-time constant DEFAULT_LIMIT_REQUEST_LINE (8190 as distributed) @@ -1166,44 +1168,44 @@ from the client +

    LimitRequestLine 16380 - - -

    Under normal conditions, the value should not be changed from - the default.
    -

    LimitXMLRequestBody Directive

    Description: - Limits the size of an XML-based request body
    Syntax: - LimitXMLRequestBody number
    Default: - LimitXMLRequestBody 1000000
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    +

    + +
    Under normal conditions, the value should not be changed from + the default.
    +
    top

    LimitXMLRequestBody Directive

    Description: + Limits the size of an XML-based request body
    Syntax: + LimitXMLRequestBody number
    Default: + LimitXMLRequestBody 1000000
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    Limit (in bytes) on maximum size of an XML-based request body. A value of 0 will disable any checking.

    Example:

    -
    +

    LimitXMLRequestBody 0 -

    - -

    <Location> Directive

    Description: - Applies the enclosed directives only to matching -URLs
    Syntax: - <Location - URL-path|URL> ... </Location>
    Context: - server config, virtual host
    Status: - Core
    Module: - core
    +

    + +
    top

    <Location> Directive

    Description: + Applies the enclosed directives only to matching +URLs
    Syntax: + <Location + URL-path|URL> ... </Location>
    Context: + server config, virtual host
    Status: + Core
    Module: + core

    The <Location> directive provides for access control by URL. It is similar to the - <Directory> + <Directory> directive, and starts a subsection which is terminated with a </Location> directive. <Location> sections are processed in the - order they appear in the configuration file, after the <Directory> sections and - .htaccess files are read, and after the <Files> sections.

    + order they appear in the configuration file, after the <Directory> sections and + .htaccess files are read, and after the <Files> sections.

    Note that URLs do not have to line up with the filesystem at all, it should be emphasized that <Location> operates @@ -1223,36 +1225,36 @@ URLsExtended regular expressions can also be used, with the addition of the ~ character. For example:

    -
    +

    <Location ~ "/(extra|special)/data"> -

    +

    would match URLs that contained the substring "/extra/data" or "/special/data". In Apache 1.3 and above, a new directive - <LocationMatch> + <LocationMatch> exists which behaves identical to the regex version of <Location>.

    The <Location> functionality is especially useful when combined with the - SetHandler + SetHandler directive. For example, to enable status requests, but allow them only from browsers at foo.com, you might use:

    -
    - <Location /status>
    - SetHandler server-status
    - Order Deny,Allow
    - Deny from all
    - Allow from .foo.com
    +

    + <Location /status>
    + SetHandler server-status
    + Order Deny,Allow
    + Deny from all
    + Allow from .foo.com
    </Location> -

    +

    -

    Note about / (slash)

    The slash character has +

    Note about / (slash)

    The slash character has special meaning depending on where in a URL it appears. People may be used to its behavior 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 +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 @@ -1262,45 +1264,45 @@ used for proxy requests. But when (non-regex) <Locati 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.

    -
    -

    See also

    top

    <LocationMatch> Directive

    Description: + Applies the enclosed directives only to regular-expression +matching URLs
    Syntax: + <LocationMatch + regex> ... </Location>
    Context: + server config, virtual host
    Status: + Core
    Module: + core

    The <LocationMatch> directive provides for access control by URL, in an identical manner to - <Location>. However, it takes a regular + <Location>. However, it takes a regular expression as an argument instead of a simple string. For example:

    -
    +

    <LocationMatch "/(extra|special)/data"> -

    +

    would match URLs that contained the substring "/extra/data" or "/special/data".

    -

    See also

    top

    LogLevel Directive

    Description: + Controls the verbosity of the ErrorLog
    Syntax: + LogLevel level
    Default: + LogLevel warn
    Context: + server config, virtual host
    Status: + Core
    Module: + core

    LogLevel adjusts the verbosity of the - messages recorded in the error logs (see ErrorLog directive). The following + messages recorded in the error logs (see ErrorLog directive). The following levels are available, in order of decreasing significance:

    - +
    @@ -1388,40 +1390,40 @@ matching URLs
    Level
    LogLevel notice
    +

    LogLevel notice

    -

    MaxKeepAliveRequests Directive

    Description: - Number of requests allowed on a persistent -connection
    Syntax: - MaxKeepAliveRequests number
    Default: - MaxKeepAliveRequests 100
    Context: - server config, virtual host
    Status: - Core
    Module: - core
    +
    top

    MaxKeepAliveRequests Directive

    Description: + Number of requests allowed on a persistent +connection
    Syntax: + MaxKeepAliveRequests number
    Default: + MaxKeepAliveRequests 100
    Context: + server config, virtual host
    Status: + Core
    Module: + core

    The MaxKeepAliveRequests directive limits the number of requests allowed per connection when - KeepAlive is on. If it is + KeepAlive is on. If it is set to "0", unlimited requests will be allowed. We recommend that this setting be kept to a high value for maximum server performance.

    For example:

    -
    MaxKeepAliveRequests 500
    -

    NameVirtualHost Directive

    Description: - Designates an IP address for name-virtual -hosting
    Syntax: - NameVirtualHost addr[:port]
    Context: - server config
    Status: - Core
    Module: - core
    +

    MaxKeepAliveRequests 500

    +
    top

    NameVirtualHost Directive

    Description: + Designates an IP address for name-virtual +hosting
    Syntax: + NameVirtualHost addr[:port]
    Context: + server config
    Status: + Core
    Module: + core

    The NameVirtualHost directive is a required directive if you want to configure name-based virtual hosts.

    Although addr can be hostname it is recommended that you always use an IP address, e.g.

    -
    NameVirtualHost 111.22.33.44
    +

    NameVirtualHost 111.22.33.44

    With the NameVirtualHost directive you specify the IP address on which the server will receive requests @@ -1442,41 +1444,41 @@ hostingOptionally you can specify a port number on which the name-based virtual hosts should be used, e.g.

    -
    NameVirtualHost 111.22.33.44:8080
    +

    NameVirtualHost 111.22.33.44:8080

    IPv6 addresses must be enclosed in square brackets, as shown in the following example:

    -
    NameVirtualHost [fe80::a00:20ff:fea7:ccea]:8080
    +

    NameVirtualHost [fe80::a00:20ff:fea7:ccea]:8080

    To receive requests on all interfaces, you can use an argument of *

    -
    NameVirtualHost *
    +

    NameVirtualHost *

    -

    Argument to <VirtualHost> directive

    +

    Argument to <VirtualHost> directive

    Note that the argument to the <VirtualHost> directive must exactly match the argument to the NameVirtualHost directive.

    -
    -NameVirtualHost 1.2.3.4
    -<VirtualHost 1.2.3.4>
    -...
    -</VirtualHost>
    -
    -
    - -

    See also

    Options Directive

    Description: - Configures what features are available in a particular -directory
    Syntax: - Options - [+|-]option [[+|-]option] ...
    Default: - Options All
    Context: - server config, virtual host, directory, .htaccess
    Override: - Options
    Status: - Core
    Module: - core
    +

    +NameVirtualHost 1.2.3.4
    +<VirtualHost 1.2.3.4>
    +...
    +</VirtualHost>
    +

    +
    + +

    See also

    top

    Options Directive

    Description: + Configures what features are available in a particular +directory
    Syntax: + Options + [+|-]option [[+|-]option] ...
    Default: + Options All
    Context: + server config, virtual host, directory, .htaccess
    Override: + Options
    Status: + Core
    Module: + core

    The Options directive controls which server features are available in a particular directory.

    @@ -1499,12 +1501,12 @@ directory - The server will follow symbolic links in this directory.
    + The server will follow symbolic links in this directory.
    Note: even though the server follows the symlink it does not change the pathname used to match - against     <Directory> sections.
    + against <Directory> sections.
    Note: this option gets ignored if set inside a - <Location> + <Location> section.
    Includes
    @@ -1539,8 +1541,8 @@ directory The server will only follow symbolic links for which the target - file or directory is owned by the same user id as the link.
    Note: this option gets ignored if set inside - a     <Location> + file or directory is owned by the same user id as the link.
    Note: this option gets ignored if set inside + a <Location> section.

    Normally, if multiple Options could apply to a @@ -1555,25 +1557,25 @@ directoryFor example, without any + and - symbols:

    -
    <Directory /web/docs>
    - Options Indexes FollowSymLinks
    - </Directory>
    - <Directory /web/docs/spec>
    - Options Includes
    +

    <Directory /web/docs>
    + Options Indexes FollowSymLinks
    + </Directory>
    + <Directory /web/docs/spec>
    + Options Includes
    </Directory> -

    +

    then only Includes will be set for the /web/docs/spec directory. However if the second Options directive uses the + and - symbols:

    -
    - <Directory /web/docs>
    - Options Indexes FollowSymLinks
    - </Directory>
    - <Directory /web/docs/spec>
    - Options +Includes -Indexes
    +

    + <Directory /web/docs>
    + Options Indexes FollowSymLinks
    + </Directory>
    + <Directory /web/docs/spec>
    + Options +Includes -Indexes
    </Directory> -

    +

    then the options FollowSymLinks and Includes are set for the /web/docs/spec directory.

    @@ -1584,14 +1586,14 @@ directory    The default in the absence of any other settings is All.

    -

    Require Directive

    Description: - Selects which authenticated users can access -a resource
    Syntax: - Require entity-name [entity-name] ...
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Core
    Module: - core
    +
    top

    Require Directive

    Description: + Selects which authenticated users can access +a resource
    Syntax: + Require entity-name [entity-name] ...
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Core
    Module: + core

    This directive selects which authenticated users can access a directory. The allowed syntaxes are:

    @@ -1618,35 +1620,35 @@ a resource

    Require must be accompanied by - AuthName and AuthType directives, and directives such - as AuthUserFile - and AuthGroupFile (to + AuthName and AuthType directives, and directives such + as AuthUserFile + and AuthGroupFile (to define users and groups) in order to work correctly. Example:

    -
    - AuthType Basic
    - AuthName "Restricted Directory"
    - AuthUserFile /web/users
    - AuthGroupFile /web/groups
    - Require group admin
    -
    +

    + AuthType Basic
    + AuthName "Restricted Directory"
    + AuthUserFile /web/users
    + AuthGroupFile /web/groups
    + Require group admin
    +

    Access controls which are applied in this way are effective for all methods. This is what is normally desired. If you wish to apply access controls only to specific methods, while leaving other methods unprotected, then place the Require statement into a - <Limit> + <Limit> section.

    -

    See also

    RLimitCPU Directive

    Description: - Limits the CPU consumption of processes launched -by Apache children
    Syntax: - RLimitCPU number|max [number|max]
    Default: - Unset; uses operating system defaults
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    +

    See also

    top

    RLimitCPU Directive

    Description: + Limits the CPU consumption of processes launched +by Apache children
    Syntax: + RLimitCPU number|max [number|max]
    Default: + Unset; uses operating system defaults
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    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, @@ -1664,15 +1666,15 @@ by Apache childrenRLimitMEM

  • RLimitNPROC

    • RLimitMEM Directive

    Description: - Limits the memory consumption of processes launched -by Apache children
    Syntax: - RLimitMEM number|max [number|max]
    Default: - Unset; uses operating system defaults
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    +

    See also

    top

    RLimitMEM Directive

    Description: + Limits the memory consumption of processes launched +by Apache children
    Syntax: + RLimitMEM number|max [number|max]
    Default: + Unset; uses operating system defaults
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    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, @@ -1690,15 +1692,15 @@ by Apache childrenRLimitCPU

  • RLimitNPROC

    • RLimitNPROC Directive

    Description: - Limits the number of processes that can be launched by -processes launched by Apache children
    Syntax: - RLimitNPROC number|max [number|max]
    Default: - Unset; uses operating system defaults
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Core
    Module: - core
    +

    See also

    top

    RLimitNPROC Directive

    Description: + Limits the number of processes that can be launched by +processes launched by Apache children
    Syntax: + RLimitNPROC number|max [number|max]
    Default: + Unset; uses operating system defaults
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    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, @@ -1722,16 +1724,16 @@ processes launched by Apache childrenRLimitMEM

  • RLimitCPU

    • Satisfy Directive

    Description: - Interaction between host-level access control and -user authentication
    Syntax: - Satisfy any|all
    Default: - Satisfy all
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Core
    Module: - core
    -

    Access policy if both Allow and Require used. The parameter can be +

    See also

    top

    Satisfy Directive

    Description: + Interaction between host-level access control and +user authentication
    Syntax: + Satisfy any|all
    Default: + Satisfy all
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Core
    Module: + core
    +

    Access policy if both Allow and Require used. The parameter can be either 'all' or 'any'. This directive is only useful if access to a particular area is being restricted by both username/password and client host address. In this case @@ -1748,71 +1750,71 @@ user authentication - Require valid-user
    - Allow from 192.168.1
    +

    + Require valid-user
    + Allow from 192.168.1
    Satisfy any -     +

    -

    See also

    ScriptInterpreterSource Directive

    Description: - Technique for locating the interpreter for CGI -scripts
    Syntax: - ScriptInterpreterSource registry|script
    Default: - ScriptInterpreterSource script
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Core
    Module: - core
    Compatibility: - Win32 only
    +

    See also

    top

    ScriptInterpreterSource Directive

    Description: + Technique for locating the interpreter for CGI +scripts
    Syntax: + ScriptInterpreterSource registry|script
    Default: + ScriptInterpreterSource script
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Core
    Module: + core
    Compatibility: + Win32 only

    This directive is used to control how Apache finds the interpreter used to run CGI scripts. The default technique is to use the interpreter pointed to by the #! line in the script. Setting ScriptInterpreterSource registry will cause the Windows Registry to be searched using the script file extension (e.g., .pl) as a search key.

    -

    ServerAdmin Directive

    Description: - Email address that the server includes in error -messages sent to the client
    Syntax: - ServerAdmin email-address
    Context: - server config, virtual host
    Status: - Core
    Module: - core
    +
    top

    ServerAdmin Directive

    Description: + Email address that the server includes in error +messages sent to the client
    Syntax: + ServerAdmin email-address
    Context: + server config, virtual host
    Status: + Core
    Module: + core

    The ServerAdmin sets the e-mail address that the server includes in any error messages it returns to the client.

    It may be worth setting up a dedicated address for this, e.g.

    -
    ServerAdmin www-admin@foo.bar.com
    +

    ServerAdmin www-admin@foo.bar.com

    as users do not always mention that they are talking about the server!

    -

    ServerAlias Directive

    Description: - Alternate names for a host used when matching requests -to name-virtual hosts
    Syntax: - ServerAlias hostname [hostname] ...
    Context: - virtual host
    Status: - Core
    Module: - core
    +
    top

    ServerAlias Directive

    Description: + Alternate names for a host used when matching requests +to name-virtual hosts
    Syntax: + ServerAlias hostname [hostname] ...
    Context: + virtual host
    Status: + Core
    Module: + core

    The ServerAlias directive sets the alternate names for a host, for use with name-based virtual hosts.

    -
    - <VirtualHost *>
    - ServerName server.domain.com
    - ServerAlias server server2.domain.com server2
    - ...
    +

    + <VirtualHost *>
    + ServerName server.domain.com
    + ServerAlias server server2.domain.com server2
    + ...
    </VirtualHost> -

    -

    See also

    ServerName Directive

    Description: - Hostname and port that the server uses to identify -itself
    Syntax: - ServerName fully-qualified-domain-name[:port]
    Context: - server config, virtual host
    Status: - Core
    Module: - core
    Compatibility: - In version 2.0, this +

    +

    See also

    top

    ServerName Directive

    Description: + Hostname and port that the server uses to identify +itself
    Syntax: + ServerName fully-qualified-domain-name[:port]
    Context: + server config, virtual host
    Status: + Core
    Module: + core
    Compatibility: + In version 2.0, this directive supersedes the functionality of the Port - directive from version 1.3.
    + directive from version 1.3.

    The ServerName directive sets the hostname and port that the server uses to identify itself. This is used when creating redirection URLs. For example, if the name of the @@ -1821,7 +1823,7 @@ itself -

    ServerName www.example.com:80
    +

    ServerName www.example.com:80

    If no ServerName is specified, then the server attempts to deduce the hostname by performing a reverse @@ -1833,75 +1835,75 @@ itselfIf you are using name-based virtual hosts, the ServerName inside a - <VirtualHost> + <VirtualHost> section specifies what hostname must appear in the request's Host: header to match this virtual host.

    See the description of the - UseCanonicalName directive for + UseCanonicalName directive for settings which determine whether self-referential URL's (e.g., by the - mod_dir module) will refer to the + mod_dir module) will refer to the specified port, or to the port number given in the client's request.

    -

    See also

    ServerPath Directive

    Description: - Legacy URL pathname for a name-virtual host that -is accessed by an incompatible browser
    Syntax: - ServerPath URL-path
    Context: - virtual host
    Status: - Core
    Module: - core
    +

    See also

    top

    ServerPath Directive

    Description: + Legacy URL pathname for a name-virtual host that +is accessed by an incompatible browser
    Syntax: + ServerPath URL-path
    Context: + virtual host
    Status: + Core
    Module: + core

    The ServerPath directive sets the legacy URL pathname for a host, for use with name-based virtual hosts.

    -

    See also

    ServerRoot Directive

    Description: - Base directory for the server installation
    Syntax: - ServerRoot directory-path
    Default: - ServerRoot /usr/local/apache
    Context: - server config
    Status: - Core
    Module: - core
    +

    See also

    top

    ServerRoot Directive

    Description: + Base directory for the server installation
    Syntax: + ServerRoot directory-path
    Default: + ServerRoot /usr/local/apache
    Context: + server config
    Status: + Core
    Module: + core

    The ServerRoot directive sets the directory in which the server lives. Typically it will contain the subdirectories conf/ and logs/. Relative paths for other configuration files are taken as relative to this directory.

    -

    Example

    +

    Example

    ServerRoot /home/httpd -

    +

    -

    See also

    top

    ServerSignature Directive

    Description: + Configures the footer on server-generated documents
    Syntax: + ServerSignature On|Off|EMail
    Default: + ServerSignature Off
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Core
    Module: + core

    The ServerSignature directive allows the configuration of a trailing footer line under server-generated documents (error messages, mod_proxy ftp directory listings, mod_info output, ...). The reason why you would want to enable such a footer line is that in a chain of proxies, the user often has no possibility to tell which of the chained servers actually - produced a returned error message.
    The Off + produced a returned error message.
    The Off setting, which is the default, suppresses the error line (and is therefore compatible with the behavior of Apache-1.2 and below). The On setting simply adds a line with the - server version number and ServerName of the serving virtual host, + server version number and ServerName of the serving virtual host, and the EMail setting additionally creates a - "mailto:" reference to the ServerAdmin of the referenced + "mailto:" reference to the ServerAdmin of the referenced document.

    -

    See also

    ServerTokens Directive

    Description: - Configures the Server HTTP response header
    Syntax: - ServerTokens Major|Minor|Minimal|ProductOnly|OS|Full
    Default: - ServerTokens Full
    Context: - server config
    Status: - Core
    Module: - core
    +

    See also

    top

    ServerTokens Directive

    Description: + Configures the Server HTTP response header
    Syntax: + ServerTokens Major|Minor|Minimal|ProductOnly|OS|Full
    Default: + ServerTokens Full
    Context: + server config
    Status: + Core
    Module: + core

    This directive controls whether Server response header field which is sent back to clients includes a description of the generic OS-type of the server as well as @@ -1941,91 +1943,91 @@ is accessed by an incompatible browserThis setting applies to the entire server, and cannot be enabled or disabled on a virtualhost-by-virtualhost basis.

    -

    See also

    SetHandler Directive

    Description: - Forces all matching files to be processed by a -handler
    Syntax: - SetHandler handler-name
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Core
    Module: - core
    Compatibility: - Moved into the core in Apache 2.0
    +

    See also

    top

    SetHandler Directive

    Description: + Forces all matching files to be processed by a +handler
    Syntax: + SetHandler handler-name
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Core
    Module: + core
    Compatibility: + Moved into the core in Apache 2.0

    When placed into an .htaccess file or a - <Directory> or - <Location> + <Directory> or + <Location> section, this directive forces all matching files to be parsed through the handler given by handler-name. For example, if you had a directory you wanted to be parsed entirely as imagemap rule files, regardless of extension, you might put the following into an .htaccess file in that directory:

    -
    +

    SetHandler imap-file -

    +

    Another example: if you wanted to have the server display a status report whenever a URL of http://servername/status was called, you might put the following into httpd.conf:

    -
    - <Location /status>
    - SetHandler server-status
    +

    + <Location /status>
    + SetHandler server-status
    </Location> -

    - -

    See also

    SetInputFilter Directive

    Description: - Sets the filters that will process client requests and POST -input
    Syntax: - SetInputFilter filter[;filter...]
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Core
    Module: - core
    +

    + +

    See also

    top

    SetInputFilter Directive

    Description: + Sets the filters that will process client requests and POST +input
    Syntax: + SetInputFilter filter[;filter...]
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Core
    Module: + core

    The SetInputFilter directive sets the filter or filters which will process client requests and POST input when they are received by the server. This is in addition to any filters defined elsewhere, including the - AddInputFilter + AddInputFilter directive.

    If more than one filter is specified, they must be separated by semicolons in the order in which they should process the content.

    -

    See also

    SetOutputFilter Directive

    Description: - Sets the filters that will process responses from the -server
    Syntax: - SetOutputFilter filter[;filter...]
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Core
    Module: - core
    +

    See also

    top

    SetOutputFilter Directive

    Description: + Sets the filters that will process responses from the +server
    Syntax: + SetOutputFilter filter[;filter...]
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Core
    Module: + core

    The SetOutputFilter directive sets the filters which will process responses from the server before they are sent to the client. This is in addition to any filters defined elsewhere, including the - AddOutputFilter + AddOutputFilter directive.

    For example, the following configuration will process all files in the /www/data/ directory for server-side includes.

    -
    -<Directory /www/data/>
    -  SetOutputFilter INCLUDES
    +

    +<Directory /www/data/>
    +  SetOutputFilter INCLUDES
    </Directory> -

    +

    If more than one filter is specified, they must be separated by semicolons in the order in which they should process the content.

    -

    See also

    TimeOut Directive

    Description: - Amount of time the server will wait for -certain events before failing a request
    Syntax: - TimeOut number
    Default: - TimeOut 300
    Context: - server config
    Status: - Core
    Module: - core
    +

    See also

    top

    TimeOut Directive

    Description: + Amount of time the server will wait for +certain events before failing a request
    Syntax: + TimeOut number
    Default: + TimeOut 300
    Context: + server config
    Status: + Core
    Module: + core

    The TimeOut directive currently defines the amount of time Apache will wait for three things:

    @@ -2046,18 +2048,18 @@ certain events before failing a request -

    UseCanonicalName Directive

    Description: - Configures how the server determines its own name and -port
    Syntax: - UseCanonicalName on|off|dns
    Default: - UseCanonicalName on
    Context: - server config, virtual host, directory
    Status: - Core
    Module: - core
    +
    top

    UseCanonicalName Directive

    Description: + Configures how the server determines its own name and +port
    Syntax: + UseCanonicalName on|off|dns
    Default: + UseCanonicalName on
    Context: + server config, virtual host, directory
    Status: + Core
    Module: + core

    In many situations Apache must construct a self-referential URL -- that is, a URL that refers back to the same server. With UseCanonicalName on Apache will - use the hostname and port specified in the ServerName directive to construct the canonical + use the hostname and port specified in the ServerName directive to construct the canonical name for the server. This name is used in all self-referential URLs, and for the values of SERVER_NAME and SERVER_PORT in CGIs.

    @@ -2098,15 +2100,15 @@ portSERVER_NAME to construct self-referential URLs then it should be just fine.

    -

    See also

    <VirtualHost> Directive

    Description: - Contains directives that apply only to a specific -hostname or IP address
    Syntax: - <VirtualHost +

    See also

    top

    <VirtualHost> Directive

    Description: + Contains directives that apply only to a specific +hostname or IP address
    Syntax: + <VirtualHost addr[:port] [addr[:port]] - ...> ... </VirtualHost>
    Context: - server config
    Status: - Core
    Module: - core
    + ...> ... </VirtualHost>
    Context: + server config
    Status: + Core
    Module: + core

    <VirtualHost> and </VirtualHost> are used to enclose a group of directives that will apply only to a particular virtual host. Any @@ -2130,30 +2132,30 @@ hostname or IP address

    Example

    - <VirtualHost 10.1.2.3>
    - ServerAdmin webmaster@host.foo.com
    - DocumentRoot /www/docs/host.foo.com
    - ServerName host.foo.com
    - ErrorLog logs/host.foo.com-error_log
    - TransferLog logs/host.foo.com-access_log
    +

    Example

    + <VirtualHost 10.1.2.3>
    + ServerAdmin webmaster@host.foo.com
    + DocumentRoot /www/docs/host.foo.com
    + ServerName host.foo.com
    + ErrorLog logs/host.foo.com-error_log
    + TransferLog logs/host.foo.com-access_log
    </VirtualHost> -     +

    IPv6 addresses must be specified in square brackets because the optional port number could not be determined otherwise. An IPv6 example is shown below:

    -
    -<VirtualHost [fe80::a00:20ff:fea7:ccea]>
    - ServerAdmin webmaster@host.foo.com
    - DocumentRoot /www/docs/host.foo.com
    - ServerName host.foo.com
    - ErrorLog logs/host.foo.com-error_log
    - TransferLog logs/host.foo.com-access_log
    +

    +<VirtualHost [fe80::a00:20ff:fea7:ccea]>
    + ServerAdmin webmaster@host.foo.com
    + DocumentRoot /www/docs/host.foo.com
    + ServerName host.foo.com
    + ErrorLog logs/host.foo.com-error_log
    + TransferLog logs/host.foo.com-access_log
    </VirtualHost> -

    +

    Each Virtual Host must correspond to a different IP address, different port number or a different host name for the server, @@ -2170,13 +2172,13 @@ hostname or IP addressNameVirtualHost directive will use neither + address that matches a NameVirtualHost directive will use neither the "main" server config nor the _default_ virtual host. See the name-based virtual hosting documentation for further details.)

    You can specify a :port to change the port that is matched. If unspecified then it defaults to the same port as the - most recent Listen + most recent Listen statement of the main server. You may also specify :* to match all ports on that address. (This is recommended when used with _default_.)

    @@ -2188,10 +2190,10 @@ hostname or IP address<VirtualHost> does not affect what addresses Apache listens on. You may need to ensure - that Apache is listening on the correct addresses using Listen.

    -

    See also

    \ No newline at end of file diff --git a/docs/manual/mod/directives.html.en b/docs/manual/mod/directives.html.en index f90060f138..66d58ba720 100644 --- a/docs/manual/mod/directives.html.en +++ b/docs/manual/mod/directives.html.en @@ -1,12 +1,14 @@ -Directive Index - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Directive Index

    + -->Directive Index - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Directive Index

    Each Apache directive available in the standard Apache distribution is listed here. They are described using a consistent format, and there is a dictionary of the terms used in their descriptions available.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

     A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  X 

    \ No newline at end of file diff --git a/docs/manual/mod/directives.html.ja.jis b/docs/manual/mod/directives.html.ja.jis index 3b5bfc6424..aeea72deb4 100644 --- a/docs/manual/mod/directives.html.ja.jis +++ b/docs/manual/mod/directives.html.ja.jis @@ -1,11 +1,13 @@ -$B%G%#%l%/%F%#%V0lMw(B - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    $B%G%#%l%/%F%#%V0lMw(B

    + -->$B%G%#%l%/%F%#%V0lMw(B - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    $B%G%#%l%/%F%#%V0lMw(B

    - $BI8=`(B Apache $BG[I[$K$"$k$9$Y$F$N(B Apache $B$N%G%#%l%/%F%#%V$N0l(B$BMw$G$9!#(B - $B$3$l$i$O0l4S$7$?7A<0$G=q$+$l$F$$$F!";H$o$l(B$B$F$$$kMQ8l$N(B + $BI8=`(B Apache $BG[I[$K$"$k$9$Y$F$N(B Apache $B$N%G%#%l%/%F%#%V$N0lMw$G$9!#(B + $B$3$l$i$O0l4S$7$?7A<0$G=q$+$l$F$$$F!";H$o$l$F$$$kMQ8l$N(B $BMQ8l=8(B $B$bMQ0U$5$l$F$$$^$9!#(B

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file +
    \ No newline at end of file diff --git a/docs/manual/mod/directives.xml b/docs/manual/mod/directives.xml index 4392aef0b8..6bd3823885 100644 --- a/docs/manual/mod/directives.xml +++ b/docs/manual/mod/directives.xml @@ -15,5 +15,18 @@ descriptions available.

    + + + A B C + D E F + G H I + J K L + M N O + P Q R + S T U + V W X + Y Z + + &allmodules; \ No newline at end of file diff --git a/docs/manual/mod/index.html.en b/docs/manual/mod/index.html.en index bb9c678d49..264fb7fd99 100644 --- a/docs/manual/mod/index.html.en +++ b/docs/manual/mod/index.html.en @@ -1,22 +1,24 @@ -Module Index - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Module Index

    + -->Module Index - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Module Index

    Below is a list of all of the modules that come as part of the Apache distribution. See also the complete alphabetical list of all Apache directives.

    -

    Core Features and Multi-Processing Modules

    core
    Core Apache HTTP Server features that are always +
    top

    Core Features and Multi-Processing Modules

    core
    Core Apache HTTP Server features that are always available
    mpm_common
    A collection of directives that are implemented by more than one multi-processing module (MPM)
    mpm_netware
    Multi-Processing Module implementing an exclusively threaded web server optimized for Novell NetWare
    mpm_winnt
    This Multi-Processing Module is optimized for Windows NT.
    perchild
    Multi-Processing Module allowing for daemon processes serving requests to be assigned a variety of different userids
    prefork
    Implements a non-threaded, pre-forking web server
    worker
    Multi-Processing Module implementing a hybrid - multi-threaded multi-process web server

    Other Modules

    mod_access
    Provides access control based on client hostname, IP + multi-threaded multi-process web server
    top

    Other Modules

    mod_access
    Provides access control based on client hostname, IP address, or other characteristics of the client request.
    mod_actions
    This module provides for executing CGI scripts based on media type or request method.
    mod_alias
    Provides for mapping different parts of the host filesystem in the document tree and for URL redirection
    mod_asis
    Sends files that contain their own @@ -55,4 +57,4 @@ and Group
    mod_unique_id
    Provide identifier for each request
    mod_userdir
    User-specific directories
    mod_usertrack
    Clickstream logging of user activity on a site
    mod_vhost_alias
    Provides for dynamically configured mass virtual -hosting

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +hosting \ No newline at end of file diff --git a/docs/manual/mod/index.html.ja.jis b/docs/manual/mod/index.html.ja.jis index 3c93845e55..b525ce5ba2 100644 --- a/docs/manual/mod/index.html.ja.jis +++ b/docs/manual/mod/index.html.ja.jis @@ -1,23 +1,25 @@ -$B%b%8%e!<%k0lMw(B - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    $B%b%8%e!<%k0lMw(B

    + -->$B%b%8%e!<%k0lMw(B - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    $B%b%8%e!<%k0lMw(B

    $B0J2<$O(B Apache $B$NG[I[$N0lIt$H$7$FG[$i$l$F$$$k$9$Y$F$N%b%8%e!<%k$N(B $B0lMw$G$9!#$9$Y$F$N(B Apache - $B%G%#%l%/%F(B$B%#%V(B $B$N%"%k%U%!%Y%C%H=g$N%j%9%H$b8+$F$/$@$5$$!#(B + $B%G%#%l%/%F%#%V(B $B$N%"%k%U%!%Y%C%H=g$N%j%9%H$b8+$F$/$@$5$$!#(B

    -

    $B%3%"5!G=$H(B MPM

    core
    Core Apache HTTP Server features that are always -available
    mpm_common
    $BFs$D0J>e$N%^%k%A%W%m%;%C%7%s%0%b%8%e(B$B!<%k(B (MPM) +
    top

    $B%3%"5!G=$H(B MPM

    core
    Core Apache HTTP Server features that are always +available
    mpm_common
    $BFs$D0J>e$N%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM) $B$G
    mpm_netware
    Multi-Processing Module implementing an exclusively threaded web server optimized for Novell NetWare
    mpm_winnt
    Windows NT -$B8~$1$K:GE,2=$5$l$?(B$B%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B
    perchild
    Multi-Processing Module allowing for daemon processes +$B8~$1$K:GE,2=$5$l$?%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B
    perchild
    Multi-Processing Module allowing for daemon processes serving requests to be assigned a variety of different - userids
    prefork
    $B%9%l%C%I$r;H$o$:!"@h9T$7$F(B fork $B$r9T$J(B$B$&%&%'%V%5!<%P$r
    prefork
    $B%9%l%C%I$r;H$o$:!"@h9T$7$F(B fork $B$r9T$J$&%&%'%V%5!<%P$r
    worker
    $B%^%k%A%9%l%C%I$H%^%k%A%W%m%;%9$N%O%$%V%j%C%I7?(B -$B%&%'%V%5!<%P$r

    $BB>$N%b%8%e!<%k(B

    mod_access
    $B%/%i%$%"%s%H$N%[%9%HL>!"(BIP $B%"(B$B%I%l%9!"$=$NB>$N%/%i%$%"%s%H(B -$B$N%j%/%(%9%H$NFCD'$K4p$E$$$?%"%/%;(B$B%9@)8f5!G=$rDs6!$9$k(B
    mod_actions
    This module provides for executing CGI scripts based on +$B%&%'%V%5!<%P$r
    top

    $BB>$N%b%8%e!<%k(B

    mod_access
    $B%/%i%$%"%s%H$N%[%9%HL>!"(BIP $B%"%I%l%9!"$=$NB>$N%/%i%$%"%s%H(B +$B$N%j%/%(%9%H$NFCD'$K4p$E$$$?%"%/%;%9@)8f5!G=$rDs6!$9$k(B
    mod_actions
    This module provides for executing CGI scripts based on media type or request method.
    mod_alias
    Provides for mapping different parts of the host filesystem in the document tree and for URL redirection
    mod_asis
    Sends files that contain their own HTTP headers
    mod_auth
    $B%F%-%9%H%U%!%$%k$rMQ$$$?%f!<%6G'>Z(B
    mod_auth_anon
    Allows "anonymous" user access to authenticated @@ -25,10 +27,10 @@ HTTP headers
    mod_auth
    $B%F%-%9%H%U% files
    mod_auth_digest
    User authentication using MD5 Digest Authentication.
    mod_autoindex
    Unix $B$N(B ls $B%3%^%s%I$d(B Win32 $B$N(B dir $B%7%'%k%3%^%s%I$K;w$?(B - $B%G(B$B%#%l%/%H%j%$%s%G%C%/%9$r@8@.$9$k(B
    mod_cache
    Content cache keyed to URIs.
    mod_cern_meta
    CERN httpd metafile semantics
    mod_cgi
    Execution of CGI scripts
    mod_cgid
    Execution of CGI scripts using an + $B%G%#%l%/%H%j%$%s%G%C%/%9$r@8@.$9$k(B
    mod_cache
    Content cache keyed to URIs.
    mod_cern_meta
    CERN httpd metafile semantics
    mod_cgi
    Execution of CGI scripts
    mod_cgid
    Execution of CGI scripts using an external CGI daemon
    mod_charset_lite
    Specify character set translation or recoding
    mod_dav
    $BJ,;6%*!<%5%j%s%0$H%P!<%8%g%s4IM}(B (WebDAV) $B5!G=(B
    mod_deflate
    Compress content before - it is delivered to the client
    mod_dir
    $B!V:G8e$N%9%i%C%7%e!W$N%j%@%$%l%/%H$H!"%G%#(B$B%l%/%H%j$N(B + it is delivered to the client
    mod_dir
    $B!V:G8e$N%9%i%C%7%e!W$N%j%@%$%l%/%H$H!"%G%#%l%/%H%j$N(B $B%$%s%G%C%/%9%U%!%$%k$r07$&5!G=$rDs6!$9$k(B
    mod_echo
    A simple echo server to illustrate protocol modules
    mod_env
    CGI $B%9%/%j%W%H5Z$S(B SSI $B%Z!<%8$KEO$5$l$k4D6-JQ?t$rJQ99$9$k5!G=$rDs6!$9$k(B
    mod_example
    Illustrates the Apache module API
    mod_expires
    Generation of @@ -43,7 +45,7 @@ configuration
    mod_isapi
    ISAPI Exten encoding)
    mod_mime_magic
    Determines the MIME type of a file by looking at a few bytes of its contents
    mod_negotiation
    Provides for content negotiation
    mod_proxy
    HTTP/1.1 proxy/gateway server
    mod_rewrite
    Provides a rule-based rewriting engine to rewrite requested URLs on the fly
    mod_setenvif
    Allows the setting of environment variables based -on characteristics of the request
    mod_so
    $B5/F0;~$d:F5/F0;~$K
    mod_so
    $B5/F0;~$d:F5/F0;~$K
    mod_speling
    Attempts to correct mistaken URLs that users might have entered by ignoring capitalization and by allowing up to one misspelling
    mod_ssl
    Strong cryptography using the Secure Sockets @@ -53,4 +55,4 @@ identifier for each request
    mod_userdir
    mod_usertrack
    Clickstream logging of user activity on a site
    mod_vhost_alias
    Provides for dynamically configured mass virtual -hosting

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file +hosting \ No newline at end of file diff --git a/docs/manual/mod/mod_access.html.en b/docs/manual/mod/mod_access.html.en index ec47c7a5ab..b6c4be635e 100644 --- a/docs/manual/mod/mod_access.html.en +++ b/docs/manual/mod/mod_access.html.en @@ -1,26 +1,28 @@ -mod_access - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_access

    Description: - Provides access control based on client hostname, IP -address, or other characteristics of the client request.
    Status: - Base
    Module Identifier: - access_module

    Summary

    -

    The directives provided by mod_access are used in <Directory>, <Files>, and <Location> sections as well as + -->mod_access - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_access

    Description: + Provides access control based on client hostname, IP +address, or other characteristics of the client request.
    Status: + Base
    Module Identifier: + access_module

    Summary

    +

    The directives provided by mod_access are used in <Directory>, <Files>, and <Location> sections as well as .htaccess files to control access to particular parts of the server. Access can be controlled based on the client hostname, IP address, or - other characteristics of the client request, as captured in environment variables. The Allow and Deny directives are used to + other characteristics of the client request, as captured in environment variables. The Allow and Deny directives are used to specify which clients are or are not allowed access to the server, - while the Order + while the Order directive sets the default access state, and configures how the - Allow and Deny directives interact with each + Allow and Deny directives interact with each other.

    Both host-based access restrictions and password-based authentication may be implemented simultaneously. In that case, - the Satisfy directive is used + the Satisfy directive is used to determine how the two sets of restrictions interact.

    In general, access restriction directives apply to all @@ -28,17 +30,17 @@ address, or other characteristics of the client request.POST, etc). This is the desired behavior in most cases. However, it is possible to restrict some methods, while leaving other methods unrestricted, by enclosing the directives - in a <Limit> section.

    -

    Directives

    See also

    Allow Directive

    Description: - Controls which hosts can access an area of the -server
    Syntax: - Allow from + in a <Limit> section.

    +

    Directives

    See also

    top

    Allow Directive

    Description: + Controls which hosts can access an area of the +server
    Syntax: + Allow from all|host|env=env-variable - [host|env=env-variable] ...
    Context: - directory, .htaccess
    Override: - Limit
    Status: - Base
    Module: - mod_access
    + [host|env=env-variable] ...
    Context: + directory, .htaccess
    Override: + Limit
    Status: + Base
    Module: + mod_access

    The Allow directive affects which hosts can access an area of the server. Access can be controlled by @@ -50,7 +52,7 @@ serverfrom. The subsequent arguments can take three different forms. If Allow from all is specified, then all hosts are allowed access, subject to the configuration of the - Deny and Order directives as discussed + Deny and Order directives as discussed below. To allow only particular hosts or groups of hosts to access the server, the host can be specified in any of the following formats:

    @@ -58,36 +60,36 @@ server
    A (partial) domain-name
    -
    Example: Allow from apache.org
    +
    Example: Allow from apache.org
    Hosts whose names match, or end in, this string are allowed access. Only complete components are matched, so the above example will match foo.apache.org but it will not match fooapache.org. This configuration will cause the server to perform a reverse DNS lookup on the - client IP address, regardless of the setting of the     HostnameLookups + client IP address, regardless of the setting of the HostnameLookups directive.
    A full IP address
    -
    Example: Allow from 10.1.2.3
    +
    Example: Allow from 10.1.2.3
    An IP address of a host allowed access
    A partial IP address
    -
    Example: Allow from 10.1
    +
    Example: Allow from 10.1
    The first 1 to 3 bytes of an IP address, for subnet restriction.
    A network/netmask pair
    Example: Allow from - 10.1.0.0/255.255.0.0
    + 10.1.0.0/255.255.0.0
    A network a.b.c.d, and a netmask w.x.y.z. For more fine-grained subnet restriction.
    A network/nnn CIDR specification
    -
    Example: Allow from 10.1.0.0/16
    +
    Example: Allow from 10.1.0.0/16
    Similar to the previous case, except the netmask consists of nnn high-order 1 bits.
    @@ -98,10 +100,10 @@ serverIPv6 addresses and IPv6 subnets can be specified as shown below:

    -
    - Allow from fe80::a00:20ff:fea7:ccea
    +

    + Allow from fe80::a00:20ff:fea7:ccea
    Allow from fe80::a00:20ff:fea7:ccea/10 -

    +

    The third format of the arguments to the Allow directive allows access to the server @@ -111,91 +113,91 @@ servermod_setenvif. Therefore, this directive can be + mod_setenvif. Therefore, this directive can be used to allow access based on such factors as the clients User-Agent (browser type), Referer, or other HTTP request header fields.

    -

    Example:

    +

    Example:

    -SetEnvIf User-Agent ^KnockKnock/2.0 let_me_in
    -<Directory /docroot>
    -   Order Deny,Allow
    -   Deny from all
    -   Allow from env=let_me_in
    +SetEnvIf User-Agent ^KnockKnock/2.0 let_me_in
    +<Directory /docroot>
    +   Order Deny,Allow
    +   Deny from all
    +   Allow from env=let_me_in
    </Directory> -

    +

    In this case, browsers with a user-agent string beginning with KnockKnock/2.0 will be allowed access, and all others will be denied.

    -

    Deny Directive

    Description: - Controls which hosts are denied access to the -server
    Syntax: - Deny from +
    top

    Deny Directive

    Description: + Controls which hosts are denied access to the +server
    Syntax: + Deny from all|host|env=env-variable - [host|env=env-variable] ...
    Context: - directory, .htaccess
    Override: - Limit
    Status: - Base
    Module: - mod_access
    + [host|env=env-variable] ...
    Context: + directory, .htaccess
    Override: + Limit
    Status: + Base
    Module: + mod_access

    This directive allows access to the server to be restricted based on hostname, IP address, or environment variables. The arguments for the Deny directive are - identical to the arguments for the Allow directive.

    -

    Order Directive

    Description: - Controls the default access state and the order in which + identical to the arguments for the Allow directive.

    +
    top

    Order Directive

    Description: + Controls the default access state and the order in which Allow and Deny are -evaluated.
    Syntax: - Order ordering
    Default: - Order Deny,Allow
    Context: - directory, .htaccess
    Override: - Limit
    Status: - Base
    Module: - mod_access
    +evaluated.
    Syntax: + Order ordering
    Default: + Order Deny,Allow
    Context: + directory, .htaccess
    Override: + Limit
    Status: + Base
    Module: + mod_access

    The Order directive controls the default - access state and the order in which Allow and Deny directives are evaluated. + access state and the order in which Allow and Deny directives are evaluated. Ordering is one of

    Deny,Allow
    -
    The Deny directives - are evaluated before the Allow directives. Access is +
    The Deny directives + are evaluated before the Allow directives. Access is allowed by default. Any client which does not match a - Deny directive or does - match an Allow + Deny directive or does + match an Allow directive will be allowed access to the server.
    Allow,Deny
    -
    The Allow - directives are evaluated before the Deny directives. Access is denied - by default. Any client which does not match an Allow directive or does match a - Deny directive will be +
    The Allow + directives are evaluated before the Deny directives. Access is denied + by default. Any client which does not match an Allow directive or does match a + Deny directive will be denied access to the server.
    Mutual-failure
    -
    Only those hosts which appear on the Allow list and do not appear on - the Deny list are +
    Only those hosts which appear on the Allow list and do not appear on + the Deny list are granted access. This ordering has the same effect as Order Allow,Deny and is deprecated in favor of that configuration.

    Keywords may only be separated by a comma; no whitespace is - allowed between them. Note that in all cases every Allow and Deny statement is evaluated.

    + allowed between them. Note that in all cases every Allow and Deny statement is evaluated.

    In the following example, all hosts in the apache.org domain are allowed access; all other hosts are denied access.

    -
    - Order Deny,Allow
    - Deny from all
    - Allow from apache.org
    -
    +

    + Order Deny,Allow
    + Deny from all
    + Allow from apache.org
    +

    In the next example, all hosts in the apache.org domain are allowed access, except for the hosts which are in the @@ -203,11 +205,11 @@ evaluated. -

    - Order Allow,Deny
    - Allow from apache.org
    - Deny from foo.apache.org
    -
    +

    + Order Allow,Deny
    + Allow from apache.org
    + Deny from foo.apache.org
    +

    On the other hand, if the Order in the last example is changed to Deny,Allow, all hosts will @@ -221,14 +223,14 @@ evaluated.The presence of an Order directive can affect access to a part of the server even in the absence of accompanying - Allow and Deny directives because of its effect + Allow and Deny directives because of its effect on the default access state. For example,

    -
    - <Directory /www>
    -   Order Allow,Deny
    +

    + <Directory /www>
    +   Order Allow,Deny
    </Directory> -

    +

    will deny all access to the /www directory because the default access state will be set to @@ -237,12 +239,12 @@ evaluated.The Order directive controls the order of access directive processing only within each phase of the server's configuration processing. This implies, for example, that an - Allow or Deny directive occurring in a - <Location> section will - always be evaluated after an Allow or Deny directive occurring in a - <Directory> section or + Allow or Deny directive occurring in a + <Location> section will + always be evaluated after an Allow or Deny directive occurring in a + <Directory> section or .htaccess file, regardless of the setting of the Order directive. For details on the merging of configuration sections, see the documentation on How Directory, Location and Files sections work.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_access.html.ja.jis b/docs/manual/mod/mod_access.html.ja.jis index 7bbae83cff..7b44acdf8a 100644 --- a/docs/manual/mod/mod_access.html.ja.jis +++ b/docs/manual/mod/mod_access.html.ja.jis @@ -1,60 +1,62 @@ -mod_access - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mod_access

    $B@bL@(B: - $B%/%i%$%"%s%H$N%[%9%HL>!"(BIP $B%"(B$B%I%l%9!"$=$NB>$N%/%i%$%"%s%H(B -$B$N%j%/%(%9%H$NFCD'$K4p$E$$$?%"%/%;(B$B%9@)8f5!G=$rDs6!$9$k(B
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<(B$B%k<1JL;R(B: - access_module

    $B35MW(B

    -

    mod_access $B$K$h$j(B$BDs6!$5$l$k%G%#%l%/%F%#%V$O%5!<%P$NFCDj$NItJ,$X$N(B - $B%"%/%;%9$r@)8f$9$k$?$a$K(B <Directory>, <Files>, <Location> + -->mod_access - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mod_access

    $B@bL@(B: + $B%/%i%$%"%s%H$N%[%9%HL>!"(BIP $B%"%I%l%9!"$=$NB>$N%/%i%$%"%s%H(B +$B$N%j%/%(%9%H$NFCD'$K4p$E$$$?%"%/%;%9@)8f5!G=$rDs6!$9$k(B
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k<1JL;R(B: + access_module

    $B35MW(B

    +

    mod_access $B$K$h$jDs6!$5$l$k%G%#%l%/%F%#%V$O%5!<%P$NFCDj$NItJ,$X$N(B + $B%"%/%;%9$r@)8f$9$k$?$a$K(B <Directory>, <Files>, <Location> $B$H(B .htaccess $B%U%!%$%k$G;HMQ$5$l$^$9!#%/%i%$%"%s%H$N%[%9%HL>!"(BIP - $B%"%I%l%9$d(B $B4D6-JQ?t(B$B$H$7(B$B$F$N%j%/%(%9%H$NFCD'$K4p$E$$$F(B - $B%"%/%;%9@)8f$r9T$J$&$3$H$,$G$-$^$9!#(BAllow $B$H(B - Deny $B%G%#%l%/%F%#%V$O(B + $B%"%I%l%9$d(B $B4D6-JQ?t(B$B$H$7$F$N%j%/%(%9%H$NFCD'$K4p$E$$$F(B + $B%"%/%;%9@)8f$r9T$J$&$3$H$,$G$-$^$9!#(BAllow $B$H(B + Deny $B%G%#%l%/%F%#%V$O(B $B$I$N$h$&$J%/%i%$%"%s%H$K%"%/%;%9$r(B $B5v2D$9$k!"$7$J$$$+$r;XDj$9$k$?$a$K;HMQ$5$l$^$9!#0lJ}!"(B - Order $B%G%#%l%/%F%#%V$O(B + Order $B%G%#%l%/%F%#%V$O(B $B%G%U%)%k%H$N%"%/%;%9>uBV$H!"(B - Allow $B%G%#%l%/%F%#%V$H(B - Deny + Allow $B%G%#%l%/%F%#%V$H(B + Deny $B%G%#%l%/%F%#%V$H$N$*8_$$$X$N1F6A$N;EJ}$r@_Dj$7$^$9!#(B

    -

    $B%[%9%H$K$h$k%"%/%;%9@)8B$H%Q%9%o!<%I$K$h$kG'(B$B>Z$rF1;~$K(B +

    $B%[%9%H$K$h$k%"%/%;%9@)8B$H%Q%9%o!<%I$K$h$kG'>Z$rF1;~$K(B $B9T$J$&$3$H$,2DG=$G$9!#$=$N>l9g!"$=$NFs$D$N@)8B$N4X78$r;XDj$9$k$?$a$K(B - Satisfy + Satisfy $B%G%#%l%/%F%#%V$r;HMQ$7$^$9!#(B

    $B0lHLE*$K$O!"%"%/%;%9@)8B%G%#%l%/%F%#%V$O$9$Y$F$N%"%/%;%9%a%=%C%I(B (GET, PUT, POST $B$J$I(B) $B$KE,MQ$5$l$^$9!#$=$7$F!"$[$H$s$I$N>l9g$3$l$,K>$^$7$$F0:n$G$9!#(B - $B$7$+$7!"(B<Limit> + $B$7$+$7!"(B<Limit> $B%;%/%7%g%s$NCf$K%G%#%l%/%F%#%V$r=q$/$3$H$G!"(B $B0lIt$N%a%=%C%I$K$N$_@)8B$r$+$1$k$3$H$b$G$-$^$9!#(B

    -

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    Allow $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%5!<%P$N$"$kNN0h$K%"%/%;%9$G$-$k%[%9%H$r@)8f$9$k(B
    $B9=J8(B: - Allow from +

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    top

    Allow $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%5!<%P$N$"$kNN0h$K%"%/%;%9$G$-$k%[%9%H$r@)8f$9$k(B
    $B9=J8(B: + Allow from all|host|env=env-variable - [host|env=env-variable] ...
    $B%3%s%F%-%9%H(B: - $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Limit
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_access
    + [host|env=env-variable] ...
    $B%3%s%F%-%9%H(B: + $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Limit
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_access

    Allow $B%G%#%l%/%F%#%V$O$I$N%[%9%H$,(B $B%5!<%P$N$"$kNN0h$r%"%/%;%9$G$-$k$+$K1F6A$rM?$($^$9!#(B $B%"%/%;%9$O%[%9%HL>!"(BIP $B%"%I%l%9!"(BIP $B%"%I%l%9$NHO0O$d!"(B - $B4D6-JQ?t$H$7$F$N%/%i%$%"%s(B$B%H$N%j%/%(%9%H$N(B + $B4D6-JQ?t$H$7$F$N%/%i%$%"%s%H$N%j%/%(%9%H$N(B $BFCD'$K$h$C$F@)8f$9$k$3$H$,$G$-$^$9!#(B

    $B$3$N%G%#%l%/%F%#%V$N:G=i$N0z?t$O>o$K(B from $B$G$9!#(B $B$=$l$KB3$/0z?t$O;0$D$N0c$C$?7A<0$,$"$j$^$9!#(BAllow from all $B$,;XDj$5$l$F$$$l$P!"$9$Y$F$N%[%9%H$K%"%/%;%9$r5v2D$7!"(B $B%"%/%;%9@)8B$O2<$G@bL@$5$l$F$$$k$h$&$K!"(B - Deny - $B%G%#%l%/%F%#%V$H(B Order + Deny + $B%G%#%l%/%F%#%V$H(B Order $B%G%#%l%/%F%#%V$N@_Dj$G7h$^$j$^$9!#(B $BFCDj$N%[%9%H$d%[%9%H72$K$N$_%5!<%P$X$N%"%/%;%9$r5v2D$9$k$?$a$K$O!"(B $B0J2<$N$I$l$+$N7A<0$G(B host $B$r;XDj$9$k$3$H$,$G$-$^$9(B:

    @@ -62,49 +64,49 @@
    $B%I%a%$%sL>(B ($B$N0lIt(B)
    -
    $BNc(B: Allow from apache.org
    +
    $BNc(B: Allow from apache.org
    $B$3$NJ8;zNs$K9g$&$+!"$3$l$G=*$o$kL>A0$N%[%9%H$N%"%/%;%9$,5v2D$5$l$^$9!#(B $B3FItJ,$,40A4$K9g$&$b$N$@$1$KE,MQ$5$l$^$9$N$G!">e$NNc$O(B foo.apache.org $B$K$O%^%C%A$7$^$9$,!"(B fooapache.org $B$K$O%^%C%A$7$^$;$s!#(B $B$3$N@_Dj$r$9$k$H!"%5!<%P$O(B - HostnameLookups + HostnameLookups $B$N@_Dj$K4X$o$i$:!"%/%i%$%"%s%H$N(B IP $B%"%I%l%9$KBP$7$F(B DNS $B$N5U0z$-$r9T$J$$$^$9!#(B
    $B40A4$J(B IP $B%"%I%l%9(B
    -
    $BNc(B: Allow from 10.1.2.3
    +
    $BNc(B: Allow from 10.1.2.3
    $B%"%/%;%9$r5v2D$9$k(B IP $B%"%I%l%9$G$9!#(B
    IP $B%"%I%l%9$N0lIt(B
    -
    $BNc(B: Allow from 10.1
    +
    $BNc(B: Allow from 10.1
    $B%5%V%M%C%H$N@)8BMQ$N!"(BIP $B%"%I%l%9$N:G=i$N0l$D$+$i;0$D$^$G$N%P%$%H$G$9!#(B
    $B%M%C%H%o!<%/(B/$B%M%C%H%^%9%/(B $B$NBP(B
    -
    $BNc(B: Allow from 10.1.0.0/255.255.0.0
    +
    $BNc(B: Allow from 10.1.0.0/255.255.0.0
    $B%M%C%H%o!<%/(B a.b.c.d $B$H%M%C%H%^%9%/(B w.x.y.z $B$G$9!#(B $B$h$j:YN3EY$N%5%V%M%C%H@)8BMQ$G$9!#(B
    $B%M%C%H%o!<%/(B/nnn CIDR $B;XDj(B
    -
    $BNc(B: Allow from 10.1.0.0/16
    +
    $BNc(B: Allow from 10.1.0.0/16
    $B%M%C%H%^%9%/$,(B nnn $B$N>e0L%S%C%H$,(B 1 $B$H$J$C$F$$$k$b$N$+$i$J$k$3$H0J30$OA0$N$b$N$HF1$8$G$9!#(B
    -

    $BCm(B: $B:G8e$N;0$D$NNc$O$^(B$B$C$?$/F1$8%[%9%H$K9g$$$^$9!#(B

    +

    $BCm(B: $B:G8e$N;0$D$NNc$O$^$C$?$/F1$8%[%9%H$K9g$$$^$9!#(B

    IPv6 $B%"%I%l%9$H(B IPv6 $B$N%5%V%M%C%H$O0J2<$N$h$&$K;XDj$G$-$^$9(B:

    -
    - Allow from fe80::a00:20ff:fea7:ccea
    +

    + Allow from fe80::a00:20ff:fea7:ccea
    Allow from fe80::a00:20ff:fea7:ccea/10 -

    +

    Allow $B%G%#%l%/%F%#%V$N0z?t$N;0$DL\$N7A<0$O!"(B $B4D6-JQ?t(B @@ -112,7 +114,7 @@ Allow from env=variablename $B$,;XDj$5$l$F$$$k$H!"4D6-JQ?t(B variablename $B$,B8:_$7$?>l9g$K%j%/%(%9%H$O%"%/%;%9$r5v2D$5$l$^$9!#%5!<%P$O(B - mod_setenvif + mod_setenvif $B$N%G%#%l%/%F%#%V$K$h$j!"%/%i%$%"%s%H$N%j%/%(%9%H(B $B$NFCD'$K4p$E$$$F=@Fp$K4D6-JQ?t$r@_Dj$9$k5!G=$rDs6!$7$^$9!#(B $B$G$9$+$i!"$3$N%G%#%l%/%F%#%V$O%/%i%$%"%s%H$N(B @@ -121,81 +123,81 @@ $B%"%/%;%95v2D$r$9$k$?$a$K;H$&$3$H$,$G$-$^$9!#(B

    -

    $BNc(B:

    +

    $BNc(B:

    -SetEnvIf User-Agent ^KnockKnock/2.0 let_me_in
    -<Directory /docroot>
    -   Order Deny,Allow
    -   Deny from all
    -   Allow from env=let_me_in
    +SetEnvIf User-Agent ^KnockKnock/2.0 let_me_in
    +<Directory /docroot>
    +?? Order Deny,Allow
    +?? Deny from all
    +?? Allow from env=let_me_in
    </Directory> -

    +

    $B$3$N>l9g!"(Buser-agent $B$NJ8;zNs$,(B KnockKnock/2.0 $B$G;O$^$k%V%i%&%6$N$_$,%"%/%;%9$r5v2D$5$l!"(B $BB>$N$b$N$O%"%/%;%9$r5qH]$5$l$^$9!#(B

    -

    Deny $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%5!<%P$,%"%/%;%9$r5qH]$9$k%[%9%H$r@)8f$9$k(B
    $B9=J8(B: - Deny from +
    top

    Deny $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%5!<%P$,%"%/%;%9$r5qH]$9$k%[%9%H$r@)8f$9$k(B
    $B9=J8(B: + Deny from all|host|env=env-variable - [host|env=env-variable] ...
    $B%3%s%F%-%9%H(B: - $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Limit
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_access
    + [host|env=env-variable] ...
    $B%3%s%F%-%9%H(B: + $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Limit
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_access

    $B$3$N%G%#%l%/%F%#%V$O%[%9%HL>!"(BIP $B%"%I%l%9!"4D6-JQ?t$K4p$E$$$F%5!<%P$X$N%"%/%;%9$r@)8B$7$^$9!#(B - Deny $B%G%#%l%/%F%#%V$N0z?t$O(B Allow + Deny $B%G%#%l%/%F%#%V$N0z?t$O(B Allow $B%G%#%l%/%F%#%V$H$^$C$?$/F1$8$G$9!#(B

    -

    Order $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%G%U%)%k%H$N%"%/%;%92DG=$J>uBV$H!"(BAllow $B$H(B -Deny $B$,I>2A$5$l$k=gHV$r@)8f$9$k(B
    $B9=J8(B: - Order ordering
    $B%G%U%)%k%H(B: - Order Deny,Allow
    $B%3%s%F%-%9%H(B: - $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Limit
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_access
    +
    top

    Order $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%G%U%)%k%H$N%"%/%;%92DG=$J>uBV$H!"(BAllow $B$H(B +Deny $B$,I>2A$5$l$k=gHV$r@)8f$9$k(B
    $B9=J8(B: + Order ordering
    $B%G%U%)%k%H(B: + Order Deny,Allow
    $B%3%s%F%-%9%H(B: + $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Limit
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_access

    Order $B%G%#%l%/%F%#%V$O%G%U%)%k%H$N%"%/%;%9$N>uBV$H(B - Allow $B%G%#%l%/%F%#%V$H(B - Deny + Allow $B%G%#%l%/%F%#%V$H(B + Deny $B%G%#%l%/%F%#%V$,I>2A$5$l$k=gHV$r@)8f$7$^$9!#(B Ordering $B$O0J2<$N$I$l$+$G$9!#(B

    Deny,Allow
    -
    Deny $B%G%#%l%/%F%#%V$,(B - Allow +
    Deny $B%G%#%l%/%F%#%V$,(B + Allow $B%G%#%l%/%F%#%V$NA0$KI>2A$5$l$^$9!#(B - $B%"%/%;%9$O%G%U%)%k%H$G5v2D$5$l$^$9!#(BDeny - $B%G%#%l%/%F%#%V$K9g$o$J$$$+!"(BAllow + $B%"%/%;%9$O%G%U%)%k%H$G5v2D$5$l$^$9!#(BDeny + $B%G%#%l%/%F%#%V$K9g$o$J$$$+!"(BAllow $B%G%#%l%/%F%#%V$K9g$&%/%i%$%"%s%H$O%"%/%;%9$r5v2D$5$l$^$9!#(B
    Allow,Deny
    -
    Allow - $B%G%#%l%/%F%#%V$,(B Deny +
    Allow + $B%G%#%l%/%F%#%V$,(B Deny $B%G%#%l%/%F%#%V$NA0$KI>2A$5$l$^$9!#(B - $B%"%/%;%9$O%G%U%)%k%H$G5qH]$5$l$^$9!#(BAllow - $B%G%#%l%/%F%#%V$K9g$o$J$$$+!"(BDeny + $B%"%/%;%9$O%G%U%)%k%H$G5qH]$5$l$^$9!#(BAllow + $B%G%#%l%/%F%#%V$K9g$o$J$$$+!"(BDeny $B%G%#%l%/%F%#%V$K9g$&%/%i%$%"%s%H$O%"%/%;%9$r5qH]$5$l$^$9!#(B
    Mutual-failure
    -
    Allow $B$N%j%9%H$K8=$l$F!"(B - Deny +
    Allow $B$N%j%9%H$K8=$l$F!"(B + Deny $B$N%j%9%H$K8=$l$J$$%[%9%H$N$_$,%"%/%;%9$r5v2D$5$l$^$9!#(B $B$3$N=gHVIU$1$O(B Order Allow,Deny $B$HF1$88z2L$r;}$A!"(B $B$=$N@_Dj$NJ}$,9%$^$7$$$?$a$KHs?d>)$H$J$C$F$$$^$9!#(B

    $B%-!<%o!<%I$O%3%s%^$GJ,N%$9$k$3$H$@$1$,2DG=$G$9!#(B - $B4V$K6uGr$,$"$C$F$O$$$1$^$;$s!#$I$N>l9g$G$b!"(BAllow $B$H(B - Deny $BJ8$O(B + $B4V$K6uGr$,$"$C$F$O$$$1$^$;$s!#$I$N>l9g$G$b!"(BAllow $B$H(B + Deny $BJ8$O(B $BA4$FI>2A$5$l$k$H$$$&$3$H$KCm0U$7$F$/$@$5$$!#(B

    @@ -203,11 +205,11 @@ Deny $B$,I>2A$5$l$k=gHV$r@)8f$9$k(B$N$9$Y$F$N%[%9%H$O%"%/%;%9$r5qH]$5$l$^$9!#(B

    -
    - Order Deny,Allow
    - Deny from all
    - Allow from apache.org
    -
    +

    + Order Deny,Allow
    + Deny from all
    + Allow from apache.org
    +

    $B2A$5$l$k=gHV$r@)8f$9$k(BuBV$,%"%/%;%95qH]$N$?$a!"(B $B%5!<%P$X$N%"%/%;%9$r5qH]$5$l$^$9!#(B

    -
    - Order Allow,Deny
    - Allow from apache.org
    - Deny from foo.apache.org
    -
    +

    + Order Allow,Deny
    + Allow from apache.org
    + Deny from foo.apache.org
    +

    $B0lJ}!">e$NNc$N(B Order $B$,(B Deny,Allow $B$KJQ$o$C$F$$$l$P!"$9$Y$N%[%9%H$K%"%/%;%9$,5v2D$5$l$^$9!#(B @@ -233,16 +235,16 @@ Deny $B$,I>2A$5$l$k=gHV$r@)8f$9$k(BOrder $B%G%#%l%/%F%#%V$O%G%U%)%k%H$N%"%/%;%9$N>uBV$K1F6A$rM?$($k$N$G!"(B - Allow $B%G%#%l%/%F%#%V$H(B - Deny + Allow $B%G%#%l%/%F%#%V$H(B + Deny $B%G%#%l%/%F%#%V$,L5$/$F$b!"%5!<%P$N%"%/%;%9$K1F6A$rM?$($k$3$H$,$G$-$^$9!#(B $B$?$H$($P!"(B

    -
    - <Directory /www>
    -   Order Allow,Deny
    +

    + <Directory /www>
    + ??Order Allow,Deny
    </Directory> -

    +

    $B$O%G%U%)%k%H$N%"%/%;%9>uBV$,(B deny $B$K$J$k$?$a!"(B /www $B%G%#%l%/%H%j$X$N$9$Y$F$N%"%/%;%9$r5qH]$7$^$9!#(B @@ -252,14 +254,14 @@ Deny $B$,I>2A$5$l$k=gHV$r@)8f$9$k(BOrder $B%G%#%l%/%F%#%V$N@_Dj$K4X$o$i$:!"(B - <Location> $B%;%/%7%g%s$N(B - Allow $B%G%#%l%/%F%#%V$d(B - Deny $B%G%#%l%/%F%#%V$O!"(B - Directory $B%;%/%7%g%s$d(B - .htaccess $B%U%!%$%k$N(B Allow - $B%G%#%l%/%F%#%V$d(B Deny + <Location> $B%;%/%7%g%s$N(B + Allow $B%G%#%l%/%F%#%V$d(B + Deny $B%G%#%l%/%F%#%V$O!"(B + Directory $B%;%/%7%g%s$d(B + .htaccess $B%U%!%$%k$N(B Allow + $B%G%#%l%/%F%#%V$d(B Deny $B%G%#%l%/%F%#%V$h$j$b>o$K8e$KI>2A$5$l$k$H$$$&$3$H$r0UL#$7$^$9!#(B $B@_Dj%;%/%7%g%s$N%^!<%8$N>\:Y$K$D$$$F$O!"(B Directory,Location, Files $B%;%/%7%g%s$NF0:nJ}K!(B $B$r;2>H$7$F$/$@$5$$!#(B

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_actions.html.en b/docs/manual/mod/mod_actions.html.en index dc91be6ccb..ae1dddf689 100644 --- a/docs/manual/mod/mod_actions.html.en +++ b/docs/manual/mod/mod_actions.html.en @@ -1,45 +1,47 @@ -mod_actions - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_actions

    Description: - This module provides for executing CGI scripts based on -media type or request method.
    Status: - Base
    Module Identifier: - actions_module

    Summary

    -

    This module has two directives. The Action directive lets you run CGI + -->mod_actions - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_actions

    Description: + This module provides for executing CGI scripts based on +media type or request method.
    Status: + Base
    Module Identifier: + actions_module

    Summary

    +

    This module has two directives. The Action directive lets you run CGI scripts whenever a file of a certain type is requested. The - Script directive lets + Script directive lets you run CGI scripts whenever a particular method is used in a request. This makes it much easier to execute scripts that process files.

    -

    Directives

    Action Directive

    Description: - Activates a CGI script for a particular handler or -content-type
    Syntax: - Action action-type cgi-script
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_actions
    +

    Directives

    top

    Action Directive

    Description: + Activates a CGI script for a particular handler or +content-type
    Syntax: + Action action-type cgi-script
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_actions

    This directive adds an action, which will activate cgi-script when action-type is triggered by the request. The cgi-script is the URL-path to a resource - that has been designated as a CGI script using ScriptAlias or AddHandler. The + that has been designated as a CGI script using ScriptAlias or AddHandler. The action-type can be either a handler or a MIME content type. It sends the URL and file path of the requested document using the standard CGI PATH_INFO and PATH_TRANSLATED environment variables.

    -

    Examples

    +

    Examples

    - # Requests for files of a particular type:
    - Action image/gif /cgi-bin/images.cgi
    -
    - # Files of a particular file extension
    - AddHandler my-file-type .xyz
    - Action my-file-type /cgi-bin/program.cgi
    -

    + # Requests for files of a particular type:
    + Action image/gif /cgi-bin/images.cgi
    +
    + # Files of a particular file extension
    + AddHandler my-file-type .xyz
    + Action my-file-type /cgi-bin/program.cgi
    +

    In the first example, requests for files with a MIME content type of image/gif will instead be handled by the @@ -48,26 +50,26 @@ content-typeAddHandler

    Script Directive

    Description: - Activates a CGI script for a particular request -method.
    Syntax: - Script method cgi-script
    Context: - server config, virtual host, directory
    Status: - Base
    Module: - mod_actions
    +

    See also

    top

    Script Directive

    Description: + Activates a CGI script for a particular request +method.
    Syntax: + Script method cgi-script
    Context: + server config, virtual host, directory
    Status: + Base
    Module: + mod_actions

    This directive adds an action, which will activate cgi-script when a file is requested using the method of method. The cgi-script is the URL-path to a - resource that has been designated as a CGI script using ScriptAliase or AddHandler. The URL and + resource that has been designated as a CGI script using ScriptAliase or AddHandler. The URL and file path of the requested document is sent using the standard CGI PATH_INFO and PATH_TRANSLATED environment variables.

    -
    +
    Any arbitrary method name may be used. Method names are - case-sensitive, so Script PUT and - Script put have two entirely different + case-sensitive, so Script PUT and + Script put have two entirely different effects. -
    +

    Note that the Script command defines default actions only. If a CGI script is called, or some other resource that is @@ -77,11 +79,11 @@ method.e.g., foo.html?hi). Otherwise, the request will proceed normally.

    -

    Examples

    +

    Examples

    - # For <ISINDEX>-style searching
    - Script GET /cgi-bin/search
    - # A CGI PUT handler
    - Script PUT /~bob/put.cgi
    -

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + # For <ISINDEX>-style searching
    + Script GET /cgi-bin/search
    + # A CGI PUT handler
    + Script PUT /~bob/put.cgi
    +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_alias.html.en b/docs/manual/mod/mod_alias.html.en index 266b02633e..e4bc83fd68 100644 --- a/docs/manual/mod/mod_alias.html.en +++ b/docs/manual/mod/mod_alias.html.en @@ -1,42 +1,44 @@ -mod_alias - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_alias

    Description: - Provides for mapping different parts of the host - filesystem in the document tree and for URL redirection
    Status: - Base
    Module Identifier: - alias_module

    Summary

    + -->mod_alias - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_alias

    Description: + Provides for mapping different parts of the host + filesystem in the document tree and for URL redirection
    Status: + Base
    Module Identifier: + alias_module

    Summary

    The directives contained in this module allow for manipulation and control of URLs as requests arrive at the server. The - Alias and ScriptAlias directives are used to + Alias and ScriptAlias directives are used to map between URLs and filesystem paths. This allows for content - which is not directly under the DocumentRoot served as part of the web - document tree. The ScriptAlias directive has the + which is not directly under the DocumentRoot served as part of the web + document tree. The ScriptAlias directive has the additional effect of marking the target directory as containing only CGI scripts.

    -

    The Redirect +

    The Redirect directives are used to instruct clients to make a new request with a different URL. They are often used when a resource has moved to a new location.

    -

    Directives

    See also

    Alias Directive

    Description: - Maps URLs to filesystem locations
    Syntax: - Alias URL-path - file-path|directory-path
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_alias
    +
    top

    Alias Directive

    Description: + Maps URLs to filesystem locations
    Syntax: + Alias URL-path + file-path|directory-path
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_alias

    The Alias directive allows documents to be stored in the local filesystem other than under the - DocumentRoot. URLs with a + DocumentRoot. URLs with a (%-decoded) path beginning with url-path will be mapped to local files beginning with directory-filename.

    Example:

    -
    Alias /image /ftp/pub/image
    +

    Alias /image /ftp/pub/image

    A request for http://myserver/image/foo.gif would cause the server to return the file /ftp/pub/image/foo.gif.

    @@ -47,40 +49,40 @@ /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 +

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

    -

    AliasMatch Directive

    Description: - Maps URLs to filesystem locations using regular -expressions
    Syntax: - AliasMatch regex - file-path|directory-path
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_alias
    -

    This directive is equivalent to Alias, but makes use of standard +

    top

    AliasMatch Directive

    Description: + Maps URLs to filesystem locations using regular +expressions
    Syntax: + AliasMatch regex + file-path|directory-path
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_alias
    +

    This directive is equivalent to Alias, but makes use of standard regular expressions, instead of simple prefix matching. The supplied regular expression is matched against the URL-path, and if it matches, the server will substitute any parenthesized matches into the given string and use it as a filename. For example, to activate the /icons directory, one might use:

    -
    +

    AliasMatch ^/icons(.*) /usr/local/apache/icons$1 -

    -

    Redirect Directive

    Description: - Sends an external redirect asking the client to fetch -a different URL
    Syntax: - Redirect [status] URL-path URL
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_alias
    +

    +
    top

    Redirect Directive

    Description: + Sends an external redirect asking the client to fetch +a different URL
    Syntax: + Redirect [status] URL-path URL
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_alias

    The Redirect directive maps an old URL into a new one. The new URL is returned to the client which attempts to fetch it again with the new address. URL-path a (%-decoded) @@ -90,18 +92,18 @@ a different URLRedirect /service http://foo2.bar.com/service

    +

    Redirect /service http://foo2.bar.com/service

    If the client requests http://myserver/service/foo.txt, it will be told to access http://foo2.bar.com/service/foo.txt instead.

    -

    Note

    Redirect directives take precedence over +

    Note

    Redirect directives take precedence over Alias and ScriptAlias directives, irrespective of their ordering in the configuration file. Also, URL-path must be an absolute path, not a relative path, even when used with .htaccess files or -inside of <Directory> -sections.

    +inside of     <Directory> +sections.

    If no status argument is given, the redirect will be "temporary" (HTTP status 302). This indicates to the client @@ -140,90 +142,90 @@ sections.

    Example:

    -
    - Redirect permanent /one http://example.com/two
    +

    + Redirect permanent /one http://example.com/two
    Redirect 303 /three http://example.com/other -

    +

    -

    RedirectMatch Directive

    Description: - Sends an external redirect asking the client to fetch +
    top

    RedirectMatch Directive

    Description: + Sends an external redirect asking the client to fetch a different URL based on a regular expression match of the -current URL
    Syntax: - RedirectMatch [status] regex URL
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_alias
    -

    This directive is equivalent to Redirect, but makes use of standard +current URL

    Syntax: + RedirectMatch [status] regex URL
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_alias
    +

    This directive is equivalent to Redirect, but makes use of standard regular expressions, instead of simple prefix matching. The supplied regular expression is matched against the URL-path, and if it matches, the server will substitute any parenthesized matches into the given string and use it as a filename. For example, to redirect all GIF files to like-named JPEG files on another server, one might use:

    -
    +

    RedirectMatch (.*)\.gif$ http://www.anotherserver.com$1.jpg -

    -

    RedirectPermanent Directive

    Description: - Sends an external permanent redirect asking the client to fetch -a different URL
    Syntax: - RedirectPermanent URL-path URL
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_alias
    +

    +
    top

    RedirectPermanent Directive

    Description: + Sends an external permanent redirect asking the client to fetch +a different URL
    Syntax: + RedirectPermanent URL-path URL
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_alias

    This directive makes the client know that the Redirect is permanent (status 301). Exactly equivalent to Redirect permanent.

    -

    RedirectTemp Directive

    Description: - Sends an external temporary redirect asking the client to fetch -a different URL
    Syntax: - RedirectTemp URL-path URL
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_alias
    +
    top

    RedirectTemp Directive

    Description: + Sends an external temporary redirect asking the client to fetch +a different URL
    Syntax: + RedirectTemp URL-path URL
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_alias

    This directive makes the client know that the Redirect is only temporary (status 302). Exactly equivalent to Redirect temp.

    -

    ScriptAlias Directive

    Description: - Maps a URL to a filesystem location and designates the -target as a CGI script
    Syntax: - ScriptAlias -URL-path file-path|directory-path
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_alias
    +
    top

    ScriptAlias Directive

    Description: + Maps a URL to a filesystem location and designates the +target as a CGI script
    Syntax: + ScriptAlias +URL-path file-path|directory-path
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_alias

    The ScriptAlias directive has the same - behavior as the Alias + behavior as the Alias directive, except that in addition it marks the target directory - as containing CGI scripts that will be processed by mod_cgi's cgi-script handler. URLs with a + as containing CGI scripts that will be processed by mod_cgi's cgi-script handler. URLs with a (%-decoded) path beginning with URL-path will be mapped to scripts beginning with the second argument which is a full pathname in the local filesystem.

    Example:

    -
    ScriptAlias /cgi-bin/ /web/cgi-bin/
    +

    ScriptAlias /cgi-bin/ /web/cgi-bin/

    A request for http://myserver/cgi-bin/foo would cause the server to run the script /web/cgi-bin/foo.

    -

    ScriptAliasMatch Directive

    Description: - Maps a URL to a filesystem location using a regular expression -and designates the target as a CGI script
    Syntax: - ScriptAliasMatch -regex file-path|directory-path
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_alias
    -

    This directive is equivalent to ScriptAlias, but makes use of standard +

    top

    ScriptAliasMatch Directive

    Description: + Maps a URL to a filesystem location using a regular expression +and designates the target as a CGI script
    Syntax: + ScriptAliasMatch +regex file-path|directory-path
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_alias
    +

    This directive is equivalent to ScriptAlias, but makes use of standard regular expressions, instead of simple prefix matching. The supplied regular expression is matched against the URL-path, and if it matches, the server will substitute any parenthesized matches into the given string and use it as a filename. For example, to activate the standard /cgi-bin, one might use:

    -
    +

    ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1 -

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_asis.html.en b/docs/manual/mod/mod_asis.html.en index 1d0c538fa2..2109d1d504 100644 --- a/docs/manual/mod/mod_asis.html.en +++ b/docs/manual/mod/mod_asis.html.en @@ -1,12 +1,14 @@ -mod_asis - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_asis

    Description: - Sends files that contain their own -HTTP headers
    Status: - Base
    Module Identifier: - asis_module

    Summary

    + -->mod_asis - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_asis

    Description: + Sends files that contain their own +HTTP headers
    Status: + Base
    Module Identifier: + asis_module

    Summary

    This module provides the handler send-as-is which causes Apache to send the document without adding most of the usual HTTP headers.

    @@ -17,12 +19,12 @@ HTTP headersFor historical reasons, this module will also process any file with the mime type httpd/send-as-is.

    -

    Directives

    This module provides no directives.

    See also

    Usage

    +

    Directives

    This module provides no directives.

    Topics

    • Usage

    See also

    top

    Usage

    In the server configuration file, associate files with the send-as-is handler e.g.

    -
    AddHandler send-as-is asis
    +

    AddHandler send-as-is asis

    The contents of any file with a .asis extension will then be sent by Apache to the client with almost no @@ -36,27 +38,27 @@ HTTP headers -

    Status: 301 Now where did I leave that URL
    - Location: http://xyz.abc.com/foo/bar.html
    - Content-type: text/html
    -
    - <HTML>
    - <HEAD>
    - <TITLE>Lame excuses'R'us</TITLE>
    - </HEAD>
    - <BODY>
    +

    Status: 301 Now where did I leave that URL
    + Location: http://xyz.abc.com/foo/bar.html
    + Content-type: text/html
    +
    + <HTML>
    + <HEAD>
    + <TITLE>Lame excuses'R'us</TITLE>
    + </HEAD>
    + <BODY>
    <H1>Fred's exceptionally wonderful page has moved - to
    + to
    <A HREF="http://xyz.abc.com/foo/bar.html">Joe's</A> - site.
    - </H1>
    - </BODY>
    + site.
    + </H1>
    + </BODY>
    </HTML> -

    +

    Notes: the server always adds a Date: and Server: header to the data returned to the client, so these should not be included in the file. The server does not add a Last-Modified header; it probably should.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_auth.html.en b/docs/manual/mod/mod_auth.html.en index 971407d9c0..da8a34504f 100644 --- a/docs/manual/mod/mod_auth.html.en +++ b/docs/manual/mod/mod_auth.html.en @@ -1,30 +1,32 @@ -mod_auth - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_auth

    Description: - User authentication using text files
    Status: - Base
    Module Identifier: - auth_module

    Summary

    + -->mod_auth - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_auth

    Description: + User authentication using text files
    Status: + Base
    Module Identifier: + auth_module

    Summary

    This module allows the use of HTTP Basic Authentication to restrict access by looking up users in plain text password and group files. Similar functionality and greater scalability is - provided by mod_auth_dbm. HTTP Digest + provided by mod_auth_dbm. HTTP Digest Authentication is provided by - mod_auth_digest.

    - -

    Directives

    See also

    AuthAuthoritative Directive

    Description: - Sets whether authorization and authentication are -passed to lower level modules
    Syntax: - AuthAuthoritative on|off
    Default: - AuthAuthoritative on
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Base
    Module: - mod_auth
    -
    This information has not been updated for Apache 2.0, which - uses a different system for module ordering.
    + mod_auth_digest.

    + +
    top

    AuthAuthoritative Directive

    Description: + Sets whether authorization and authentication are +passed to lower level modules
    Syntax: + AuthAuthoritative on|off
    Default: + AuthAuthoritative on
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Base
    Module: + mod_auth
    +
    This information has not been updated for Apache 2.0, which + uses a different system for module ordering.

    Setting the AuthAuthoritative directive explicitly to 'off' allows for both @@ -37,76 +39,76 @@ passed to lower level modulesRequire + or if a valid Require directive applies to more than one module; then the first module will verify the credentials; and no access is passed on; regardless of the AuthAuthoritative setting.

    A common use for this is in conjunction with one of the - database modules; such as mod_auth_dbm, - mod_auth_msql, and mod_auth_anon. + database modules; such as mod_auth_dbm, + mod_auth_msql, and mod_auth_anon. These modules supply the bulk of the user credential checking; but a few (administrator) related accesses fall through to a lower - level with a well protected AuthUserFile.

    + level with a well protected AuthUserFile.

    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 NCSA compliant behaviour.

    -

    Security

    Do consider the implications of +

    Security

    Do consider the implications of allowing a user to allow fall-through in his .htaccess file; and verify that this is really what you want; Generally it is easier to just secure a single .htpasswd file, than it is to secure a - database such as mSQL. Make sure that the AuthUserFile and the AuthGroupFile are stored outside the + database such as mSQL. Make sure that the AuthUserFile and the AuthGroupFile are stored outside the document tree of the web-server; do not put them in the directory that they protect. Otherwise, clients will be able to - download the AuthUserFile - and the AuthGroupFile. -
    -

    AuthGroupFile Directive

    Description: - Sets the name of a text file containing the list -of user groups for authentication
    Syntax: - AuthGroupFile file-path
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Base
    Module: - mod_auth
    + download the AuthUserFile + and the AuthGroupFile. +
    +
    top

    AuthGroupFile Directive

    Description: + Sets the name of a text file containing the list +of user groups for authentication
    Syntax: + AuthGroupFile file-path
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Base
    Module: + mod_auth

    The AuthGroupFile directive sets the name of a textual file containing the list of user groups for user authentication. File-path is the path to the group file. If it is not absolute (i.e., if it doesn't begin - with a slash), it is treated as relative to the ServerRoot.

    + with a slash), it is treated as relative to the ServerRoot.

    Each line of the group file contains a groupname followed by a colon, followed by the member usernames separated by spaces. Example:

    -
    mygroup: bob joe anne
    +

    mygroup: bob joe anne

    Note that searching large text files is very - inefficient; AuthDBMGroupFile should be used + inefficient; AuthDBMGroupFile should be used instead.

    -

    Security

    +

    Security

    Make sure that the AuthGroupFile is stored outside the document tree of the web-server; do not put it in the directory that it protects. Otherwise, clients will be able to download the AuthGroupFile.

    -
    -

    AuthUserFile Directive

    Description: - Sets the name of a text file containing the list of users and -passwords for authentication
    Syntax: - AuthUserFile file-path
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Base
    Module: - mod_auth
    +
    +
    top

    AuthUserFile Directive

    Description: + Sets the name of a text file containing the list of users and +passwords for authentication
    Syntax: + AuthUserFile file-path
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Base
    Module: + mod_auth

    The AuthUserFile directive sets the name of a textual file containing the list of users and passwords for user authentication. File-path is the path to the user file. If it is not absolute (i.e., if it doesn't begin - with a slash), it is treated as relative to the ServerRoot.

    + with a slash), it is treated as relative to the ServerRoot.

    Each line of the user file contains a username followed by a colon, followed by the crypt() encrypted @@ -121,19 +123,19 @@ passwords for authenticationhtpasswd -c Filename username

    +

    htpasswd -c Filename username

    Add or modify 'username2' in the password file 'Filename':

    -
    htpasswd Filename username2
    +

    htpasswd Filename username2

    Note that searching large text files is very - inefficient; AuthDBMUserFile should be used + inefficient; AuthDBMUserFile should be used instead.

    -

    Security

    +

    Security

    Make sure that the AuthUserFile is stored outside the document tree of the web-server; do not put it in the directory that it protects. Otherwise, clients will be able to download the AuthUserFile.

    -
    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + + \ No newline at end of file diff --git a/docs/manual/mod/mod_auth.html.ja.jis b/docs/manual/mod/mod_auth.html.ja.jis index 3e7b70c949..bcda6207b1 100644 --- a/docs/manual/mod/mod_auth.html.ja.jis +++ b/docs/manual/mod/mod_auth.html.ja.jis @@ -1,31 +1,33 @@ -mod_auth - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mod_auth

    $B@bL@(B: - $B%F%-%9%H%U%!%$%k$rMQ$$$?%f!<%6G'>Z(B
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<(B$B%k<1JL;R(B: - auth_module

    $B35MW(B

    + -->mod_auth - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mod_auth

    $B@bL@(B: + $B%F%-%9%H%U%!%$%k$rMQ$$$?%f!<%6G'>Z(B
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k<1JL;R(B: + auth_module

    $B35MW(B

    -

    $B%W%l%$%s%F%-%9%H$N%Q%9%o!<%I%U%!%$%k$H%0%k!<%W%U%!%$%k$r8!::$7(B$B$F(B - $B%f!<%6$rC5$9$3$H$G!"(BHTTP $B4pK\G'>Z$G%"%/%;%9@)8B(B$B$G$-$k$h$&$K$7$^$9!#(B +

    $B%W%l%$%s%F%-%9%H$N%Q%9%o!<%I%U%!%$%k$H%0%k!<%W%U%!%$%k$r8!::$7$F(B + $B%f!<%6$rC5$9$3$H$G!"(BHTTP $B4pK\G'>Z$G%"%/%;%9@)8B$G$-$k$h$&$K$7$^$9!#(B $B;w$?$h$&$J5!G=$G!"$b$C$HBg$-$J%9%1!<%i%S%j%F%#$r;}$C$?$b$N$O!"(B - mod_auth_dbm $B$GDs6!$5$l$F$$$^$9!#(B - $B$^$?!"(BHTTP $B%@%$%8%'%9%HG'>Z$O(B mod_auth_digest + mod_auth_dbm $B$GDs6!$5$l$F$$$^$9!#(B + $B$^$?!"(BHTTP $B%@%$%8%'%9%HG'>Z$O(B mod_auth_digest $B$GDs6!$5$l$F$$$^$9!#(B

    -

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    AuthAuthoritative $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $BG'>Z$H>5G'%W%m%;%9$r!"(B -$B$h$jDc$$%l%Y%k$N%b%8%e!<%k$K0\9T$5$;$k$+$I$&$+$r@_Dj$9$k(B
    $B9=J8(B: - AuthAuthoritative on|off
    $B%G%U%)%k%H(B: - AuthAuthoritative on
    $B%3%s%F%-%9%H(B: - $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - AuthConfig
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_auth
    +
    top

    AuthAuthoritative $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $BG'>Z$H>5G'%W%m%;%9$r!"(B +$B$h$jDc$$%l%Y%k$N%b%8%e!<%k$K0\9T$5$;$k$+$I$&$+$r@_Dj$9$k(B
    $B9=J8(B: + AuthAuthoritative on|off
    $B%G%U%)%k%H(B: + AuthAuthoritative on
    $B%3%s%F%-%9%H(B: + $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + AuthConfig
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_auth
    -
    $B5-:\$5$l$F$$$k>pJs$O!"L$$@(B Apache 2.0 $B8~$1$K%"%C%W%G!<%H$5$l$F$$$^$;$s!#(B -Apache 2.0 $B$G$O!"%b%8%e!<%k$N=g=x$E$1$K0[$J$k;EAH$_$r;H$C$F$$$^$9!#(B
    +
    $B5-:\$5$l$F$$$k>pJs$O!"L$$@(B Apache 2.0 $B8~$1$K%"%C%W%G!<%H$5$l$F$$$^$;$s!#(B +Apache 2.0 $B$G$O!"%b%8%e!<%k$N=g=x$E$1$K0[$J$k;EAH$_$r;H$C$F$$$^$9!#(B

    AuthAuthoritative $B%G%#%l%/%F%#%V$GL@<(E*$K(B 'off'$B$K@_Dj$9$k$H!"(B @@ -40,17 +42,17 @@ Apache 2.0 $B$G$O!"%b%8%e!<%k$N=g=x$E$1$K0[$J$k;EAH$_$r;H$C$F$$$^$9!#(B$B$G$9$+$i!"Fs$D0J>e$N%b%8%e!<%k$N%G!<%?%Y!<%9$GF10l$N(B $B%f!<%6(B ID $B$,8=$o$l$?$j!"(B - $B$^$?$O!"@5$7$$(B Require + $B$^$?$O!"@5$7$$(B Require $B%G%#%l%/%F%#%V$,Fs$D0J>e$N%b%8%e!<%k$G8=$o$l$?$j$7$?>l9g$O!"(B $B0l$DL\$N%b%8%e!<%k$,G'Dj$r9T$C$F!"(BAuthAuthoritative $B@_Dj$K4X$o$i$:!"(B $B%"%/%;%9$O0\9T$7$^$;$s!#(B

    -

    $B0lHLE*$J;HMQK!$O!"(Bauth_dbm, - mod_auth_msql, mod_auth_anon +

    $B0lHLE*$J;HMQK!$O!"(Bauth_dbm, + mod_auth_msql, mod_auth_anon $B$H$$$C$?%G!<%?%Y!<%9%b%8%e!<%k$N0l$D$HAH$_9g$o$;$k$3$H$G$9!#(B $B$3$l$i$N%b%8%e!<%k$OB?$/$N%f!<%6;q3J8!::$rDs6!$7$F$/$l$^$9!#(B $B$7$+$7!">/?t$N(B ($B4IM}AuthUserFile + AuthUserFile $B$GNI$/J]8n$5$l$?!"$h$jDc%l%Y%k$K0\9T$9$k$h$&$K$7$^$9!#(B

    $B%G%U%)%k%H$G$O!"@)8f$O0\9T$7$^$;$s!#$=$7$F!"L$CN$N%f!<%6(B ID $B$d(B @@ -58,7 +60,7 @@ Apache 2.0 $B$G$O!"%b%8%e!<%k$N=g=x$E$1$K0[$J$k;EAH$_$r;H$C$F$$$^$9!#(B -

    $BCV$+$J$$$G2<$5$$(B$B!#$=$&$7$J$$$H(B - AuthUserFile - $B$O%@%&%s%m!<%I$G$-$F$7$^$$$^$9!#(B

    $B%;%-%e%j%F%#(B

    $B%f!<%6$,<+J,<+?H$G:n@.$7$?(B +

    $B%;%-%e%j%F%#(B

    $B%f!<%6$,<+J,<+?H$G:n@.$7$?(B .htaccess $B%U%!%$%k$GG'>Z$G$-$k$h$&$K$9$k$3$H$N1F6A$r(B $B9MN8$KF~$l$F$*$$$F$/$@$5$$!#$=$7$F!"(B $B$=$l$,K\Ev$K4uK>$N5sF0$G$"$k$+$I$&$+$r8!F$$7$F$/$@$5$$!#(B @@ -67,57 +69,57 @@ Apache 2.0 $B$G$O!"%b%8%e!<%k$N=g=x$E$1$K0[$J$k;EAH$_$r;H$C$F$$$^$9!#(B
    -

    AuthGroupFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $BG'>Z$K;HMQ$9$k%f!<%6%0%k!<%W$N0lMw$,3JG<$5$l$F$$$k!"(B -$B%F%-%9%H%U%!%$%k$NL>A0$r@_Dj$9$k(B
    $B9=J8(B: - AuthGroupFile file-path
    $B%3%s%F%-%9%H(B: - $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - AuthConfig
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_auth
    + AuthUserFile + $B$O%@%&%s%m!<%I$G$-$F$7$^$$$^$9!#(B
    +
    top

    AuthGroupFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $BG'>Z$K;HMQ$9$k%f!<%6%0%k!<%W$N0lMw$,3JG<$5$l$F$$$k!"(B +$B%F%-%9%H%U%!%$%k$NL>A0$r@_Dj$9$k(B
    $B9=J8(B: + AuthGroupFile file-path
    $B%3%s%F%-%9%H(B: + $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + AuthConfig
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_auth

    AuthGroupFile $B%G%#%l%/%F%#%V$O!"(B $BG'>Z$K;HMQ$9$k%f!<%6%0%k!<%W$N0lMw$,3JG<$5$l$F$$$k!"(B $B%F%-%9%H%U%!%$%k$NL>A0$r@_Dj$7$^$9!#(B - file-path $B$O%0%k!<%W%U%!%$%k$X(B$B$N%Q%9$G$9!#(B + file-path $B$O%0%k!<%W%U%!%$%k$X$N%Q%9$G$9!#(B $B$b$7@dBP%Q%9$G$J$1$l$P(B ($B$D$^$j(B $B%9%i%C%7%e$G;O$^$i$J$$%Q%9$G$"$l$P(B) - $B!"(BServerRoot + $B!"(BServerRoot $B$+$i$NAjBP%Q%9$H$7$F07$o$l$^$9!#(B

    $B%0%k!<%W%U%!%$%k3F9T$O!"%0%k!<%WL>!"%3%m%s!"$=$7$F(B $B%9%Z!<%96h@Z$j$G$=$N%a%s%P!<$N%f!<%6L>$r5-=R$7$^$9!#(B $BNc$($P(B:

    -
    mygroup: bob joe anne
    +

    mygroup: bob joe anne

    $BBg$-$J%U%!%$%k$rC5:w$9$k$N$O!"(B$BHs>o$K(B$B8zN($,0-$$$H$$$&E@$K(B $BCm0U$7$F$/$@$5$$!#$=$N$h$&$J>l9g$O!"(B - AuthDBMGroupFile + AuthDBMGroupFile $B$rBe$o$j$K;H$&$Y$-$G$7$g$&!#(B

    -

    $B%;%-%e%j%F%#(B

    +

    $B%;%-%e%j%F%#(B

    AuthGroupFile $B$O!"%&%'%V%5!<%P$N%I%-%e%a%s%H%D%j!<$N30B&$K(B $BJ]4I$9$k$h$&$K$7$F$/$@$5$$!#(B $BJ]8n$7$h$&$H$7$F$$$k%G%#%l%/%H%j0J2<$K$O!"(B$BCV$+$J$$$G2<$5$$(B$B!#(B $B$=$&$7$J$$$H(B AuthGroupFile $B$O%@%&%s%m!<%I$G$-$F$7$^$$$^$9!#(B

    -
    -

    AuthUserFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $BG'>Z$K;HMQ$9$k%f!<%6$H%Q%9%o!<%I$N0lMw$,3JG<$5$l$F$$$k!"(B -$B%F%-%9%H%U%!%$%k$NL>A0$r@_Dj$9$k(B
    $B9=J8(B: - AuthUserFile file-path
    $B%3%s%F%-%9%H(B: - $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - AuthConfig
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_auth
    +
    +
    top

    AuthUserFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $BG'>Z$K;HMQ$9$k%f!<%6$H%Q%9%o!<%I$N0lMw$,3JG<$5$l$F$$$k!"(B +$B%F%-%9%H%U%!%$%k$NL>A0$r@_Dj$9$k(B
    $B9=J8(B: + AuthUserFile file-path
    $B%3%s%F%-%9%H(B: + $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + AuthConfig
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_auth

    AuthUserFile $B%G%#%l%/%F%#%V$O!"(B $B%f!<%6G'>Z$N$?$a$N%f!<%6$H%Q%9%o!<%I$N0lMw$r3JG<$7$?(B $B%F%-%9%H%U%!%$%k$NL>A0$r@_Dj$7$^$9!#(Bfile-path $B$O%f!<%6%U%!%$%k$X$N%Q%9$G$9!#(B $B$b$7@dBP%Q%9$G$J$1$l$P(B ($B$D$^$j(B $B%9%i%C%7%e$G;O$^$i$J$$%Q%9$G$"$l$P(B) - $B!"(BServerRoot + $B!"(BServerRoot $B$+$i$NAjBP%Q%9$H$7$F07$o$l$^$9!#(B

    $B%f!<%6%U%!%$%k$N3F9T$K$O!"%f!<%6L>!"%3%m%s!"(B @@ -132,22 +134,22 @@ Apache 2.0 $B$G$O!"%b%8%e!<%k$N=g=x$E$1$K0[$J$k;EAH$_$r;H$C$F$$$^$9!#(B$B=i4|(B ID username $B$G!"(BFilename $B$H$$$&%Q%9%o!<%I%U%!%$%k$r@8@.$7$^$9!#(B - $B -

    htpasswd -c Filename username
    + $B +

    htpasswd -c Filename username

    $B%Q%9%o!<%I%U%!%$%k(B Filename $B$K!"(Busername2 $B$rDI2C$7$?$j=$@5$7$?$j$7$^$9(B:

    -
    htpasswd Filename username2
    +

    htpasswd Filename username2

    ($BLuCm(B: $BHs>o$KB?$/$N%f!<%6$rEPO?$9$k$HBg$-$J%U%!%$%k$K$J$j$^$9$,(B) $BBg$-$J%F%-%9%H%U%!%$%k$r8!:w$9$k$N$O(B$BHs>o$K(B$B8zN($,0-$$(B $B$H$$$&$3$H$KCm0U$7$F$/$@$5$$!#$=$N$h$&$JI,MW$N$"$k;~$O!"(B - AuthDBMUserFile + AuthDBMUserFile $B$rBe$o$j$K;H$C$F$/$@$5$$!#(B

    -

    $B%;%-%e%j%F%#(B

    AuthUserFile +

    $B%;%-%e%j%F%#(B

    AuthUserFile $B$O!"%&%'%V%5!<%P$N%I%-%e%a%s%H%D%j!<$N30B&$KJ]4I$9$k$h$&$K$7$F$/$@$5$$!#(B $BJ]8n$7$h$&$H$7$F$$$k%G%#%l%/%H%j0J2<$K$O!"(B$BCV$+$J$$$G2<$5$$(B$B!#(B -$B$=$&$7$J$$$H(B AuthUserFile $B$O%@%&%s%m!<%I$G$-$F$7$^$$$^$9!#(B

    +$B$=$&$7$J$$$H(B AuthUserFile $B$O%@%&%s%m!<%I$G$-$F$7$^$$$^$9!#(B

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_auth_anon.html.en b/docs/manual/mod/mod_auth_anon.html.en index 6647590f48..78728b05a0 100644 --- a/docs/manual/mod/mod_auth_anon.html.en +++ b/docs/manual/mod/mod_auth_anon.html.en @@ -1,12 +1,14 @@ -mod_auth_anon - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_auth_anon

    Description: - Allows "anonymous" user access to authenticated - areas
    Status: - Extension
    Module Identifier: - auth_anon_module

    Summary

    + -->mod_auth_anon - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_auth_anon

    Description: + Allows "anonymous" user access to authenticated + areas
    Status: + Extension
    Module Identifier: + auth_anon_module

    Summary

    This module does access control in a manner similar to anonymous-ftp sites; i.e. have a 'magic' user id 'anonymous' and the email address as a password. These email @@ -19,7 +21,7 @@ tracking is that, unlike magic-cookies and funny URL pre/postfixes, it is completely browser independent and it allows users to share URLs.

    -

    Directives

    Example

    +
    top

    Example

    The example below (when combined with the Auth directives of a htpasswd-file based (or GDM, mSQL etc.) base access @@ -48,116 +50,116 @@

    Excerpt of httpd.conf:

    -
    - Anonymous_NoUserId off
    - Anonymous_MustGiveEmail on
    - Anonymous_VerifyEmail on
    - Anonymous_LogEmail on
    - Anonymous anonymous guest www test welcome
    -
    +

    + Anonymous_NoUserId off
    + Anonymous_MustGiveEmail on
    + Anonymous_VerifyEmail on
    + Anonymous_LogEmail on
    + Anonymous anonymous guest www test welcome
    +
    AuthName "Use 'anonymous' & Email address for - guest entry"
    - AuthType basic
    -
    + guest entry"
    + AuthType basic
    +
    # An - AuthUserFile/AuthDBUserFile/AuthDBMUserFile
    - # directive must be specified, or use
    - # Anonymous_Authoritative for public access.
    - # In the .htaccess for the public directory, add:
    - <Files *>
    - Order Deny,Allow
    - Allow from all
    -
    - Require valid-user
    - </Files>
    -

    -

    Anonymous Directive

    Description: - Specifies userIDs that areallowed access without -password verification
    Syntax: - Anonymous user [user] ...
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_anon
    + AuthUserFile/AuthDBUserFile/AuthDBMUserFile
    + # directive must be specified, or use
    + # Anonymous_Authoritative for public access.
    + # In the .htaccess for the public directory, add:
    + <Files *>
    + Order Deny,Allow
    + Allow from all
    +
    + Require valid-user
    + </Files>
    +

    +
    top

    Anonymous Directive

    Description: + Specifies userIDs that areallowed access without +password verification
    Syntax: + Anonymous user [user] ...
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_anon

    A list of one or more 'magic' userIDs which are allowed access without password verification. The userIDs are space separated. It is possible to use the ' and " quotes to allow a space in a userID as well as the \ escape character.

    Please note that the comparison is - case-IN-sensitive.
    + case-IN-sensitive.
    I strongly suggest that the magic username 'anonymous' is always one of the allowed userIDs.

    Example:

    -
    Anonymous anonymous "Not Registered" 'I don\'t know'
    +

    Anonymous anonymous "Not Registered" 'I don\'t know'

    This would allow the user to enter without password verification by using the userId's 'anonymous', 'AnonyMous','Not Registered' and 'I Don't Know'.

    -

    Anonymous_Authoritative Directive

    Description: - Configures if authorization will fall-through -to other methods
    Syntax: - Anonymous_Authoritative on|off
    Default: - Anonymous_Authoritative off
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_anon
    +
    top

    Anonymous_Authoritative Directive

    Description: + Configures if authorization will fall-through +to other methods
    Syntax: + Anonymous_Authoritative on|off
    Default: + Anonymous_Authoritative off
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_anon

    When set 'on', there is no fall-through to other authorization methods. So if a userID does not match the values specified in the - Anonymous directive, + Anonymous directive, access is denied.

    Be sure you know what you are doing when you decide to switch it on. And remember that it is the linking order of the modules (in the Configuration / Make file) which details the order in which the Authorization modules are queried.

    -

    Anonymous_LogEmail Directive

    Description: - Sets whether the password entered will be logged in the -error log
    Syntax: - Anonymous_LogEmail on|off
    Default: - Anonymous_LogEmail on
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_anon
    +
    top

    Anonymous_LogEmail Directive

    Description: + Sets whether the password entered will be logged in the +error log
    Syntax: + Anonymous_LogEmail on|off
    Default: + Anonymous_LogEmail on
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_anon

    When set on, the default, the 'password' entered (which hopefully contains a sensible email address) is logged in the error log.

    -

    Anonymous_MustGiveEmail Directive

    Description: - Specifies whether blank passwords are allowed
    Syntax: - Anonymous_MustGiveEmail on|off
    Default: - Anonymous_MustGiveEmail on
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_anon
    +
    top

    Anonymous_MustGiveEmail Directive

    Description: + Specifies whether blank passwords are allowed
    Syntax: + Anonymous_MustGiveEmail on|off
    Default: + Anonymous_MustGiveEmail on
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_anon

    Specifies whether the user must specify an email address as the password. This prohibits blank passwords.

    -

    Anonymous_NoUserID Directive

    Description: - Sets whether the userID field may be empty
    Syntax: - Anonymous_NoUserID on|off
    Default: - Anonymous_NoUserID off
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_anon
    +
    top

    Anonymous_NoUserID Directive

    Description: + Sets whether the userID field may be empty
    Syntax: + Anonymous_NoUserID on|off
    Default: + Anonymous_NoUserID off
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_anon

    When set on, users can leave the userID (and perhaps the password field) empty. This can be very convenient for MS-Explorer users who can just hit return or click directly on the OK button; which seems a natural reaction.

    -

    Anonymous_VerifyEmail Directive

    Description: - Sets whether to check the password field for a correctly -formatted email address
    Syntax: - Anonymous_VerifyEmail on|off
    Default: - Anonymous_VerifyEmail off
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_anon
    +
    top

    Anonymous_VerifyEmail Directive

    Description: + Sets whether to check the password field for a correctly +formatted email address
    Syntax: + Anonymous_VerifyEmail on|off
    Default: + Anonymous_VerifyEmail off
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_anon

    When set on the 'password' entered is checked for at least one '@' and a '.' to encourage users to enter valid email - addresses (see the above Auth_LogEmail).

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + addresses (see the above Auth_LogEmail).

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_auth_dbm.html.en b/docs/manual/mod/mod_auth_dbm.html.en index 33e4322476..3a00f62433 100644 --- a/docs/manual/mod/mod_auth_dbm.html.en +++ b/docs/manual/mod/mod_auth_dbm.html.en @@ -1,28 +1,30 @@ -mod_auth_dbm - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_auth_dbm

    Description: - Provides for user authentication using DBM - files
    Status: - Extension
    Module Identifier: - auth_dbm_module

    Summary

    + -->mod_auth_dbm - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_auth_dbm

    Description: + Provides for user authentication using DBM + files
    Status: + Extension
    Module Identifier: + auth_dbm_module

    Summary

    This module provides for HTTP Basic Authentication, where the usernames and passwords are stored in DBM type database files. It is an alternative to the plain text password files - provided by mod_auth.

    -

    Directives

    See also

    AuthDBMAuthoritative Directive

    Description: - Sets whether authentication and authorization will be -passwed on to lower level modules
    Syntax: - AuthDBMAuthoritative on|off
    Default: - AuthDBMAuthoritative on
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_dbm
    - -
    This information has not been updated to take into account the -new module ordering techniques in Apache 2.0
    + provided by mod_auth.

    +
    top

    AuthDBMAuthoritative Directive

    Description: + Sets whether authentication and authorization will be +passwed on to lower level modules
    Syntax: + AuthDBMAuthoritative on|off
    Default: + AuthDBMAuthoritative on
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_dbm
    + +
    This information has not been updated to take into account the +new module ordering techniques in Apache 2.0

    Setting the AuthDBMAuthoritative directive explicitly to 'off' allows for both @@ -35,13 +37,13 @@ new module ordering techniques in Apache 2.0

    Required reply.

    So if a userID appears in the database of more than one module; - or if a valid Require + or if a valid Require directive applies to more than one module; then the first module will verify the credentials; and no access is passed on; regardless of the AuthAuthoritative setting.

    A common use for this is in conjunction with one of the - basic auth modules; such as mod_auth. Whereas this + basic auth modules; such as mod_auth. Whereas this DBM module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file.

    @@ -56,14 +58,14 @@ new module ordering techniques in Apache 2.0 is really what you want; Generally it is easier to just secure a single .htpasswd file, than it is to secure a database which might have more access interfaces.

    -

    AuthDBMGroupFile Directive

    Description: - Sets the name of the database file containing the list -of user groups for authentication
    Syntax: - AuthDBMGroupFile file-path
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_dbm
    +
    top

    AuthDBMGroupFile Directive

    Description: + Sets the name of the database file containing the list +of user groups for authentication
    Syntax: + AuthDBMGroupFile file-path
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_dbm

    The AuthDBMGroupFile directive sets the name of a DBM file containing the list of user groups for user authentication. File-path is the absolute path to the @@ -89,16 +91,16 @@ of user groups for authentication -AuthDBMGroupFile /www/userbase
    +

    +AuthDBMGroupFile /www/userbase
    AuthDBMUserFile /www/userbase -     +

    The key for the single DBM is the username. The value consists of

    -
    Unix Crypt-ed Password : List of Groups [ : (ignored) - ]
    +

    Unix Crypt-ed Password : List of Groups [ : (ignored) + ]

    The password section contains the Unix crypt() password as before. This is followed by a colon and the comma @@ -106,16 +108,16 @@ AuthDBMUserFile /www/userbase DBM file after another colon; it is ignored by the authentication module. This is what www.telescope.org uses for its combined password and group database.

    -

    AuthDBMType Directive

    Description: - Sets the type of database file that is used to -store passwords
    Syntax: - AuthDBMType default|SDBM|GDBM|NDBM|DB
    Default: - AuthDBMType default
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_dbm
    Compatibility: - Available in version 2.0.30 and later.
    +
    top

    AuthDBMType Directive

    Description: + Sets the type of database file that is used to +store passwords
    Syntax: + AuthDBMType default|SDBM|GDBM|NDBM|DB
    Default: + AuthDBMType default
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_dbm
    Compatibility: + Available in version 2.0.30 and later.

    Sets the type of database file that is used to store the passwords. The default database type is determined at compile time. The @@ -124,14 +126,14 @@ availability of other types of database files also depends on

    It is crucial that whatever program you use to create your password files is configured to use the same type of database.

    -

    AuthDBMUserFile Directive

    Description: - Sets thename of a database file containing the list of users and -passwords for authentication
    Syntax: - AuthDBMUserFile file-path
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_auth_dbm
    +
    top

    AuthDBMUserFile Directive

    Description: + Sets thename of a database file containing the list of users and +passwords for authentication
    Syntax: + AuthDBMUserFile file-path
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_auth_dbm

    The AuthDBMUserFile directive sets the name of a DBM file containing the list of users and passwords for user authentication. File-path is the absolute path to @@ -161,4 +163,4 @@ passwords for authenticationdbmmanage is included with Apache. This program can be used to create and update DBM format password files for use with this module.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +
    \ No newline at end of file diff --git a/docs/manual/mod/mod_auth_digest.html.en b/docs/manual/mod/mod_auth_digest.html.en index bcd38ae116..58c9840a6d 100644 --- a/docs/manual/mod/mod_auth_digest.html.en +++ b/docs/manual/mod/mod_auth_digest.html.en @@ -1,16 +1,18 @@ -mod_auth_digest - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_auth_digest

    Description: - User authentication using MD5 - Digest Authentication.
    Status: - Experimental
    Module Identifier: - auth_digest_module

    Summary

    + -->mod_auth_digest - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_auth_digest

    Description: + User authentication using MD5 + Digest Authentication.
    Status: + Experimental
    Module Identifier: + auth_digest_module

    Summary

    This module implements HTTP Digest Authentication. However, it has not been extensively tested and is therefore marked experimental.

    -

    Directives

    See also

    Using Digest Authentication

    +
    top

    Using Digest Authentication

    Using MD5 Digest authentication is very simple. Simply set up authentication normally, using "AuthType Digest" and @@ -19,17 +21,17 @@ "AuthDigestGroupFile". Then add a "AuthDigestDomain" directive containing at least the root URI(s) for this protection space. Example:

    -
    - <Location /private/>
    - AuthType Digest
    - AuthName "private area"
    - AuthDigestDomain /private/ http://mirror.my.dom/private2/
    - AuthDigestFile /web/auth/.digest_pw
    - Require valid-user
    +

    + <Location /private/>
    + AuthType Digest
    + AuthName "private area"
    + AuthDigestDomain /private/ http://mirror.my.dom/private2/
    + AuthDigestFile /web/auth/.digest_pw
    + Require valid-user
    </Location> -

    +

    -

    Note

    +

    Note

    Digest authentication provides a more secure password system than Basic authentication, but only works with supporting @@ -39,16 +41,16 @@ authentication is not as widely implemented as basic authentication, you should use it only in controlled settings.

    -
    -

    AuthDigestAlgorithm Directive

    Description: - Selects the algorithm used to calculate the challenge and -response hases in digest authentication
    Syntax: - AuthDigestAlgorithm MD5|MD5-sess
    Default: - AuthDigestAlgorithm MD5
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Experimental
    Module: - mod_auth_digest
    +
    +
    top

    AuthDigestAlgorithm Directive

    Description: + Selects the algorithm used to calculate the challenge and +response hases in digest authentication
    Syntax: + AuthDigestAlgorithm MD5|MD5-sess
    Default: + AuthDigestAlgorithm MD5
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Experimental
    Module: + mod_auth_digest

    The AuthDigestAlgorithm directive selects the algorithm used to calculate the challenge and response hashes.

    @@ -56,14 +58,14 @@ response hases in digest authenticationMD5-sess is not correctly implemented yet.

    -

    AuthDigestDomain Directive

    Description: - URIs that are in the same protection space for digest -authentication
    Syntax: - AuthDigestDomain URI [URI] ...
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Experimental
    Module: - mod_auth_digest
    +
    top

    AuthDigestDomain Directive

    Description: + URIs that are in the same protection space for digest +authentication
    Syntax: + AuthDigestDomain URI [URI] ...
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Experimental
    Module: + mod_auth_digest

    The AuthDigestDomain directive allows you to specify one or more URIs which are in the same protection space (i.e. use the same realm and username/password info). The @@ -84,14 +86,14 @@ authenticationAuthDigestFile Directive
    Description: - Location of the text file containing the list -of users and encoded passwords for digest authentication
    Syntax: - AuthDigestFile file-path
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Experimental
    Module: - mod_auth_digest
    +

    top

    AuthDigestFile Directive

    Description: + Location of the text file containing the list +of users and encoded passwords for digest authentication
    Syntax: + AuthDigestFile file-path
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Experimental
    Module: + mod_auth_digest

    The AuthDigestFile directive sets the name of a textual file containing the list of users and encoded passwords for digest authentication. File-path is the @@ -100,14 +102,14 @@ of users and encoded passwords for digest authenticationThe digest file uses a special format. Files in this format can be created using the htdigest utility found in the support/ subdirectory of the Apache distribution.

    -

    AuthDigestGroupFile Directive

    Description: - Name of the text file containing the list of groups -for digest authentication
    Syntax: - AuthDigestGroupFile file-path
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Experimental
    Module: - mod_auth_digest
    +
    top

    AuthDigestGroupFile Directive

    Description: + Name of the text file containing the list of groups +for digest authentication
    Syntax: + AuthDigestGroupFile file-path
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Experimental
    Module: + mod_auth_digest

    The AuthDigestGroupFile directive sets the name of a textual file containing the list of groups and their members (user names). File-path is the absolute path to @@ -117,7 +119,7 @@ for digest authenticationmygroup: bob joe anne

    +

    mygroup: bob joe anne

    Note that searching large text files is very inefficient.

    @@ -126,34 +128,34 @@ for digest authentication    AuthDigestNcCheck Directive
    Description: - Enables or disables checking of the nonce-count sent by the -server
    Syntax: - AuthDigestNcCheck On|Off
    Default: - AuthDigestNcCheck Off
    Context: - server config
    Status: - Experimental
    Module: - mod_auth_digest
    +
    top

    AuthDigestNcCheck Directive

    Description: + Enables or disables checking of the nonce-count sent by the +server
    Syntax: + AuthDigestNcCheck On|Off
    Default: + AuthDigestNcCheck Off
    Context: + server config
    Status: + Experimental
    Module: + mod_auth_digest

    Not implemented yet.

    -

    AuthDigestNonceFormat Directive

    Description: - Determines how the nonce is generated
    Syntax: - ???
    Default: - ???
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Experimental
    Module: - mod_auth_digest
    +
    top

    AuthDigestNonceFormat Directive

    Description: + Determines how the nonce is generated
    Syntax: + ???
    Default: + ???
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Experimental
    Module: + mod_auth_digest

    Not implemented yet.

    -

    AuthDigestNonceLifetime Directive

    Description: - How long the server nonce is valid
    Syntax: - AuthDigestNonceLifetime seconds
    Default: - AuthDigestNonceLifetime 300
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Experimental
    Module: - mod_auth_digest
    +
    top

    AuthDigestNonceLifetime Directive

    Description: + How long the server nonce is valid
    Syntax: + AuthDigestNonceLifetime seconds
    Default: + AuthDigestNonceLifetime 300
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Experimental
    Module: + mod_auth_digest

    The AuthDigestNonceLifetime directive controls how long the server nonce is valid. When the client contacts the server using an expired nonce the server will send @@ -163,15 +165,15 @@ serverseconds is less than 0 then the nonce never expires.

    -

    AuthDigestQop Directive

    Description: - Determines the quality-of-protection to use in digest -authentication
    Syntax: - AuthDigestQop none|auth|auth-int [auth|auth-int]
    Default: - AuthDigestQop auth
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Experimental
    Module: - mod_auth_digest
    +
    top

    AuthDigestQop Directive

    Description: + Determines the quality-of-protection to use in digest +authentication
    Syntax: + AuthDigestQop none|auth|auth-int [auth|auth-int]
    Default: + AuthDigestQop auth
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Experimental
    Module: + mod_auth_digest

    The AuthDigestQop directive determines the quality-of-protection to use. auth will only do authentication (username/password); auth-int is @@ -185,4 +187,4 @@ authenticationApache HTTP Server Version 2.0IndexHome \ No newline at end of file +

    \ No newline at end of file diff --git a/docs/manual/mod/mod_auth_ldap.html.en b/docs/manual/mod/mod_auth_ldap.html.en index 00e7215387..ac231400b3 100644 --- a/docs/manual/mod/mod_auth_ldap.html.en +++ b/docs/manual/mod/mod_auth_ldap.html.en @@ -1,14 +1,16 @@ -mod_auth_ldap - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_auth_ldap

    Description: - Allows an LDAP directory to be used to store the database -for HTTP Basic authentication.
    Status: - experimental
    Module Identifier: - auth_ldap_module
    Compatibility: - Available in version 2.0.41 and later

    Summary

    -

    mod_auth_ldap supports the following features:

    + -->mod_auth_ldap - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_auth_ldap

    Description: + Allows an LDAP directory to be used to store the database +for HTTP Basic authentication.
    Status: + experimental
    Module Identifier: + auth_ldap_module
    Compatibility: + Available in version 2.0.41 and later

    Summary

    +

    mod_auth_ldap supports the following features:

    See also

    Contents

    +
    top

    Contents

    top

    Operation

    There are two phases in granting access to a user. The first - phase is authentication, in which mod_auth_ldap + phase is authentication, in which mod_auth_ldap verifies that the user's credentials are valid. This also called the search/bind phase. The second phase is - authorization, in which mod_auth_ldap determines + authorization, in which mod_auth_ldap determines if the authenticated user is allowed access to the resource in question. This is also known as the compare phase.

    -

    The Authentication +

    The Authentication Phase

    -

    During the authentication phase, mod_auth_ldap +

    During the authentication phase, mod_auth_ldap searches for an entry in the directory that matches the username that the HTTP client passes. If a single unique match is found, - then mod_auth_ldap attempts to bind to the + then mod_auth_ldap attempts to bind to the directory server using the DN of the entry plus the password provided by the HTTP client. Because it does a search, then a bind, it is often referred to as the search/bind phase. Here are @@ -98,7 +101,7 @@ for HTTP Basic authentication.AuthLDAPURL directive with + filter provided in the AuthLDAPURL directive with the username passed by the HTTP client.

  • Search the directory using the generated filter. If the @@ -116,7 +119,7 @@ for HTTP Basic authentication.AuthLDAPURL + AuthLDAPURL Specifies the LDAP server, the base DN, the attribute to use in the search, as well as the @@ -124,14 +127,14 @@ for HTTP Basic authentication.AuthLDAPBindDN + AuthLDAPBindDN An optional DN to bind with during the search phase. - AuthLDAPBindPassword + AuthLDAPBindPassword An optional password to bind with during the search phase. @@ -139,16 +142,16 @@ for HTTP Basic authentication.The Authorization +

    The Authorization Phase

    -

    During the authorization phase, mod_auth_ldap +

    During the authorization phase, mod_auth_ldap attempts to determine if the user is authorized to access the resource. Many of these checks require - mod_auth_ldap to do a compare operation on the + mod_auth_ldap to do a compare operation on the LDAP server. This is why this phase is often referred to as the - compare phase. mod_auth_ldap accepts the - following Require + compare phase. mod_auth_ldap accepts the + following Require directives to determine if the credentials are acceptable:

      @@ -170,12 +173,12 @@ for HTTP Basic authentication.mod_auth_ldap uses the following directives during the +

      mod_auth_ldap uses the following directives during the compare phase:

      - + + - + +
      AuthLDAPURL AuthLDAPURL The attribute specified in the URL is used in compare operations for the require @@ -183,14 +186,14 @@ for HTTP Basic authentication.
      AuthLDAPCompareDNOnServerAuthLDAPCompareDNOnServer Determines the behavior of the require dn directive.
      AuthLDAPGroupAttributeAuthLDAPGroupAttribute Determines the attribute to use for comparisons in the require group @@ -198,7 +201,7 @@ for HTTP Basic authentication.
      AuthLDAPGroupAttributeIsDNAuthLDAPGroupAttributeIsDN Specifies whether to use the user DN or the username when doing comparisons for the @@ -206,25 +209,25 @@ for HTTP Basic authentication.
      The require Directives +
      top

      The require Directives

      -

      Apache's Require +

      Apache's Require directives are used during the authorization phase to ensure that a user is allowed to access a resource.

      -

      require +

      require valid-user

      -

      If this directive exists, mod_auth_ldap grants +

      If this directive exists, mod_auth_ldap grants access to any user that has successfully authenticated during the search/bind phase.

      -

      require user

      +

      require user

      The require user directive specifies what usernames can access the resource. Once - mod_auth_ldap has retrieved a unique DN from the + mod_auth_ldap has retrieved a unique DN from the directory, it does an LDAP compare operation using the username specified in the require user to see if that username is part of the just-fetched LDAP entry. Multiple users can be @@ -232,17 +235,17 @@ for HTTP Basic authentication.

      AuthLDAPURL of + directives, with one user per line. For example, with a AuthLDAPURL of ldap://ldap/o=Airius?cn (i.e., cn is used for searches), the following require directives could be used to restrict access:

      -
      -require user Barbara Jenson
      -require user Fred User
      -require user Joe Manager
      -
      +

      +require user Barbara Jenson
      +require user Fred User
      +require user Joe Manager
      +

      -

      Because of the way that mod_auth_ldap handles this +

      Because of the way that mod_auth_ldap handles this directive, Barbara Jenson could sign on as Barbara Jenson, Babs Jenson or any other cn that she has in her LDAP entry. Only the single require @@ -252,32 +255,32 @@ require user Joe Manager

      If the uid attribute was used instead of the cn attribute in the URL above, the above three lines could be condensed to

      -
      require user bjenson fuser jmanager
      +

      require user bjenson fuser jmanager

      -

      require group

      +

      require group

      This directive specifies an LDAP group whose members are allowed access. It takes the distinguished name of the LDAP group. For example, assume that the following entry existed in the LDAP directory:

      -
      -dn: cn=Administrators, o=Airius
      -objectClass: groupOfUniqueNames
      -uniqueMember: cn=Barbara Jenson, o=Airius
      -uniqueMember: cn=Fred User, o=Airius
      -
      +

      +dn: cn=Administrators, o=Airius
      +objectClass: groupOfUniqueNames
      +uniqueMember: cn=Barbara Jenson, o=Airius
      +uniqueMember: cn=Fred User, o=Airius
      +

      The following directive would grant access to both Fred and Barbara:

      -
      require group cn=Administrators, o=Airius
      +

      require group cn=Administrators, o=Airius

      -

      Behavior of this directive is modified by the AuthLDAPGroupAttribute and - AuthLDAPGroupAttributeIsDN +

      Behavior of this directive is modified by the AuthLDAPGroupAttribute and + AuthLDAPGroupAttributeIsDN directives.

      -

      require dn

      +

      require dn

      The require dn directive allows the administrator to grant access based on distinguished names. It specifies a DN @@ -288,30 +291,30 @@ uniqueMember: cn=Fred User, o=Airius

      The following directive would grant access to a specific DN:

      -
      require dn cn=Barbara Jenson, o=Airius
      +

      require dn cn=Barbara Jenson, o=Airius

      -

      Behavior of this directive is modified by the AuthLDAPCompareDNOnServer +

      Behavior of this directive is modified by the AuthLDAPCompareDNOnServer directive.

      -

      Examples

      +
      top

      Examples

      • Grant access to anyone who exists in the LDAP directory, using their UID for searches. -
        -AuthLDAPURL ldap://ldap1.airius.com:389/ou=People, o=Airius?uid?sub?(objectClass=*)
        +

        +AuthLDAPURL ldap://ldap1.airius.com:389/ou=People, o=Airius?uid?sub?(objectClass=*)
        require valid-user -

        +

    • The next example is the same as above; but with the fields that have useful defaults omitted. Also, note the use of a redundant LDAP server. -
      AuthLDAPURL ldap://ldap1.airius.com ldap2.airius.com/ou=People, o=Airius
      +

      AuthLDAPURL ldap://ldap1.airius.com ldap2.airius.com/ou=People, o=Airius
      require valid-user -

      +

    • @@ -323,19 +326,19 @@ require valid-user this approach is not recommended: it's a better idea to choose an attribute that is guaranteed unique in your directory, such as uid. -
      -AuthLDAPURL ldap://ldap.airius.com/ou=People, o=Airius?cn
      +

      +AuthLDAPURL ldap://ldap.airius.com/ou=People, o=Airius?cn
      require valid-user -

      +

    • Grant access to anybody in the Administrators group. The users must authenticate using their UID. -
      -AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid
      +

      +AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid
      require group cn=Administrators, o=Airius -

      +

    • @@ -344,10 +347,10 @@ require group cn=Administrators, o=Airius of qpagePagerID. The example will grant access only to people (authenticated via their UID) who have alphanumeric pagers: -
      -AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(qpagePagerID=*)
      +

      +AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(qpagePagerID=*)
      require valid-user -

      +

    • @@ -360,10 +363,10 @@ require valid-user a filter, plus grant access to Joe Manager, who doesn't have a pager, but does need to access the same resource:

      -
      -AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(|(qpagePagerID=*)(uid=jmanager))
      +

      +AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(|(qpagePagerID=*)(uid=jmanager))
      require valid-user -

      +

      This last may look confusing at first, so it helps to evaluate what the search filter will look like based on who @@ -375,30 +378,30 @@ require valid-user Fred User connects as fuser, the filter would look like

      -
      (&(|(qpagePagerID=*)(uid=jmanager))(uid=fuser))
      +

      (&(|(qpagePagerID=*)(uid=jmanager))(uid=fuser))

      The above search will only succeed if fuser has a pager. When Joe Manager connects as jmanager, the filter looks like

      -
      (&(|(qpagePagerID=*)(uid=jmanager))(uid=jmanager))
      +

      (&(|(qpagePagerID=*)(uid=jmanager))(uid=jmanager))

      The above search will succeed whether jmanager has a pager or not.

      • -

      Using TLS

      +
      top

      Using TLS

      -

      To use TLS, simply set the AuthLDAPStartTLS to on. +

      To use TLS, simply set the AuthLDAPStartTLS to on. Nothing else needs to be done (other than ensure that your LDAP server is configured for TLS).

      -

      Using SSL

      +
      top

      Using SSL

      -

      If mod_auth_ldap is linked against the +

      If mod_auth_ldap is linked against the Netscape/iPlanet LDAP SDK, it will not talk to any SSL server unless that server has a certificate signed by a known Certificate Authority. As part of the configuration - mod_auth_ldap needs to be told where it can find + mod_auth_ldap needs to be told where it can find a database containing the known CAs. This database is in the same format as Netscape Communicator's cert7.db database. The easiest way to get this file is to start up a fresh @@ -406,13 +409,13 @@ require valid-user $HOME/.netscape/cert7.db file.

      To specify a secure LDAP server, use ldaps:// in the - AuthLDAPURL + AuthLDAPURL directive, instead of ldap://.

      -

      Using Microsoft +

      top

      Using Microsoft FrontPage with mod_auth_ldap

      Normally, FrontPage uses FrontPage-web-specific user/group - files (i.e., the mod_auth module) to handle all + files (i.e., the mod_auth module) to handle all authentication. Unfortunately, it is not possible to just change to LDAP authentication by adding the proper directives, because it will break the Permissions forms in @@ -423,23 +426,23 @@ require valid-user authentication to it is a matter of adding the following directives to every .htaccess file that gets created in the web

      -
      +
       AuthLDAPURL            the url
 AuthLDAPAuthoritative  off
 AuthLDAPFrontPageHack  on
-
      +
      -

      AuthLDAPAuthoritative must be - off to allow mod_auth_ldap to decline group +

      AuthLDAPAuthoritative must be + off to allow mod_auth_ldap to decline group authentication so that Apache will fall back to file authentication for checking group membership. This allows the FrontPage-managed group file to be used.

      -

      How It Works

      +

      How It Works

      FrontPage restricts access to a web by adding the require valid-user directive to the .htaccess - files. If AuthLDAPFrontPageHack is not + files. If AuthLDAPFrontPageHack is not on, the require valid-user directive will succeed for any user who is valid as far as LDAP is concerned. This means that anybody who has an entry in @@ -454,12 +457,12 @@ AuthLDAPFrontPageHack on operations from the FrontPage client.

      -

      Caveats

      +

      Caveats

      • When choosing the LDAP URL, the attribute to use for authentication should be something that will also be valid - for putting into a mod_auth user file. The user ID is + for putting into a mod_auth user file. The user ID is ideal for this.
      • When adding users via FrontPage, FrontPage administrators @@ -470,175 +473,175 @@ AuthLDAPFrontPageHack on LDAP database, and not against the password in the local user file. This could cause confusion for web administrators.
        • -
      • Apache must be compiled with mod_auth in order to +
      • Apache must be compiled with mod_auth in order to use FrontPage support. This is because Apache will still use - the mod_auth group file for determine the extent of a + the mod_auth group file for determine the extent of a user's access to the FrontPage web.
      • The directives must be put in the .htaccess - files. Attempting to put them inside <Location> or <Directory> directives won't work. This - is because mod_auth_ldap has to be able to grab - the AuthUserFile + files. Attempting to put them inside <Location> or <Directory> directives won't work. This + is because mod_auth_ldap has to be able to grab + the AuthUserFile directive that is found in FrontPage .htaccess files so that it knows where to look for the valid user list. If - the mod_auth_ldap directives aren't in the same + the mod_auth_ldap directives aren't in the same .htaccess file as the FrontPage directives, then - the hack won't work, because mod_auth_ldap will + the hack won't work, because mod_auth_ldap will never get a chance to process the .htaccess file, and won't be able to find the FrontPage-managed user file.
      -

      AuthLDAPAuthoritative Directive

      Description: -
      Syntax: - AuthLDAPAuthoritative on|off
      Default: - AuthLDAPAuthoritative on
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      +
      top

      AuthLDAPAuthoritative Directive

      Description: +
      Syntax: + AuthLDAPAuthoritative on|off
      Default: + AuthLDAPAuthoritative on
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      Set to off if this module should let other authentication modules attempt to authenticate the user, should authentication with this module fail. Control is only passed on to lower modules if there is no DN or rule that matches the supplied user name (as passed by the client).

      -

      AuthLDAPBindDN Directive

      Description: -
      Syntax: - AuthLDAPBindDN distinguished-name
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      +
      top

      AuthLDAPBindDN Directive

      Description: +
      Syntax: + AuthLDAPBindDN distinguished-name
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      An optional DN used to bind to the server when searching for - entries. If not provided, mod_auth_ldap will use + entries. If not provided, mod_auth_ldap will use an anonymous bind.

      -

      AuthLDAPBindPassword Directive

      Description: -
      Syntax: - AuthLDAPBindPassword password
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      +
      top

      AuthLDAPBindPassword Directive

      Description: +
      Syntax: + AuthLDAPBindPassword password
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      A bind password to use in conjunction with the bind DN. Note that the bind password is probably sensitive data, and should be - properly protected. You should only use the AuthLDAPBindDN and AuthLDAPBindPassword if you + properly protected. You should only use the AuthLDAPBindDN and AuthLDAPBindPassword if you absolutely need them to search the directory.

      -

      AuthLDAPCompareDNOnServer Directive

      Description: -
      Syntax: - AuthLDAPCompareDNOnServer on|off
      Default: - AuthLDAPCompareDNOnServer on
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      -

      When set, mod_auth_ldap will use the LDAP +

      top

      AuthLDAPCompareDNOnServer Directive

      Description: +
      Syntax: + AuthLDAPCompareDNOnServer on|off
      Default: + AuthLDAPCompareDNOnServer on
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap
      +

      When set, mod_auth_ldap will use the LDAP server to compare the DNs. This is the only foolproof way to - compare DNs. mod_auth_ldap will search the + compare DNs. mod_auth_ldap will search the directory for the DN specified with the require dn directive, then, retrieve the DN and compare it with the DN retrieved from the user entry. If this directive is not set, - mod_auth_ldap simply does a string comparison. It + mod_auth_ldap simply does a string comparison. It is possible to get false negatives with this approach, but it is - much faster. Note the mod_ldap cache can speed up + much faster. Note the mod_ldap cache can speed up DN comparison in most situations.

      -

      AuthLDAPDereferenceAliases Directive

      Description: -
      Syntax: - AuthLDAPDereferenceAliases never|searching|finding|always
      Default: - AuthLDAPDereferenceAliases Always
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      -

      This directive specifies when mod_auth_ldap will +

      top

      AuthLDAPDereferenceAliases Directive

      Description: +
      Syntax: + AuthLDAPDereferenceAliases never|searching|finding|always
      Default: + AuthLDAPDereferenceAliases Always
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap
      +

      This directive specifies when mod_auth_ldap will de-reference aliases during LDAP operations. The default is always.

      -

      AuthLDAPEnabled Directive

      Description: -
      Syntax: - AuthLDAPEnabled on|off
      Default: - AuthLDAPEnabled on
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      +
      top

      AuthLDAPEnabled Directive

      Description: +
      Syntax: + AuthLDAPEnabled on|off
      Default: + AuthLDAPEnabled on
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      Set to off to disable - mod_auth_ldap in certain directories. This is - useful if you have mod_auth_ldap enabled at or + mod_auth_ldap in certain directories. This is + useful if you have mod_auth_ldap enabled at or near the top of your tree, but want to disable it completely in certain locations.

      -

      AuthLDAPFrontPageHack Directive

      Description: -
      Syntax: - AuthLDAPFrontPageHack on|off
      Default: - AuthLDAPFronPageHack off
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      +
      top

      AuthLDAPFrontPageHack Directive

      Description: +
      Syntax: + AuthLDAPFrontPageHack on|off
      Default: + AuthLDAPFronPageHack off
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      See the section on using Microsoft - FrontPage with mod_auth_ldap.

      -

      AuthLDAPGroupAttribute Directive

      Description: -
      Syntax: - AuthLDAPGroupAttribute attribute
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      + FrontPage with mod_auth_ldap.

      +
      top

      AuthLDAPGroupAttribute Directive

      Description: +
      Syntax: + AuthLDAPGroupAttribute attribute
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      This directive specifies which LDAP attributes are used to check for group membership. Multiple attributes can be used by specifying this directive multiple times. If not specified, - then mod_auth_ldap uses the member and + then mod_auth_ldap uses the member and uniquemember attributes.

      -

      AuthLDAPGroupAttributeIsDN Directive

      Description: -
      Syntax: - AuthLDAPGroupAttributeIsDN on|off
      Default: - AuthLDAPGroupAttributeIsDN on
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      +
      top

      AuthLDAPGroupAttributeIsDN Directive

      Description: +
      Syntax: + AuthLDAPGroupAttributeIsDN on|off
      Default: + AuthLDAPGroupAttributeIsDN on
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      When set on, this directive says to use the distinguished name of the client username when checking for group membership. Otherwise, the username will be used. For example, assume that the client sent the username bjenson, which corresponds to the LDAP DN cn=Babs Jenson, o=Airius. If this directive is set, - mod_auth_ldap will check if the group has + mod_auth_ldap will check if the group has cn=Babs Jenson, o=Airius as a member. If this - directive is not set, then mod_auth_ldap will + directive is not set, then mod_auth_ldap will check if the group has bjenson as a member.

      -

      AuthLDAPRemoteUserIsDN Directive

      Description: -
      Syntax: - AuthLDAPRemoteUserIsDN on|off
      Default: - AuthLDAPUserIsDN off
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      +
      top

      AuthLDAPRemoteUserIsDN Directive

      Description: +
      Syntax: + AuthLDAPRemoteUserIsDN on|off
      Default: + AuthLDAPUserIsDN off
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      If this directive is set to on, the value of the REMOTE_USER environment variable will be set to the full distinguished name of the authenticated user, rather than just the username that was passed by the client. It is turned off by default.

      -

      AuthLDAPStartTLS directive Directive

      Description: -
      Syntax: - AuthLDAPStartTLS on|off
      Default: - AuthLDAPStartTLS off
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      +
      top

      AuthLDAPStartTLS directive Directive

      Description: +
      Syntax: + AuthLDAPStartTLS on|off
      Default: + AuthLDAPStartTLS off
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      If this directive is set to on, - mod_auth_ldap will start a secure TLS session + mod_auth_ldap will start a secure TLS session after connecting to the LDAP server. This requires your LDAP server to support TLS.

      -

      AuthLDAPUrl Directive

      Description: -
      Syntax: - AuthLDAPUrl url
      Context: - directory, .htaccess
      Override: - AuthConfig
      Status: - experimental
      Module: - mod_auth_ldap
      +
      top

      AuthLDAPUrl Directive

      Description: +
      Syntax: + AuthLDAPUrl url
      Context: + directory, .htaccess
      Override: + AuthConfig
      Status: + experimental
      Module: + mod_auth_ldap

      An RFC 2255 URL which specifies the LDAP search parameters to use. The syntax of the URL is

      -
      ldap://host:port/basedn?attribute?scope?filter
      +

      ldap://host:port/basedn?attribute?scope?filter

      ldap
      @@ -655,7 +658,7 @@ AuthLDAPFrontPageHack on localhost:389 for ldap, and localhost:636 for ldaps). To specify multiple, redundant LDAP servers, just list all - servers, separated by spaces. mod_auth_ldap + servers, separated by spaces. mod_auth_ldap will try connecting to each server in turn, until it makes a successful connection.

      @@ -665,7 +668,7 @@ AuthLDAPFrontPageHack on down.

      If the LDAP server goes down and breaks an existing - connection, mod_auth_ldap will attempt to + connection, mod_auth_ldap will attempt to re-connect, starting with the primary server, and trying each redundant server in turn. Note that this is different than a true round-robin search.

      @@ -718,5 +721,5 @@ AuthLDAPFrontPageHack on Jenson, the resulting search filter will be (&(posixid=*)(cn=Babs Jenson)).

      -

      See above for examples of AuthLDAPURL URLs.

      -

      Apache HTTP Server Version 2.0

      IndexHome \ No newline at end of file +

      See above for examples of AuthLDAPURL URLs.

      +
      \ No newline at end of file diff --git a/docs/manual/mod/mod_autoindex.html.en b/docs/manual/mod/mod_autoindex.html.en index 1cf3e1ea6e..85498a3c7b 100644 --- a/docs/manual/mod/mod_autoindex.html.en +++ b/docs/manual/mod/mod_autoindex.html.en @@ -1,29 +1,31 @@ -mod_autoindex - Apache HTTP Server
      [APACHE DOCUMENTATION]

      Apache HTTP Server Version 2.0

      Apache Module mod_autoindex

      Description: - Generates directory indexes, + -->mod_autoindex - Apache HTTP Server

      Modules | Directives | FAQ | Glossary | Sitemap

      Apache HTTP Server Version 2.0

      <-

      Apache Module mod_autoindex

      Description: + Generates directory indexes, automatically, similar to the Unix ls command or the - Win32 dir shell command
      Status: - Base
      Module Identifier: - autoindex_module

      Summary

      + Win32 dir shell command
      Status: + Base
      Module Identifier: + autoindex_module

      Summary

      The index of a directory can come from one of two sources:

      The two functions are separated so that you can completely remove (or replace) automatic index generation should you want @@ -31,17 +33,17 @@

      Automatic index generation is enabled with using Options +Indexes. See the - Options directive for + Options directive for more details.

      -

      If the FancyIndexing - option is given with the IndexOptions directive, +

      If the FancyIndexing + option is given with the IndexOptions directive, the column headers are links that control the order of the display. If you select a header link, the listing will be regenerated, sorted by the values in that column. Selecting the same header repeatedly toggles between ascending and descending order. These column header links are suppressed with - IndexOptions directive's + IndexOptions directive's SuppressColumnSorting option.

      Note that when the display is sorted by "Size", it's the @@ -49,7 +51,7 @@ displayed value - so a 1010-byte file will always be displayed before a 1011-byte file (if in ascending order) even though they both are shown as "1K".

      -

      Directives

      Autoindex Request Query Arguments

      +
      top

      Autoindex Request Query Arguments

      Apache 2.0.23 reorganized the Query Arguments for Column Sorting, and introduced an entire group of new query options. @@ -72,15 +74,15 @@ name

    • C=D sorts the directory by description, then - file name
      -  
      • + file name
      +  
    • O=A sorts the listing in Ascending Order
    • O=D sorts the listing in Descending - Order
      -  
      • + Order
      +  
    • F=0 formats the listing as a simple list (not FancyIndexed)
      • @@ -89,13 +91,13 @@ list
    • F=2 formats the listing as an HTMLTable - FancyIndexed list
      -  
      • + FancyIndexed list
      +  
    • V=0 disables version sorting
      • -
    • V=1 enables version sorting
      -  
      • +
    • V=1 enables version sorting
      +  
    • P=pattern lists only files matching the given pattern
      • @@ -115,40 +117,40 @@ to assure the arguments are all parsed before mod_autoindex encounters the X=Go input.

      -
      -<FORM METHOD="GET">
      -  Show me a <SELECT NAME="F">
      -    <OPTION VALUE="0"> Plain list
      -    <OPTION VALUE="1" SELECTED> Fancy list
      -    <OPTION VALUE="2"> Table list
      -  </SELECT>
      -  Sorted by <SELECT NAME="C">
      -    <OPTION VALUE="N" SELECTED> Name
      -    <OPTION VALUE="M"> Date Modified
      -    <OPTION VALUE="S"> Size
      -    <OPTION VALUE="D"> Description
      -  </SELECT>
      -  <SELECT NAME="O">
      -    <OPTION VALUE="A" SELECTED> Ascending
      -    <OPTION VALUE="D"> Descending
      -  </SELECT>
      -  <SELECT NAME="V">
      -    <OPTION VALUE="0" SELECTED> in Normal order
      -    <OPTION VALUE="1"> in Version order
      -  </SELECT>
      -  Matching <INPUT TYPE="text" NAME="P" VALUE="*">
      -  <INPUT TYPE="submit" NAME="X" VALUE="Go">
      +

      +<FORM METHOD="GET">
      +  Show me a <SELECT NAME="F">
      +    <OPTION VALUE="0"> Plain list
      +    <OPTION VALUE="1" SELECTED> Fancy list
      +    <OPTION VALUE="2"> Table list
      +  </SELECT>
      +  Sorted by <SELECT NAME="C">
      +    <OPTION VALUE="N" SELECTED> Name
      +    <OPTION VALUE="M"> Date Modified
      +    <OPTION VALUE="S"> Size
      +    <OPTION VALUE="D"> Description
      +  </SELECT>
      +  <SELECT NAME="O">
      +    <OPTION VALUE="A" SELECTED> Ascending
      +    <OPTION VALUE="D"> Descending
      +  </SELECT>
      +  <SELECT NAME="V">
      +    <OPTION VALUE="0" SELECTED> in Normal order
      +    <OPTION VALUE="1"> in Version order
      +  </SELECT>
      +  Matching <INPUT TYPE="text" NAME="P" VALUE="*">
      +  <INPUT TYPE="submit" NAME="X" VALUE="Go">
      </FORM> -

      - -

      AddAlt Directive

      Description: - Alternate text to display for a file, instead of an -icon selected by filename
      Syntax: - AddAlt string file [file] ...
      Context: - server config, virtual host, directory, .htaccess
      Override: - Indexes
      Status: - Base
      Module: - mod_autoindex
      +

      + +
      top

      AddAlt Directive

      Description: + Alternate text to display for a file, instead of an +icon selected by filename
      Syntax: + AddAlt string file [file] ...
      Context: + server config, virtual host, directory, .htaccess
      Override: + Indexes
      Status: + Base
      Module: + mod_autoindex

      AddAlt provides the alternate text to display for a file, instead of an icon, for FancyIndexing. File is a file extension, partial filename, wild-card @@ -158,19 +160,19 @@ icon selected by filename

      - AddAlt "PDF" *.pdf
      +

      + AddAlt "PDF" *.pdf
      AddAlt "Compressed" *.gz *.zip *.Z -

    • -

    AddAltByEncoding Directive

    Description: - Alternate text to display for a file instead of an icon -selected by MIME-encoding
    Syntax: - AddAltByEncoding string MIME-encoding -[MIME-encoding] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +

    +
    top

    AddAltByEncoding Directive

    Description: + Alternate text to display for a file instead of an icon +selected by MIME-encoding
    Syntax: + AddAltByEncoding string MIME-encoding +[MIME-encoding] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    AddAltByEncoding provides the alternate text to display for a file, instead of an icon, for FancyIndexing. MIME-encoding is a valid content-encoding, such as @@ -180,18 +182,18 @@ selected by MIME-encoding +

    AddAltByEncoding "gzip" x-gzip - -

    AddAltByType Directive

    Description: - Alternate text to display for a file, instead of an -icon selected by MIME content-type
    Syntax: - AddAltByType string - MIME-type [MIME-type] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +

    +
    top

    AddAltByType Directive

    Description: + Alternate text to display for a file, instead of an +icon selected by MIME content-type
    Syntax: + AddAltByType string + MIME-type [MIME-type] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    AddAltByType sets the alternate text to display for a file, instead of an icon, for FancyIndexing. MIME-type is a valid content-type, such as @@ -201,17 +203,17 @@ icon selected by MIME content-type +

    AddAltByType "TXT" text/plain - -

    AddDescription Directive

    Description: - Description to display for a file
    Syntax: - AddDescription - string file [file] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +

    +
    top

    AddDescription Directive

    Description: + Description to display for a file
    Syntax: + AddDescription + string file [file] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    This sets the description to display for a file, for FancyIndexing. File is a file extension, partial filename, wild-card @@ -219,38 +221,38 @@ icon selected by MIME content-type). Example:

    -
    AddDescription "The planet Mars" - /web/pics/mars.gif
    +

    AddDescription "The planet Mars" + /web/pics/mars.gif

    The typical, default description field is 23 bytes wide. 6 more bytes are added by the - IndexOptions SuppressIcon option, 7 bytes are - added by the IndexOptions SuppressSize + IndexOptions SuppressIcon option, 7 bytes are + added by the IndexOptions SuppressSize option, and 19 bytes are added by the - IndexOptions SuppressLastModified option. + IndexOptions SuppressLastModified option. Therefore, the widest default the description column is ever assigned is 55 bytes.

    See the DescriptionWidth - IndexOptions keyword + IndexOptions keyword for details on overriding the size of this column, or allowing descriptions of unlimited length.

    -

    Caution

    Descriptive text defined with +

    Caution

    Descriptive text defined with AddDescription may contain HTML markup, such as tags and character entities. If the width of the description column should happen to truncate a tagged element (such as cutting off the end of a bolded phrase), the results may affect the rest of the directory listing.

    -
    -

    AddIcon Directive

    Description: - Icon to display for a file selected by name
    Syntax: - AddIcon icon - name [name] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +
    +
    top

    AddIcon Directive

    Description: + Icon to display for a file selected by name
    Syntax: + AddIcon icon + name [name] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    This sets the icon to display next to a file ending in name for FancyIndexing. Icon is either a (%-escaped) relative URL to the icon, @@ -263,24 +265,24 @@ icon selected by MIME content-type - AddIcon (IMG,/icons/image.xbm) .gif .jpg .xbm
    - AddIcon /icons/dir.xbm ^^DIRECTORY^^
    +

    + AddIcon (IMG,/icons/image.xbm) .gif .jpg .xbm
    + AddIcon /icons/dir.xbm ^^DIRECTORY^^
    AddIcon /icons/backup.xbm *~ -     +

    -

    AddIconByType +

    AddIconByType should be used in preference to AddIcon, when possible.

    -

    AddIconByEncoding Directive

    Description: - Icon to display next to files selected by MIME -content-encoding
    Syntax: - AddIconByEncoding - icon MIME-encoding [MIME-encoding] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +
    top

    AddIconByEncoding Directive

    Description: + Icon to display next to files selected by MIME +content-encoding
    Syntax: + AddIconByEncoding + icon MIME-encoding [MIME-encoding] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    This sets the icon to display next to files with FancyIndexing. Icon is either a (%-escaped) relative URL to the icon, or of the format (alttext,url) where @@ -290,16 +292,16 @@ content-encodingAddIconByEncoding /icons/compress.xbm x-compress -

    AddIconByType Directive

    Description: - Icon to display next to files selected by MIME -content-type
    Syntax: - AddIconByType - icon MIME-type [MIME-type] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +

    AddIconByEncoding /icons/compress.xbm x-compress

    +
    top

    AddIconByType Directive

    Description: + Icon to display next to files selected by MIME +content-type
    Syntax: + AddIconByType + icon MIME-type [MIME-type] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    This sets the icon to display next to files of type MIME-type for FancyIndexing. Icon is either a (%-escaped) relative URL to the icon, @@ -310,38 +312,38 @@ content-typeAddIconByType (IMG,/icons/image.xbm) image/* -

    DefaultIcon Directive

    Description: - Icon to display for files when no specific icon is -configured
    Syntax: - DefaultIcon url-path
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +

    AddIconByType (IMG,/icons/image.xbm) image/*

    +
    top

    DefaultIcon Directive

    Description: + Icon to display for files when no specific icon is +configured
    Syntax: + DefaultIcon url-path
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    The DefaultIcon directive sets the icon to display for files when no specific icon is known, for FancyIndexing. Url-path is a (%-escaped) relative URL to the icon. Examples:

    -
    DefaultIcon /icon/unknown.xbm
    -

    HeaderName Directive

    Description: - Name of the file that will be inserted at the top -of the index listing
    Syntax: - HeaderName filename
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +

    DefaultIcon /icon/unknown.xbm

    +
    top

    HeaderName Directive

    Description: + Name of the file that will be inserted at the top +of the index listing
    Syntax: + HeaderName filename
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    The HeaderName directive sets the name of the file that will be inserted at the top of the index listing. Filename is the name of the file to include.

    -

    Example

    +

    Example

    HeaderName HEADER.html -

    +

    -
    -

    Both HeaderName and ReadmeName now treat +

    +

    Both HeaderName and ReadmeName now treat Filename as a URI path relative to the one used to access the directory being indexed. Filename must resolve to a document with a major content type of @@ -350,31 +352,31 @@ HeaderName HEADER.html filename may refer to a CGI script if the script's actual file type (as opposed to its output) is marked as text/html such as with a directive like:

    -
    +

    AddType text/html .cgi -

    +

    Content negotiation - will be performed if the MultiViews Option is enabled. If + will be performed if the MultiViews Option is enabled. If filename resolves to a static text/html document (not a CGI script) and the Includes - option is enabled, the file + option is enabled, the file will be processed for server-side includes (see the - mod_include documentation).

    -
    + mod_include documentation).

    +

    If the file specified by HeaderName contains the beginnings of an HTML document (<HTML>, <HEAD>, etc) then you will probably want to set IndexOptions +SuppressHTMLPreamble, so that these tags are not repeated.

    -

    IndexIgnore Directive

    Description: - Adds to the list of files to hide when listing -a directory
    Syntax: - IndexIgnore file [file] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +
    top

    IndexIgnore Directive

    Description: + Adds to the list of files to hide when listing +a directory
    Syntax: + IndexIgnore file [file] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    The IndexIgnore directive adds to the list of files to hide when listing a directory. File is a file extension, partial filename, wildcard expression or full @@ -383,15 +385,15 @@ a directoryIndexIgnore README .htaccess *~ -

    IndexOptions Directive

    Description: - Various configuration settings for directory -indexing
    Syntax: - IndexOptions [+|-]option [[+|-]option] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +

    IndexIgnore README .htaccess *~

    +
    top

    IndexOptions Directive

    Description: + Various configuration settings for directory +indexing
    Syntax: + IndexOptions [+|-]option [[+|-]option] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    The IndexOptions directive specifies the behavior of the directory indexing. Option can be one of

    @@ -414,7 +416,7 @@ indexing -
    See the section on AddDescription for dangers +
    See the section on AddDescription for dangers inherent in truncating descriptions.
    FancyIndexing
    @@ -542,7 +544,7 @@ indexing If the directory actually contains a file specified by the - HeaderName + HeaderName directive, the module usually includes the contents of the file after a standard HTML preamble (<HTML>, <HEAD>, et cetera). The SuppressHTMLPreamble option disables @@ -611,23 +613,23 @@ indexing
    -foo-1.7
    -foo-1.7.2
    -foo-1.7.12
    -foo-1.8.2
    -foo-1.8.2a
    -foo-1.12
    -
    +

    +foo-1.7
    +foo-1.7.2
    +foo-1.7.12
    +foo-1.8.2
    +foo-1.8.2a
    +foo-1.12
    +

    If the number starts with a zero, then it is considered to be a fraction: -
    -foo-1.001
    -foo-1.002
    -foo-1.030
    +

    +foo-1.001
    +foo-1.002
    +foo-1.030
    foo-1.04 -

    +

    @@ -637,20 +639,20 @@ foo-1.04
    Apache 1.3.3 introduced some significant changes in the handling of IndexOptions directives. In - particular,
    -
    + particular,
    +
    • Multiple IndexOptions directives for a single directory are now merged together. The result of the example above will now be the equivalent of - IndexOptions FancyIndexing ScanHTMLTitles.
      • + IndexOptions FancyIndexing ScanHTMLTitles.
    • The addition of the incremental syntax (i.e., prefixing keywords with '+' or '-').
    -
    +
    Whenever a '+' or '-' prefixed keyword is encountered, it is applied to the current IndexOptions settings (which may have been inherited from an upper-level @@ -659,29 +661,29 @@ foo-1.04 incremental settings encountered so far. Consider the following example: -
    IndexOptions +ScanHTMLTitles -IconsAreLinks - FancyIndexing
    - IndexOptions +SuppressSize
    -
    +

    IndexOptions +ScanHTMLTitles -IconsAreLinks + FancyIndexing
    + IndexOptions +SuppressSize
    +

    The net effect is equivalent to - IndexOptions FancyIndexing +SuppressSize, + IndexOptions FancyIndexing +SuppressSize, because the unprefixed FancyIndexing discarded the incremental keywords before it, but allowed them to - start accumulating again afterward.
    -
    + start accumulating again afterward.
    +
    To unconditionally set the IndexOptions for a particular directory, clearing the inherited settings, specify keywords without any '+' or '-' prefixes.
    -

    IndexOrderDefault Directive

    Description: - Sets the default ordering of the directory index
    Syntax: - IndexOrderDefault -Ascending|Descending Name|Date|Size|Description
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +
    top

    IndexOrderDefault Directive

    Description: + Sets the default ordering of the directory index
    Syntax: + IndexOrderDefault +Ascending|Descending Name|Date|Size|Description
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    The IndexOrderDefault directive is used in combination with the FancyIndexing index option. By default, fancyindexed directory listings are @@ -701,23 +703,23 @@ Ascending|Descending Name|Date|Size|DescriptionSuppressColumnSorting index option; this will prevent the client from requesting the directory listing in a different order.

    -

    ReadmeName Directive

    Description: - Name of the file that will be inserted at the end -of the index listing
    Syntax: - ReadmeName filename
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_autoindex
    +
    top

    ReadmeName Directive

    Description: + Name of the file that will be inserted at the end +of the index listing
    Syntax: + ReadmeName filename
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_autoindex

    The ReadmeName directive sets the name of the file that will be appended to the end of the index listing. Filename is the name of the file to include, and is taken to be relative to the location being indexed.

    -

    Example

    +

    Example

    ReadmeName FOOTER.html -

    +

    -

    See also HeaderName, where this behavior +

    See also HeaderName, where this behavior is described in greater detail.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_autoindex.html.ja.jis b/docs/manual/mod/mod_autoindex.html.ja.jis index b1e31068b5..e50f1b90fc 100644 --- a/docs/manual/mod/mod_autoindex.html.ja.jis +++ b/docs/manual/mod/mod_autoindex.html.ja.jis @@ -1,61 +1,63 @@ -mod_autoindex - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mod_autoindex

    $B@bL@(B: - Unix $B$N(B ls $B%3%^%s%I$d(B + -->mod_autoindex - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mod_autoindex

    $B@bL@(B: + Unix $B$N(B ls $B%3%^%s%I$d(B Win32 $B$N(B dir $B%7%'%k%3%^%s%I$K;w$?(B - $B%G(B$B%#%l%/%H%j%$%s%G%C%/%9$r@8@.$9$k(B
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<(B$B%k<1JL;R(B: - autoindex_module

    $B35MW(B

    + $B%G%#%l%/%H%j%$%s%G%C%/%9$r@8@.$9$k(B
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k<1JL;R(B: + autoindex_module

    $B35MW(B

    $B%G%#%l%/%H%j$N%$%s%G%C%/%9$OFs$D$N>pJs8;$N$&$A$N(B $B0l$D$+$i@8@.$G$-$^$9(B:

    • $BIaDL$O(B index.html $B$H8F$P$l$k(B $B%f!<%6$K$h$C$F=q$+$l$?%U%!%$%k!#(B - DirectoryIndex - $B%G%#(B$B%l%/%F%#%V$G$3$N%U%!%$%kL>$r@_Dj$7$^$9!#(B - $B$3$l$O(B mod_dir $B$G@)8f$5$l$^$9!#(B
      • + DirectoryIndex + $B%G%#%l%/%F%#%V$G$3$N%U%!%$%kL>$r@_Dj$7$^$9!#(B + $B$3$l$O(B mod_dir $B$G@)8f$5$l$^$9!#(B
    • $B$b$7$/$O!"%5!<%P$K$h$C$F@8@.$5$l$?0lMw!#(B $B$=$NB>$N%G%#%l%/%F%#%V$G$3$N0lMw$N=q<0$r@)8f$7$^$9!#(B - AddIcon, AddIconByEncoding $B$H(B - AddIconByType + AddIcon, AddIconByEncoding $B$H(B + AddIconByType $B$r;H$&$3$H$G!"MM!9$J%U%!%$%k%?%$%W$KBP$7$F%"%$%3%s0lMw$r(B $B%;%C%H$7$^$9!#$D$^$j!"%j%9%H$5$l$?%U%!%$%kKh$K!"(B - $B%U%!%$%k$K%^%C%A$7$?0lHV:G=i$N%"%$%3%s$,(B$BI=<($5$l$^$9!#(B - $B$3$l$i$O(B mod_autoindex $B$G@)8f$5$l$^$9!#(B
      • + $B%U%!%$%k$K%^%C%A$7$?0lHV:G=i$N%"%$%3%s$,I=<($5$l$^$9!#(B + $B$3$l$i$O(B mod_autoindex $B$G@)8f$5$l$^$9!#(B

    $BK>$`$J$i$P!"<+F0%$%s%G%C%/%9@8@.$r40A4$K=|5n(B ($B$"$k$$$OCV49(B) $B$G$-$k$h$&$K!"$3$NFs$D$N5!G=$OJ,N%$5$l$F$$$^$9!#(B

    $B<+F0%$%s%G%C%/%9@8@.$O(B Optioins +Indexes $B$r;H$&$3$H$GM-8z$K$J$j$^$9!#>\:Y$K$D$$$F$O!"(B - Options + Options $B%G%#%l%/%F%#%V$r$4Mw2<$5$$!#(B

    -

    $B$b$7(B FancyIndexing +

    $B$b$7(B FancyIndexing $B%*%W%7%g%s$,(B - IndexOptions + IndexOptions $B%G%#%l%/%F%#%V$KM?$($i$l$F$$$k$J$i$P!"(B $BNs$N@hF,$OI=<($N=gHV$r@)8f$9$k%j%s%/$K$J$j$^$9!#(B $B@hF,$N%j%s%/$rA*Br$9$k$H!"0lMw$O:F@8@.$5$l$F(B $B$=$NNs$NCM$G%=!<%H$5$l$^$9!#(B $BF1$8@hF,$rB3$1$FA*Br$9$k$H!"8r8_$K>:=g$H9_=g$H$K$J$j$^$9!#(B $B$3$l$i$NNs$N@hF,$N%j%s%/$O!"(B - IndexOptions + IndexOptions $B%G%#%l%/%F%#%V$N(B SuppressColumnSorting $B%*%W%7%g%s$G>C$9$3$H$,$G$-$^$9!#(B

    -

    "Size" $B$G%=!<%H$7$?>l9g$O!"MQ$$$i$l$k$N(B$B$O(B +

    "Size" $B$G%=!<%H$7$?>l9g$O!"MQ$$$i$l$k$N$O(B $B$B%U%!%$%k$N%5%$%:$G$"$C$F!"(B $BI=<($NCM$G$O$J$$$3$H$KCm0U$7$F$/$@$5$$(B - $B$?$H$(N>J}$H$b$,(B "1K" $B$HI=<($5$l$F$$$?$H$7$F$b!"(B 1010 $B%P%$%H$N%U%!%$%k$OI,$:(B 1011 $B%P%$%H$N%U%!%$%k$h$j$bA0(B ($B>:=g$N>l9g(B) $B$KI=<($5$l$^$9!#(B

    -

    $B%G%#%l%/%F%#%V(B

    Autoindex $B%j%/%(%9%H%/%(%j!<0z?t(B

    +
    top

    Autoindex $B%j%/%(%9%H%/%(%j!<0z?t(B

    Apache 2.0.23 $B$G!"(B $B%3%i%`%=!<%H$N$?$a$K%/%(%j!<0z?t$r:FJT@.$7$F!"(B @@ -75,19 +77,19 @@

  • C=N $B$O!"%U%!%$%kL>$G%=!<%H$7$^$9!#(B
  • C=M $B$O!"99?7F|;~!"(B - $B%G%#%l(B$B%/%H%j!"%U%!%$%kL>$N=g$G%=!<%H$7$^$9!#(B
    • + $B%G%#%l%/%H%j!"%U%!%$%kL>$N=g$G%=!<%H$7$^$9!#(B
  • C=S $B$O!"%5%$%:!"(B $B%G%#%l%/%H%j!"%U%!%$%kL>$N=g$G%=!<%H$7$^$9!#(B
  • C=D $B$O!"@bL@!"(B - $B%G%#%l%/%H%j!"%U%!%$%kL>$N=g$G%=!<%H$7$^$9!#(B
    -  
    • + $B%G%#%l%/%H%j!"%U%!%$%kL>$N=g$G%=!<%H$7$^$9!#(B
    + ?
  • O=A $B$O!">:=g$GI=$r%=!<%H$7$^$9!#(B
    • -
  • O=D $B$O!"9_=g$GI=$r%=!<%H$7$^$9!#(B
    -  
    • +
  • O=D $B$O!"9_=g$GI=$r%=!<%H$7$^$9!#(B
    + ?
  • F=0 $B$O!"C1=c$JI=$N=q<0$K$7$^$9!#(B (FancyIndex $B$G$O$"$j$^$;$s!#(B)
    • @@ -96,22 +98,22 @@ $BI=<($NI=$N=q<0$K$7$^$9!#(B
  • F=2 $B$O!"I=$r(B HTML - $B$N%F!<%V%k$r;H$C$?(B FancyIndex $B$N=q<0$K$7$^$9!#(B
    -  
    • + $B$N%F!<%V%k$r;H$C$?(B FancyIndex $B$N=q<0$K$7$^$9!#(B
    + ?
  • V=0 $B$O!"%P!<%8%g%s$K$h$k%=!<%H$rL58z$K$7$^$9!#(B
  • V=1 - $B$O!"%P!<%8%g%s$K$h$k%=!<%H$rM-8z$K$7$^$9!#(B
    -  
    • + $B$O!"%P!<%8%g%s$K$h$k%=!<%H$rM-8z$K$7$^$9!#(B
    + ?
  • P=$B%Q%?!<%s(B $B$O!"M?$($i$l$?(B$B%Q%?!<%s(B $B$KE,9g$7$?%U%!%$%k$N$_$rI=<($7$^$9!#(B
    • -

    "P ($B%Q%?!<(B$B%s$N(B P)" $B%/%(%j!<0z?t$O!"(B +

    "P ($B%Q%?!<%s$N(B P)" $B%/%(%j!<0z?t$O!"(B $BDL>o$N(B IndexIgnore $B%G%#%l%/%F%#%V$,=hM}$5$l$?(B$B8e(B$B$K8!::$5$l!"(B $B%U%!%$%kL>A4$F$,!"B>$N(B autoindex @@ -129,40 +131,40 @@ $B0z?t$,A4$F2r -

    -<FORM METHOD="GET">
    -  Show me a <SELECT NAME="F">
    -    <OPTION VALUE="0"> Plain list
    -    <OPTION VALUE="1" SELECTED> Fancy list
    -    <OPTION VALUE="2"> Table list
    -  </SELECT>
    -  Sorted by <SELECT NAME="C">
    -    <OPTION VALUE="N" SELECTED> Name
    -    <OPTION VALUE="M"> Date Modified
    -    <OPTION VALUE="S"> Size
    -    <OPTION VALUE="D"> Description
    -  </SELECT>
    -  <SELECT NAME="O">
    -    <OPTION VALUE="A" SELECTED> Ascending
    -    <OPTION VALUE="D"> Descending
    -  </SELECT>
    -  <SELECT NAME="V">
    -    <OPTION VALUE="0" SELECTED> in Normal order
    -    <OPTION VALUE="1"> in Version order
    -  </SELECT>
    -  Matching <INPUT TYPE="text" NAME="P" VALUE="*">
    -  <INPUT TYPE="submit" NAME="X" VALUE="Go">
    +

    +<FORM METHOD="GET">
    +??Show me a <SELECT NAME="F">
    +????<OPTION VALUE="0"> Plain list
    +????<OPTION VALUE="1" SELECTED> Fancy list
    +????<OPTION VALUE="2"> Table list
    +??</SELECT>
    +??Sorted by <SELECT NAME="C">
    +????<OPTION VALUE="N" SELECTED> Name
    +????<OPTION VALUE="M"> Date Modified
    +????<OPTION VALUE="S"> Size
    +????<OPTION VALUE="D"> Description
    +??</SELECT>
    +??<SELECT NAME="O">
    +????<OPTION VALUE="A" SELECTED> Ascending
    +????<OPTION VALUE="D"> Descending
    +??</SELECT>
    +??<SELECT NAME="V">
    +????<OPTION VALUE="0" SELECTED> in Normal order
    +????<OPTION VALUE="1"> in Version order
    +??</SELECT>
    +??Matching <INPUT TYPE="text" NAME="P" VALUE="*">
    +??<INPUT TYPE="submit" NAME="X" VALUE="Go">
    </FORM> -

    - -

    AddAlt $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%"%$%3%s$NBe$o$j$K(B -$BI=<($5$l$k!"%U%!%$%kL>$GA*Br$5$l$?BeBX%F%-%9%H(B
    $B9=J8(B: - AddAlt string file [file] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +

    + +
    top

    AddAlt $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%"%$%3%s$NBe$o$j$K(B +$BI=<($5$l$k!"%U%!%$%kL>$GA*Br$5$l$?BeBX%F%-%9%H(B
    $B9=J8(B: + AddAlt string file [file] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    AddAlt $B$O!"(BFancyIndexing $B$K$*$$$F!"%"%$%3%s$NBe$o$j$KI=<($9$kBeBX%F%-%9%H$rDs6!$7$^$9!#(B File $B$O!"@bL@$9$k%U%!%$%k$N%U%!%$%k3HD%;R!"(B @@ -174,19 +176,19 @@ $B%"%$%3%s$N

    $BNc(B:

    -
    - AddAlt "PDF" *.pdf
    +

    + AddAlt "PDF" *.pdf
    AddAlt "Compressed" *.gz *.zip *.Z -

    -

    AddAltByEncoding $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%"%$%3%s$NBe$o$j$KI=<($5$l$k!"(BMIME $BId9f2=J}K!$GA*Br$5$l$?(B -$BBeBX%F%-%9%H(B
    $B9=J8(B: - AddAltByEncoding string MIME-encoding -[MIME-encoding] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +

    +
    top

    AddAltByEncoding $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%"%$%3%s$NBe$o$j$KI=<($5$l$k!"(BMIME $BId9f2=J}K!$GA*Br$5$l$?(B +$BBeBX%F%-%9%H(B
    $B9=J8(B: + AddAltByEncoding string MIME-encoding +[MIME-encoding] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    AddAltByEncoding $B$O!"(B FancyIndexing $B$K$*$$$F!"%"%$%3%s$NBe$o$j$KI=<($9$kBeBXJ8;zNs$rDs6!$7$^$9!#(B @@ -199,18 +201,18 @@ $B%"%$%3%s$N

    $BNc(B:

    -
    +

    AddAltByEncoding "gzip" x-gzip -

    -

    AddAltByType $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%"%$%3%s$NBe$o$j$K(B -$BI=<($5$l$k!"(BMIME $B%?%$%W$GA*Br$5$l$?BeBX%F%-%9%H(B
    $B9=J8(B: - AddAltByType string - MIME-type [MIME-type] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +

    +
    top

    AddAltByType $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%"%$%3%s$NBe$o$j$K(B +$BI=<($5$l$k!"(BMIME $B%?%$%W$GA*Br$5$l$?BeBX%F%-%9%H(B
    $B9=J8(B: + AddAltByType string + MIME-type [MIME-type] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    AddAltByType $B$O!"(B FancyIndexing $B$K$*$$$F!"%"%$%3%s$NBe$o$j$KI=<($9$kBeBXJ8;zNs$r@_Dj$7$^$9!#(B @@ -223,17 +225,17 @@ $B%"%$%3%s$N

    $BNc(B:

    -
    +

    AddAltByType "TXT" text/plain -

    -

    AddDescription $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%U%!%$%k$KBP$7$FI=<($9$k@bL@(B
    $B9=J8(B: - AddDescription - string file [file] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +

    +
    top

    AddDescription $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%U%!%$%k$KBP$7$FI=<($9$k@bL@(B
    $B9=J8(B: + AddDescription + string file [file] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    FancyIndexing $B$K$*$$$F!"%U%!%$%k$KBP$7$FI=<($9$k@bL@$r@_Dj$7$^$9!#(B File $B$O@bL@$9$k%U%!%$%k$N%U%!%$%k3HD%;R!"(B @@ -245,15 +247,15 @@ $B%"%$%3%s$N -

    AddDescription "The planet Mars" - /web/pics/mars.gif
    +

    AddDescription "The planet Mars" + /web/pics/mars.gif

    $BDL>o$N%G%U%)%k%H$N@bL@NN0h$O(B 23 $B%P%$%H$NI}$G$9!#(B - IndexOptions SuppressIcon + IndexOptions?SuppressIcon $B%*%W%7%g%s$G(B 6 $B%P%$%HDI2C!"(B - IndexOptions SuppressSize + IndexOptions?SuppressSize $B%*%W%7%g%s$G(B 7 $B%P%$%HDI2C!"(B - IndexOptions SuppressLastModified + IndexOptions?SuppressLastModified $B%*%W%7%g%s$G(B 19 $B%P%$%HDI2C$5$l$^$9!#(B $B$G$9$+$i!"%G%U%)%k%H$N@bL@%3%i%`$N:GBgI}$O(B 55 $B%P%$%H$K$J$j$^$9!#(B

    @@ -262,25 +264,25 @@ $B@bL@$,L5@)8BD9$G$b$h$$$h$&$K$9$k$?$a$N>\:Y$K4X$7$F$O!"(B DescriptionWidth $B$H$$$&(B - IndexOptions + IndexOptions $B$N%-!<%o!<%I$r$4Mw2<$5$$!#(B

    -

    $B7Y9p(B

    +

    $B7Y9p(B

    AddDescription $B$GDj5A$5$l$?@bL@%F%-%9%H$O!"%?%0$dJ8;zNs$H$$$C$?(B HTML $B%^!<%/%"%C%W$r4^$`$3$H$,$G$-$^$9!#(B $B$b$7!"@bL@%3%i%`$NI}$K$h$C$F%?%0IU$1$5$l$?MWAG$,4]$a9~$^$l$?(B ($BB@;z$N8l6g$N:G8e$,@Z$l$k$H$$$C$?(B) $B>l9g!"(B $B=PNO7k2L$O!"%G%#%l%/%H%j0lMw$N;D$j$NItJ,$K1F6A$rM?$($k$G$7$g$&!#(B

    -
    -

    AddIcon $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%U%!%$%k$KI=<($9$k%"%$%3%s$rL>A0$GA*Br(B
    $B9=J8(B: - AddIcon icon - name [name] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +
    +
    top

    AddIcon $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%U%!%$%k$KI=<($9$k%"%$%3%s$rL>A0$GA*Br(B
    $B9=J8(B: + AddIcon icon + name [name] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    FancyIndexing $B$K$*$$$F!"(B name $B$G=*$o$k%U%!%$%k$NNY$KI=<($9$k%"%$%3%s$r@_Dj$7$^$9!#(B @@ -295,26 +297,26 @@ $B%U%!%$%k3HD%;R$+!"%o%$%k%I%+!<%II=8=$+!"%U%!%$%kL>$N0lIt$+(B $B40A4$J%U%!%$%kL>$G$9!#Nc(B:

    -
    - AddIcon (IMG,/icons/image.xbm) .gif .jpg .xbm
    - AddIcon /icons/dir.xbm ^^DIRECTORY^^
    +

    + AddIcon (IMG,/icons/image.xbm) .gif .jpg .xbm
    + AddIcon /icons/dir.xbm ^^DIRECTORY^^
    AddIcon /icons/backup.xbm *~ -

    +

    $B$b$72DG=$J$i!"(B AddIcon $B$h$j(B - AddIconByType + AddIconByType $B$rM%@hE*$K;H$&$Y$-$G$7$g$&!#(B

    -

    AddIconByEncoding $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%U%!%$%k$KI=<($9$k%"%$%3%s$r(B MIME -$BId9f2=J}K!$GA*Br(B
    $B9=J8(B: - AddIconByEncoding - icon MIME-encoding [MIME-encoding] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +
    top

    AddIconByEncoding $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%U%!%$%k$KI=<($9$k%"%$%3%s$r(B MIME +$BId9f2=J}K!$GA*Br(B
    $B9=J8(B: + AddIconByEncoding + icon MIME-encoding [MIME-encoding] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    FancyIndexing $B$K$*$$$F!"%U%!%$%k$NNY$KI=<($9$k%"%$%3%s$r@_Dj$7$^$9!#(B Icon $B$O!"(B(% $B$G%(%9%1!<%W$5$l$?(B) $B%"%$%3%s$X$NAjBP(B URL @@ -326,16 +328,16 @@

    MIME-encoding $B$O!"MW5a$5$l$?%(%s%3!<%I$K3:Ev$9$k(B $B%o%$%k%I%+!<%II=8=$G$9!#Nc(B:

    -
    AddIconByEncoding /icons/compress.xbm x-compress
    -

    AddIconByType $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%U%!%$%k$NNY$KI=<($9$k%"%$%3%s$r(B -MIME $B%?%$%W$K$h$C$FA*Br(B
    $B9=J8(B: - AddIconByType - icon MIME-type [MIME-type] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +

    AddIconByEncoding /icons/compress.xbm x-compress

    +
    top

    AddIconByType $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%U%!%$%k$NNY$KI=<($9$k%"%$%3%s$r(B +MIME $B%?%$%W$K$h$C$FA*Br(B
    $B9=J8(B: + AddIconByType + icon MIME-type [MIME-type] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    FancyIndexing $B$K$*$$$F!"%U%!%$%k$NNY$KI=<($9$k%"%$%3%s$r@_Dj$7$^$9!#(B Icon $B$O!"(B(% $B$G%(%9%1!<%W$5$l$?(B) $B%"%$%3%s$X$NAjBP(B URL @@ -347,39 +349,39 @@ MIME $B%?%$%W$K$h$C$FA*Br(B -

    AddIconByType (IMG,/icons/image.xbm) image/*
    -

    DefaultIcon $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $BFCDj$N%"%$%3%s$,2?$b@_Dj$5$l$F$$$J$$;~$K(B -$B%U%!%$%k$KI=<($9$k%"%$%3%s(B
    $B9=J8(B: - DefaultIcon url-path
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +

    AddIconByType (IMG,/icons/image.xbm) image/*

    +
    top

    DefaultIcon $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $BFCDj$N%"%$%3%s$,2?$b@_Dj$5$l$F$$$J$$;~$K(B +$B%U%!%$%k$KI=<($9$k%"%$%3%s(B
    $B9=J8(B: + DefaultIcon url-path
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    FancyIndexing $B$K$*$$$F!"(B $BFCDj$N%"%$%3%s$,$J$$>l9g$K%U%!%$%k$KI=<($9$k%"%$%3%s$r@_Dj$7$^$9!#(B Url-path $B$O!"(B(% $B$G%(%9%1!<%W$5$l$?(B) $B%"%$%3%s$X$NAjBP(B URL $B$G$9!#Nc(B:

    -
    DefaultIcon /icon/unknown.xbm
    -

    HeaderName $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - -$B%$%s%G%C%/%90lMw$N@hF,$KA^F~$5$l$k%U%!%$%k$NL>A0(B
    $B9=J8(B: - HeaderName filename
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +

    DefaultIcon /icon/unknown.xbm

    +
    top

    HeaderName $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + +$B%$%s%G%C%/%90lMw$N@hF,$KA^F~$5$l$k%U%!%$%k$NL>A0(B
    $B9=J8(B: + HeaderName filename
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    HeaderName $B%G%#%l%/%F%#%V$O!"(B $B%$%s%G%C%/%90lMw$N@hF,$KA^F~$9$k%U%!%$%k$NL>A0$r@_Dj$7$^$9!#(B Filename $B$OA0$G$9!#(B

    -

    Example

    +

    Example

    HeaderName HEADER.html -

    -
    -

    HeaderName $B$b(B ReadmeName +

    +
    +

    HeaderName $B$b(B ReadmeName $B$bN>J}$H$b8=:_$O!"(Bfilename $B$r%$%s%G%C%/%9$5$l$F$$$k%G%#%l%/%H%j$KMQ$$$i$l$?(B URI $B$KBP$9$kAjBP(B URI $B%Q%9$H$7$F07$$$^$9!#(B @@ -395,20 +397,20 @@ HeaderName HEADER.html filename $B$O(B CGI $B%9%/%j%W%H$r;2>H$9$k$+$bCN$l$J$$!"(B $B$H$$$&$3$H$r0UL#$7$^$9(B:

    -
    +

    AddType text/html .cgi -

    -

    MultiViews Option $B$,M-8z$K$J$C$F$$$k>l9g$O!"(B +

    +

    MultiViews Option $B$,M-8z$K$J$C$F$$$k>l9g$O!"(B $B%3%s%F%s%H%M%4%7%(!<%7%g%s(B $B$,9T$o$l$^$9!#(B $B$b$7(B filename $B$,(B (CGI $B%9%/%j%W%H$G$J$$(B) $B@EE*$J(B text/html $B%I%-%e%a%s%H$G2r7h$5$l!"(B Includes - option + option $B%*%W%7%g%s$,M-8z$K$J$C$F$$$k>l9g$O!"(B $B%U%!%$%k$O%5!<%P!<%5%$%I%$%s%/%k!<%I$G=hM}$5$l$^$9(B - (mod_include $B%I%-%e%a%s%H$r;2>H$7$F2<$5$$(B)$B!#(B

    -
    + (mod_include $B%I%-%e%a%s%H$r;2>H$7$F2<$5$$(B)$B!#(B

    +

    $B$b$7(B HeaderName $B$G;XDj$5$l$?%U%!%$(B$B%k$,(B HTML $B%I%-%e%a%s%H$N3+;OItJ,(B (<HTML>, <HEAD>, @@ -416,14 +418,14 @@ HeaderName HEADER.html IndexOptions +SuppressHTMLPreamble $B$r@_Dj$7$F!"$3$l$i$N%?%0$,7+$jJV$5$l$J$$$h$&$K$7$?$$$H;W$&$G$7$g$&!#(B

    -

    IndexIgnore $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%G%#%l%/%H%j0lMw$r9T$J$&:]$KL5;k$9$Y$-(B -$B%U%!%$%k%j%9%H$KDI2C(B
    $B9=J8(B: - IndexIgnore file [file] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +
    top

    IndexIgnore $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%G%#%l%/%H%j0lMw$r9T$J$&:]$KL5;k$9$Y$-(B +$B%U%!%$%k%j%9%H$KDI2C(B
    $B9=J8(B: + IndexIgnore file [file] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    IndexIgnore $B%G%#%l%/%F%#%V$O!"(B $B%G%#%l%/%H%j$N0lMw$r9T$&:]$KL5;k$9$Y$-%U%!%$%k%j%9%H$KDI2C$7$^$9!#(B File $B$O!"L5;k$9$k%U%!%$%kL>$N%U%!%$%k3HD%;R$+!"%U%!%$%kL>$N0lIt$+!"(B @@ -432,15 +434,15 @@ HeaderName HEADER.html $BCV49$O9T$o$l$^$;$s!#%G%U%)%k%H$G$O%j%9%H$K$O(B `.' $B$,4^$^$l$F$$$^$9!#Nc(B:

    -
    IndexIgnore README .htaccess *~
    -

    IndexOptions $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%G%#%l%/%H%j%$%s%G%C%/%9$NMM!9$J@_Dj9`L\(B -
    $B9=J8(B: - IndexOptions [+|-]option [[+|-]option] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +

    IndexIgnore README .htaccess *~

    +
    top

    IndexOptions $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%G%#%l%/%H%j%$%s%G%C%/%9$NMM!9$J@_Dj9`L\(B +
    $B9=J8(B: + IndexOptions [+|-]option [[+|-]option] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    IndexOptions $B$O!"%G%#%l%/%H%j%$%s%G%C%/%9$N5sF0$r;XDj$7$^$9!#(B option $B$O @@ -462,7 +464,7 @@ HeaderName HEADER.html $B$O!":GD9$N@bL@$K9g$o$;$FI,MW$JD9$5$^$G%3%i%`$r1d$P$7$^$9!#(B

    $B@bL@$r4]$a9~$s$@>l9gFCM-$N4m81$K$D$$$F$O(B - AddDescription + AddDescription $B%;%/%7%g%s$r$*FI$_2<$5$$!#(B
    FancyIndexing
    @@ -593,7 +595,7 @@ HeaderName HEADER.html (Apache 1.3 $B0J9_(B)
    $BDL>o!"(B - HeaderName + HeaderName $B%G%#%l%/%F%#%V$G;XDj$7$?%U%!%$%k$r(B $B%G%#%l%/%H%j$,$BEy(B) $B$N8e$K!"(B @@ -672,22 +674,22 @@ HeaderName HEADER.html $B$=$l0J30$N!"@bL@$dL>A0Cf$N?t$H$J$kItJ,J8;zNs$O(B $B$=$N?tCM$GHf3S$5$l$^$9!#Nc$($P(B: -
    -foo-1.7
    -foo-1.7.2
    -foo-1.7.12
    -foo-1.8.2
    -foo-1.8.2a
    -foo-1.12
    -
    +

    +foo-1.7
    +foo-1.7.2
    +foo-1.7.12
    +foo-1.8.2
    +foo-1.8.2a
    +foo-1.12
    +

    $BHV9f$,(B 0 $B$+$i;O$^$k>l9g$O!"C
    -foo-1.001
    -foo-1.002
    -foo-1.030
    +

    +foo-1.001
    +foo-1.002
    +foo-1.030
    foo-1.04 -

    +

    @@ -698,8 +700,8 @@ foo-1.04 Apache 1.3.3 $B$G$O!"(B IndexOptions $B%G%#%l%/%F%#%V$N07$$$G4v$D$+$NBg$-$JJQ2=$,F3F~$5$l$^$7$?!#(B - $BFC$K!"(B
    -
    + $BFC$K!"(B
    +
      @@ -707,14 +709,14 @@ foo-1.04 IndexOptions $B%G%#%l%/%F%#%V$O!"8=:_$G$O0l$D$K%^!<%8$5$l$^$9!#(B $B>e$NNc$N7k2L$O!"(B - IndexOptions FancyIndexing ScanHTMLTitles + IndexOptions?FancyIndexing?ScanHTMLTitles $B$HF10l$K$J$j$^$9!#(B
    • $BA}8:9=J8(B ($B$9$J$o$A(B$B!"(B'+' $B$d(B '-' $B$N@\F,<-$,IU$/%-!<%o!<%I(B) $B$NDI2C!#(B
    -
    +
    '+' $B$d(B '-' $B@\F,<-$NIU$$$?%-!<%o!<%I$K=P2q$&$H$=$l$O!"(B $B$=$N;~E@$G$N(B IndexOptions $B$N@_Dj(B ($B$3$l$O>eN.$N%G%#%l%/%H%j$rC5n$5$l$^$9!#
    IndexOptions +ScanHTMLTitles -IconsAreLinks - FancyIndexing
    - IndexOptions +SuppressSize
    -
    +

    IndexOptions +ScanHTMLTitles -IconsAreLinks + FancyIndexing
    + IndexOptions +SuppressSize
    +

    $BCf?H$N8z2L$O(B - IndexOptions FancyIndexing +SuppressSize + IndexOptions?FancyIndexing?+SuppressSize $B$HF10l$G$9!#(B $B@\F,<-$NIU$+$J$$(B FancyIndexing $B$G$=$l0JA0$NA}8:%-!<%o!<%I$rL58z$K$5$l$F!"(B - $B$=$N8e$NN_@Q$,;O$^$k$+$i$G$9!#(B
    -
    + $B$=$N8e$NN_@Q$,;O$^$k$+$i$G$9!#(B
    +
    $BL5>r7o$K(B IndexOptions $B$r$"$k%G%#%l%/%H%j$G@_Dj$9$k$3$H$K$h$C$F(B $B7Q>5$7$?@_Dj$r>C5n$7$F!"(B'+' $B$d(B '-' @@ -741,15 +743,15 @@ foo-1.04
    -

    IndexOrderDefault $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - -$B%G%#%l%/%H%j%$%s%G%C%/%9$NI8=`$N=gHVIU$1$r@_Dj(B
    $B9=J8(B: - IndexOrderDefault -Ascending|Descending Name|Date|Size|Description
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +
    top

    IndexOrderDefault $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + +$B%G%#%l%/%H%j%$%s%G%C%/%9$NI8=`$N=gHVIU$1$r@_Dj(B
    $B9=J8(B: + IndexOrderDefault +Ascending|Descending Name|Date|Size|Description
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    IndexOrderDefault $B%G%#%l%/%F%#%V$O(B FancyIndexing $B%$%s%G%C%/%9%*%W%7%g%s$HJ;$;$FMQ$$$l$l$^$9!#(B @@ -771,22 +773,22 @@ Ascending|Descending Name|Date|Size|Description -

    ReadmeName $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%$%s%G%C%/%90lMw$N:G8e$KA^F~$5$l$k%U%!%$%k$NL>A0(B
    $B9=J8(B: - ReadmeName filename
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_autoindex
    +
    top

    ReadmeName $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%$%s%G%C%/%90lMw$N:G8e$KA^F~$5$l$k%U%!%$%k$NL>A0(B
    $B9=J8(B: + ReadmeName filename
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_autoindex

    ReadmeName $B%G%#%l%/%F%#%V$O!"(B $B%$%s%G%C%/%9$N=*$o$j$KIU$12C$($i$l$k%U%!%$%k$NL>A0$r@_Dj$7$^$9!#(B filename $B$OA^F~$9$k%U%!%$%k$NL>A0$G!"(B $B0lMw$N9T$o$l$F$$$k0LCV$+$iAjBPE*$J$b$N$H$7$F2r -

    $BNc(B

    +

    $BNc(B

    ReadmeName FOOTER.html -

    +

    -

    $B$h$j>\:Y$K$^$G$3$N5sF0$K$D$$$F5-=R$7$F$$$k(B HeaderName +

    $B$h$j>\:Y$K$^$G$3$N5sF0$K$D$$$F5-=R$7$F$$$k(B HeaderName $B$b$4Mw2<$5$$!#(B

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_cache.html.en b/docs/manual/mod/mod_cache.html.en index 37248c8c99..caf5713a20 100644 --- a/docs/manual/mod/mod_cache.html.en +++ b/docs/manual/mod/mod_cache.html.en @@ -1,91 +1,93 @@ -mod_cache - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_cache

    Description: - Content cache keyed to URIs.
    Status: - Experimental
    Module Identifier: - cache_module

    Summary

    -
    + -->mod_cache - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_cache

    Description: + Content cache keyed to URIs.
    Status: + Experimental
    Module Identifier: + cache_module

    Summary

    +
    This module is experimental. Documentation is still under development... -
    +

    mod_cache implements an RFC 2616 compliant HTTP content cache that can be used to cache either local or proxied content. mod_cache requires the services of one or more storage management modules. Two storage management modules are included in the base Apache distribution:

    -
    mod_disk_cache
    -
    implements a disk based storage manager for use with mod_proxy
    -
    mod_mem_cache
    +
    mod_disk_cache
    +
    implements a disk based storage manager for use with mod_proxy
    +
    mod_mem_cache
    implements an in-memory based storage manager. mod_mem_cache can be configured to operate in two modes: caching open file - descriptors or caching objects in heap storage. mod_mem_cache + descriptors or caching objects in heap storage. mod_mem_cache is most useful when used to cache locally generated content or to cache backend server content for mod_proxy configured for ProxyPass (aka reverse proxy)

    Content stored and retrived keyed to the URL. Content with access protections is not cached.

    -

    Directives

    Related Modules and Directives

    -
    Related Modules

    mod_disk_cache
    mod_mem_cache
    		Related Directives

    CacheRoot
    CacheSize
    CacheGcInterval
    CacheDirLevels
    CacheDirLength
    CacheExpiryCheck
    CacheMinFileSize
    CacheMaxFileSize
    CacheTimeMargin
    CacheGcDaily
    CacheGcUnused
    CacheGcClean
    CacheGcMemUsage
    MCacheSize
    MCacheMaxObjectCount
    MCacheMinObjectSize
    MCacheMaxObjectSize
    MCacheRemovalAlgorithm
    -

    Sample Configuration

    -

    Sample httpd.conf

    -#
    -# Sample Cache Configuration
    -#
    -LoadModule cache_module modules/mod_cache.so
    -<IfModule mod_cache.c>
    -
    -#LoadModule disk_cache_module modules/mod_disk_cache.so
    - <IfModule mod_disk_cache.c>
    - CacheRoot c:/cacheroot
    - CacheSize 256
    - CacheEnable disk /
    - CacheDirLevels 5
    - CacheDirLength 3
    - </IfModule>
    -

    - LoadModule mem_cache_module modules/mod_mem_cache.so
    - <IfModule mod_mem_cache.c>
    - MCacheEnable mem /
    - MCacheSize 4096
    - MCacheMaxObjectCount 100
    - MCacheMinObjectSize 1
    - MCacheMaxObjectSize 2048
    - </IfModule>
    -

    -</IfModule>
    -
    -

    CacheDefaultExpire Directive

    Description: -
    Syntax: - CacheDefaultExpire seconds
    Default: - CacheDefaultExpire 3600 (one hour)
    Context: - server config
    Status: - Experimental
    Module: - mod_cache
    +
    top

    Related Modules and Directives

    +
    Related ModulesRelated Directives
    +
    top

    Sample Configuration

    +

    Sample httpd.conf

    +#
    +# Sample Cache Configuration
    +#
    +LoadModule cache_module modules/mod_cache.so
    +<IfModule mod_cache.c>
    +
    +#LoadModule disk_cache_module modules/mod_disk_cache.so
    + <IfModule mod_disk_cache.c>
    + CacheRoot c:/cacheroot
    + CacheSize 256
    + CacheEnable disk /
    + CacheDirLevels 5
    + CacheDirLength 3
    + </IfModule>
    +
    + LoadModule mem_cache_module modules/mod_mem_cache.so
    + <IfModule mod_mem_cache.c>
    + MCacheEnable mem /
    + MCacheSize 4096
    + MCacheMaxObjectCount 100
    + MCacheMinObjectSize 1
    + MCacheMaxObjectSize 2048
    + </IfModule>
    +
    +</IfModule>
    +

    +
    top

    CacheDefaultExpire Directive

    Description: +
    Syntax: + CacheDefaultExpire seconds
    Default: + CacheDefaultExpire 3600 (one hour)
    Context: + server config
    Status: + Experimental
    Module: + mod_cache

    The default time in seconds to cache a document if the page does not have an expiry date in the Expires field.

    -
    +

    CacheDefaultExpire 86400 -

    -

    CacheDisable Directive

    Description: - Disable caching of specified URLs by specified storage manager
    Syntax: - CacheDisable cache_type url-string
    Context: - server config
    Status: - Experimental
    Module: - mod_cache
    +

    +
    top

    CacheDisable Directive

    Description: + Disable caching of specified URLs by specified storage manager
    Syntax: + CacheDisable cache_type url-string
    Context: + server config
    Status: + Experimental
    Module: + mod_cache

    The CacheDisable directive instructs mod_cache to not cache urls at or above url-string.

    -

    Example

    +

    Example

    CacheDisable disk /local_files -

    -

    CacheEnable Directive

    Description: - Enable caching specified URLs in a specified storage manager
    Syntax: - CacheEnable cache_type url-string
    Context: - server config
    Status: - Experimental
    Module: - mod_cache
    +

    +
    top

    CacheEnable Directive

    Description: + Enable caching specified URLs in a specified storage manager
    Syntax: + CacheEnable cache_type url-string
    Context: + server config
    Status: + Experimental
    Module: + mod_cache

    The CacheEnable directive instructs mod_cache to cache urls at or below url-string. The cache store is specified with the cache_type argument. @@ -94,85 +96,86 @@ LoadModule cache_module modules/mod_cache.so
    cache_type disk instructs mod_cache to use the cache storage manager implemented by mod_disk_cache .

    -
    - CacheEnable disk /
    - CacheEnable mem /manual
    - CacheEnable fd /images
    -
    -

    CacheForceCompletion Directive

    Description: - Percentage of download to arrive for the cache to force complete transfert
    Syntax: - CacheLastModifiedFactor Percentage
    Default: - CacheLastModifiedFactor 60
    Context: - server config
    Status: - Experimental
    Module: - mod_cache
    +

    + CacheEnable disk /
    + CacheEnable mem /manual
    + CacheEnable fd /images
    +

    +
    top

    CacheForceCompletion Directive

    Description: + Percentage of download to arrive for the cache to force complete transfert
    Syntax: + CacheForceCompletion Percentage
    Default: + CacheForceCompletion 60
    Context: + server config
    Status: + Experimental
    Module: + mod_cache

    Percentage of download to arrive for the cache to force complete transfert.

    -
    - CacheForceCompletion -
    -
    +

    + CacheForceCompletion 80 +

    +
    This feature is currently not implemented. -
    -

    CacheForceCompletion Directive

    Description: - Percentage of download to arrive for the cache to force complete transfert
    Syntax: - CacheLastModifiedFactor Percentage
    Default: - CacheLastModifiedFactor 60
    Context: - server config
    Status: - Experimental
    Module: - mod_cache
    -

    Percentage of download to arrive for the cache to force complete transfert.

    - -
    - CacheForceCompletion -
    -
    -This feature is currently not implemented. -
    -

    CacheIgnoreCacheControl Directive

    Description: - Ignore requests from the client for uncached content
    Syntax: - CacheIgnoreCacheControl
    Context: - server config
    Status: - Experimental
    Module: - mod_cache
    +
    +
    top

    CacheIgnoreCacheControl Directive

    Description: + Ignore requests from the client for uncached content
    Syntax: + CacheIgnoreCacheControl
    Context: + server config
    Status: + Experimental
    Module: + mod_cache

    Ignore requests from the client for uncached content

    -
    +

    CacheIgnoreNoLastMod -

    -

    CacheIgnoreNoLastMod Directive

    Description: - Ignore responses where there is no Last Modified Header
    Syntax: - CacheIgnoreNoLastMod
    Context: - server config
    Status: - Experimental
    Module: - mod_cache
    +

    +
    top

    CacheIgnoreNoLastMod Directive

    Description: + Ignore responses where there is no Last Modified Header
    Syntax: + CacheIgnoreNoLastMod
    Context: + server config
    Status: + Experimental
    Module: + mod_cache

    Ignore responses where there is no Last Modified Header

    -
    +

    CacheIgnoreNoLastMod -

    -

    CacheLastModifiedFactor Directive

    Description: - The factor used to estimate the Expires date from the LastModified date
    Syntax: - CacheLastModifiedFactor float
    Default: - CacheLastModifiedFactor 0.1
    Context: - server config
    Status: - Experimental
    Module: - mod_cache
    +

    +
    top

    CacheLastModifiedFactor Directive

    Description: + The factor used to estimate the Expires date from the LastModified date
    Syntax: + CacheLastModifiedFactor float
    Default: + CacheLastModifiedFactor 0.1
    Context: + server config
    Status: + Experimental
    Module: + mod_cache

    The factor used to estimate the Expires date from the LastModified date.

    -
    - CacheLastModifiedFactor -
    -

    CacheMaxExpire Directive

    Description: - The maximum time in seconds to cache a document
    Syntax: - CacheMaxExpire seconds
    Default: - CacheMaxExpire 86400 (one day)
    Context: - server config
    Status: - Experimental
    Module: - mod_cache
    +

    + CacheLastModifiedFactor 0.5 +

    +
    top

    CacheMaxExpire Directive

    Description: + The maximum time in seconds to cache a document
    Syntax: + CacheMaxExpire seconds
    Default: + CacheMaxExpire 86400 (one day)
    Context: + server config
    Status: + Experimental
    Module: + mod_cache

    The maximum time in seconds to cache a document. The CacheMaxExpire takes precedence over the Expire field from the header.

    -
    +

    CacheMaxExpire 604800 -

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    +
    top

    CacheMaxStreamingBuffer Directive

    Description: + Maximum amount of a streamed response to buffer in memory before declaring the response uncacheable
    Syntax: + CacheMaxStreamingBuffer size_in_bytes
    Default: + CacheMaxStreamingBuffer 0
    Context: + server config
    Status: + Experimental
    Module: + mod_cache
    +

    Maximum number of bytes of a streamed response (i.e., a response where the entire content is not available all at once, such as a proxy or CGI response) to buffer before deciding if the response is cacheable. By default, a streamed response will not be cached unless it has a Content-Length header. The reason for this is to avoid using a large amount of memory to buffer a partial response that might end up being too large to fit in the cache anyway. To enable caching of streamed responses, use CacheMaxStreamingBuffer to specify the maximum amount of buffer space to use per request.

    +

    Note: Using a nonzero value for CacheMaxStreamingBuffer will not delay the transmission of the response to the client. As soon as mod_cache copies a + block of streamed content into a buffer, it sends the block on to the next + output filter for delivery to the client.

    + +

    + # Enable caching of streamed responses up to 64KB: + CacheMaxStreamingBuffer 65536 +

    +
    \ No newline at end of file diff --git a/docs/manual/mod/mod_cache.xml b/docs/manual/mod/mod_cache.xml index 2a920cb3e7..7165d68b21 100644 --- a/docs/manual/mod/mod_cache.xml +++ b/docs/manual/mod/mod_cache.xml @@ -19,9 +19,9 @@ management modules. Two storage management modules are included in the base Apache distribution:

    -
    mod_disk_cache
    +
    mod_disk_cache
    implements a disk based storage manager for use with mod_proxy
    -
    mod_mem_cache
    +
    mod_mem_cache
    implements an in-memory based storage manager. mod_mem_cache can be configured to operate in two modes: caching open file descriptors or caching objects in heap storage. mod_mem_cache @@ -77,7 +77,7 @@ LoadModule cache_module modules/mod_cache.so
    CacheDirLevels 5
    CacheDirLength 3
    </IfModule>
    -

    +
    LoadModule mem_cache_module modules/mod_mem_cache.so
    <IfModule mod_mem_cache.c>
    MCacheEnable mem /
    @@ -86,7 +86,7 @@ LoadModule cache_module modules/mod_cache.so
    MCacheMinObjectSize 1
    MCacheMaxObjectSize 2048
    </IfModule>
    -

    +
    </IfModule>
    @@ -202,7 +202,7 @@ LoadModule cache_module modules/mod_cache.so

    The factor used to estimate the Expires date from the LastModified date.

    - CacheLastModifiedFactor + CacheLastModifiedFactor 0.5 @@ -210,15 +210,15 @@ LoadModule cache_module modules/mod_cache.so
    CacheForceCompletion Percentage of download to arrive for the cache to force complete transfert -CacheLastModifiedFactor Percentage -CacheLastModifiedFactor 60 +CacheForceCompletion Percentage +CacheForceCompletion 60 server config

    Percentage of download to arrive for the cache to force complete transfert.

    - CacheForceCompletion + CacheForceCompletion 80 This feature is currently not implemented. @@ -226,25 +226,6 @@ This feature is currently not implemented.     - -CacheForceCompletion -Percentage of download to arrive for the cache to force complete transfer -CacheLastModifiedFactor Percentage -CacheLastModifiedFactor 60 -server config - - -

    Percentage of download to arrive for the cache to force complete transfer.

    - - - CacheForceCompletion - - -This feature is currently not implemented. - -     -     - CacheMaxStreamingBuffer Maximum amount of a streamed response to buffer in memory before declaring the response uncacheable @@ -254,9 +235,9 @@ This feature is currently not implemented.

    Maximum number of bytes of a streamed response (i.e., a response where the entire content is not available all at once, such as a proxy or CGI response) to buffer before deciding if the response is cacheable. By default, a streamed response will not be cached unless it has a Content-Length header. The reason for this is to avoid using a large amount of memory to buffer a partial response that might end up being too large to fit in the cache anyway. To enable caching of streamed responses, use CacheMaxStreamingBuffer to specify the maximum amount of buffer space to use per request.

    -

    Note: Using a nonzero value for CacheMaxStreamingBuffer will not delay the transmission of the response to the client. As soon as mod_cache copies a -block of streamed content into a buffer, it sends the block on to the next -output filter for delivery to the client.

    +

    Note: Using a nonzero value for CacheMaxStreamingBuffer will not delay the transmission of the response to the client. As soon as mod_cache copies a + block of streamed content into a buffer, it sends the block on to the next + output filter for delivery to the client.

    # Enable caching of streamed responses up to 64KB: diff --git a/docs/manual/mod/mod_cern_meta.html.en b/docs/manual/mod/mod_cern_meta.html.en index d79babdea1..88a4fe5745 100644 --- a/docs/manual/mod/mod_cern_meta.html.en +++ b/docs/manual/mod/mod_cern_meta.html.en @@ -1,11 +1,13 @@ -mod_cern_meta - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_cern_meta

    Description: - CERN httpd metafile semantics
    Status: - Extension
    Module Identifier: - cern_meta_module

    Summary

    + -->mod_cern_meta - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_cern_meta

    Description: + CERN httpd metafile semantics
    Status: + Extension
    Module Identifier: + cern_meta_module

    Summary

    Emulate the CERN HTTPD Meta file semantics. Meta files are HTTP headers that can be output in addition to the normal range of headers for each file accessed. They appear rather like the @@ -17,45 +19,45 @@

    More information on the CERN metafile semantics is available.

    -

    Directives

    See also

    MetaDir Directive

    Description: - Name of the directory to find CERN-style meta information -files
    Syntax: - MetaDir directory
    Default: - MetaDir .web
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Extension
    Module: - mod_cern_meta
    +
    top

    MetaDir Directive

    Description: + Name of the directory to find CERN-style meta information +files
    Syntax: + MetaDir directory
    Default: + MetaDir .web
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Extension
    Module: + mod_cern_meta

    Specifies the name of the directory in which Apache can find meta information files. The directory is usually a 'hidden' subdirectory of the directory that contains the file being accessed. Set to "." to look in the same directory as the file:

    -
    MetaDir .
    +

    MetaDir .

    Or, to set it to a subdirectory of the directory containing the files:

    -
    MetaDir .meta
    -

    MetaFiles Directive

    Description: - Activates CERN meta-file processing
    Syntax: - MetaFiles on|off
    Default: - MetaFiles off
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Extension
    Module: - mod_cern_meta
    +

    MetaDir .meta

    +
    top

    MetaFiles Directive

    Description: + Activates CERN meta-file processing
    Syntax: + MetaFiles on|off
    Default: + MetaFiles off
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Extension
    Module: + mod_cern_meta

    Turns on/off Meta file processing on a per-directory basis.

    -

    MetaSuffix Directive

    Description: - File name suffix for the file containg CERN-style -meta information
    Syntax: - MetaSuffix suffix
    Default: - MetaSuffix .meta
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Extension
    Module: - mod_cern_meta
    +
    top

    MetaSuffix Directive

    Description: + File name suffix for the file containg CERN-style +meta information
    Syntax: + MetaSuffix suffix
    Default: + MetaSuffix .meta
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Extension
    Module: + mod_cern_meta

    Specifies the file name suffix for the file containing the meta information. For example, the default values for the two directives will cause a request to @@ -66,6 +68,6 @@ meta informationMetaSuffix .meta

    +

    MetaSuffix .meta

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_cgi.html.en b/docs/manual/mod/mod_cgi.html.en index 9c664548e8..0d5254f92a 100644 --- a/docs/manual/mod/mod_cgi.html.en +++ b/docs/manual/mod/mod_cgi.html.en @@ -1,11 +1,13 @@ -mod_cgi - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_cgi

    Description: - Execution of CGI scripts
    Status: - Base
    Module Identifier: - cgi_module

    Summary

    + -->mod_cgi - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_cgi

    Description: + Execution of CGI scripts
    Status: + Base
    Module Identifier: + cgi_module

    Summary

    @@ -16,14 +18,14 @@ as a CGI script, and run by the server, with its output being returned to the client. Files acquire this type either by having a name containing an extension defined by the - AddType directive, or by being - in a ScriptAlias + AddType directive, or by being + in a ScriptAlias directory.

    When the server invokes a CGI script, it will add a variable called DOCUMENT_ROOT to the environment. This variable will contain the value of the - DocumentRoot configuration + DocumentRoot configuration variable.

    For an introduction to using CGI scripts with Apache, see @@ -31,10 +33,10 @@ With CGI.

    When using a multi-threaded MPM under unix, the module - mod_cgid should be used in place of + mod_cgid should be used in place of this module. At the user level, the two modules are essentially identical.

    -

    Directives

    See also

    CGI Environment variables

    +

    Directives

    Topics

    See also

    top

    CGI Environment variables

    The server will set the CGI environment variables as described in the CGI specification, with the following provisions:

    @@ -42,7 +44,7 @@
    PATH_INFO
    -
    This will not be available if the AcceptPathInfo directive is explicitly set to +
    This will not be available if the AcceptPathInfo directive is explicitly set to off. The default behavior, if AcceptPathInfo is not given, is that mod_cgi will accept path info (trailing /more/path/info following the script filename in the URI), while @@ -53,13 +55,13 @@
    REMOTE_HOST
    -
    This will only be set if HostnameLookups is set to on (it +
    This will only be set if HostnameLookups is set to on (it is off by default), and if a reverse DNS lookup of the accessing host's address indeed finds a host name.
    REMOTE_IDENT
    -
    This will only be set if IdentityCheck is set to +
    This will only be set if IdentityCheck is set to on and the accessing host supports the ident protocol. Note that the contents of this variable cannot be relied upon because it can easily be faked, and if there is a @@ -71,7 +73,7 @@
    This will only be set if the CGI script is subject to authentication.
    -

    CGI Debugging

    +
    top

    CGI Debugging

    Debugging CGI scripts has traditionally been difficult, mainly because it has not been possible to study the output (standard output and error) for scripts which are failing to run @@ -83,51 +85,51 @@ execute properly. Each CGI script which fails to operate causes several lines of information to be logged. The first two lines are always of the format:

    -
    - %% [time] request-line
    +

    + %% [time] request-line
    %% HTTP-status CGI-script-filename -

    +

    If the error is that CGI script cannot be run, the log file will contain an extra two lines:

    -
    - %%error
    +

    + %%error
    error-message -

    +

    Alternatively, if the error is the result of the script returning incorrect header information (often due to a bug in the script), the following information is logged:

    -
    - %request
    - All HTTP request headers received
    - POST or PUT entity (if any)
    - %response
    - All headers output by the CGI script
    - %stdout
    - CGI standard output
    - %stderr
    - CGI standard error
    -
    +

    + %request
    + All HTTP request headers received
    + POST or PUT entity (if any)
    + %response
    + All headers output by the CGI script
    + %stdout
    + CGI standard output
    + %stderr
    + CGI standard error
    +

    (The %stdout and %stderr parts may be missing if the script did not output anything on standard output or standard error).

    -

    ScriptLog Directive

    Description: - Location of the CGI script error logfile
    Syntax: - ScriptLog file-path
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_cgi, mod_cgid
    +
    top

    ScriptLog Directive

    Description: + Location of the CGI script error logfile
    Syntax: + ScriptLog file-path
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_cgi, mod_cgid

    The ScriptLog directive sets the CGI script error logfile. If no ScriptLog is given, no error log is created. If given, any CGI errors are logged into the filename given as argument. If this is a relative file or path it is taken relative to the ServerRoot.

    -

    Example

    +

    Example

    ScriptLog logs/cgi_log -

    +

    This log will be opened as the user the child processes run - as, ie. the user specified in the main User directive. This means that + as, ie. the user specified in the main User directive. This means that either the directory the script log is in needs to be writable by that user or the file needs to be manually created and set to be writable by that user. If you place the script log in @@ -140,26 +142,26 @@ continuously on running servers. It is not optimized for speed or efficiency, and may have security problems if used in a manner other than that for which it was designed.

    -

    ScriptLogBuffer Directive

    Description: - Maximum amount of PUT or POST requests that will be recorded -in the scriptlog
    Syntax: - ScriptLogBuffer bytes
    Default: - ScriptLogBuffer 1024
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_cgi, mod_cgid
    +
    top

    ScriptLogBuffer Directive

    Description: + Maximum amount of PUT or POST requests that will be recorded +in the scriptlog
    Syntax: + ScriptLogBuffer bytes
    Default: + ScriptLogBuffer 1024
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_cgi, mod_cgid

    The size of any PUT or POST entity body that is logged to the file is limited, to prevent the log file growing too big too quickly if large bodies are being received. By default, up to 1024 bytes are logged, but this can be changed with this directive.

    -

    ScriptLogLength Directive

    Description: - Size limit of the CGI script logfile
    Syntax: - ScriptLogLength bytes
    Default: - ScriptLogLength 10385760
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_cgi, mod_cgid
    +
    top

    ScriptLogLength Directive

    Description: + Size limit of the CGI script logfile
    Syntax: + ScriptLogLength bytes
    Default: + ScriptLogLength 10385760
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_cgi, mod_cgid

    ScriptLogLength can be used to limit the size of the CGI script logfile. Since the logfile logs a lot of information per CGI error (all request headers, all script output) @@ -167,4 +169,4 @@ in the scriptlogApache HTTP Server Version 2.0IndexHome \ No newline at end of file +

    \ No newline at end of file diff --git a/docs/manual/mod/mod_cgid.html.en b/docs/manual/mod/mod_cgid.html.en index 65077ff226..f060d8063a 100644 --- a/docs/manual/mod/mod_cgid.html.en +++ b/docs/manual/mod/mod_cgid.html.en @@ -1,16 +1,18 @@ -mod_cgid - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_cgid

    Description: - Execution of CGI scripts using an - external CGI daemon
    Status: - Base
    Module Identifier: - cgid_module
    Compatibility: - Unix threaded MPMs only

    Summary

    -

    Except for the optimizations and the additional ScriptSock directive noted below, + -->mod_cgid - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_cgid

    Description: + Execution of CGI scripts using an + external CGI daemon
    Status: + Base
    Module Identifier: + cgid_module
    Compatibility: + Unix threaded MPMs only

    Summary

    +

    Except for the optimizations and the additional ScriptSock directive noted below, mod_cgid behaves similarly to mod_cgi. See the - mod_cgi Summary for additional details about + mod_cgi Summary for additional details about Apache and CGI.

    On certain unix operating systems, forking a process from a @@ -23,20 +25,20 @@ socket.

    This module is used by default instead of - mod_cgi whenever a multi-threaded MPM + mod_cgi whenever a multi-threaded MPM is selected during the compilation process. At the user level, this module is identical in configuration and operation to - mod_cgi. The only exception is the + mod_cgi. The only exception is the additional directive ScriptSock which gives the name of the socket to use for communication with the cgi daemon.

    -

    Directives

    ScriptSock Directive

    Description: -
    Syntax: - ScriptSock file-path
    Default: - ScriptSock logs/cgisock
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_cgid
    +
    top

    ScriptSock Directive

    Description: +
    Syntax: + ScriptSock file-path
    Default: + ScriptSock logs/cgisock
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_cgid

    This directive sets the name of the socket to use for communication with the CGI daemon. The socket will be opened using the permissions of the user who starts Apache (usually @@ -44,8 +46,8 @@ scripts, it is important that no other user has permission to write in the directory where the socket is located.

    -

    Example

    +

    Example

    ScriptSock /var/run/cgid.sock -

    +

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_charset_lite.html.en b/docs/manual/mod/mod_charset_lite.html.en index c8c1ff967b..7170e53aee 100644 --- a/docs/manual/mod/mod_charset_lite.html.en +++ b/docs/manual/mod/mod_charset_lite.html.en @@ -1,48 +1,50 @@ -mod_charset_lite - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_charset_lite

    Description: - Specify character set translation or recoding
    Status: - Experimental
    Module Identifier: - charset_lite_module

    Summary

    + -->mod_charset_lite - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_charset_lite

    Description: + Specify character set translation or recoding
    Status: + Experimental
    Module Identifier: + charset_lite_module

    Summary

    This is an experimental module and should be used with care. Experiment with your mod_charset_lite configuration to ensure that it performs the desired function.

    -

    mod_charset_lite allows the administrator to +

    mod_charset_lite allows the administrator to specify the source character set of objects as well as the character set they should be translated into before sending to the - client. mod_charset_lite does not translate the + client. mod_charset_lite does not translate the data itself but instead tells Apache what translation to - perform. mod_charset_lite is applicable to EBCDIC + perform. mod_charset_lite is applicable to EBCDIC and ASCII host environments. In an EBCDIC environment, Apache normally translates text content from the code page of the Apache - process locale to ISO-8859-1. mod_charset_lite + process locale to ISO-8859-1. mod_charset_lite can be used to specify that a different translation is to be performed. In an ASCII environment, Apache normally performs no - translation, so mod_charset_lite is needed in + translation, so mod_charset_lite is needed in order for any translation to take place.

    This module provides a small subset of configuration mechanisms implemented by Russian Apache and its associated mod_charset.

    -

    Directives

    Common Problems

    +

    Directives

    Topics

    • Common Problems
    top

    Common Problems

    Invalid character set names

    -

    The character set name parameters of CharsetSourceEnc and - CharsetDefault +

    The character set name parameters of CharsetSourceEnc and + CharsetDefault must be acceptable to the translation mechanism used by APR on the - system where mod_charset_lite is deployed. These + system where mod_charset_lite is deployed. These character set names are not standardized and are usually not the same as the corresponding values used in http headers. Currently, APR can only use iconv(3), so you can easily test your character set names using the iconv(1) program, as follows:

    -
    +

    iconv -f charsetsourceenc-value -t charsetdefault-value -

    +

    Mismatch between character set of content and translation @@ -60,13 +62,13 @@ it cannot translate the input buffer. -

    CharsetDefault Directive

    Description: - Charset to translate into
    Syntax: - CharsetDefault charset
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Experimental
    Module: - mod_charset_lite
    +
    top

    CharsetDefault Directive

    Description: + Charset to translate into
    Syntax: + CharsetDefault charset
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Experimental
    Module: + mod_charset_lite

    The CharsetDefault directive specifies the charset that content in the associated container should be translated to.

    @@ -76,23 +78,23 @@ APR. Generally, this means that it must be supported by iconv.

    -

    Example

    - <Directory "/export/home/trawick/apacheinst/htdocs/convert">
    - CharsetSourceEnc UTF-16BE
    - CharsetDefault ISO8859-1
    +

    Example

    + <Directory "/export/home/trawick/apacheinst/htdocs/convert">
    + CharsetSourceEnc UTF-16BE
    + CharsetDefault ISO8859-1
    </Directory> -

    -

    CharsetOptions Directive

    Description: - Configures charset tranlation behavior
    Syntax: - CharsetOptions option [option] ...
    Default: - CharsetOptions DebugLevel=0 -NoImplicitAdd
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Experimental
    Module: - mod_charset_lite
    +

    +
    top

    CharsetOptions Directive

    Description: + Configures charset tranlation behavior
    Syntax: + CharsetOptions option [option] ...
    Default: + CharsetOptions DebugLevel=0 +NoImplicitAdd
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Experimental
    Module: + mod_charset_lite

    The CharsetOptions directive configures certain - behaviors of mod_charset_lite. Option can + behaviors of mod_charset_lite. Option can be one of

    @@ -100,7 +102,7 @@ NoImplicitAddmod_charset_lite. By default, no messages are + mod_charset_lite. By default, no messages are generated. This is equivalent to DebugLevel=0. With higher numbers, more debug messages are generated, and server performance will be degraded. The actual meanings of @@ -111,20 +113,20 @@ NoImplicitAddmod_charset_lite should implicitly insert its + mod_charset_lite should implicitly insert its filter when the configuration specifies that the character set of content should be translated. If the filter chain is explicitly configured using the AddOutputFilter directive, NoImplicitAdd should be specified so that - mod_charset_lite doesn't add its filter.
    + mod_charset_lite doesn't add its filter.
    -

    CharsetSourceEnc Directive

    Description: - Source charset of files
    Syntax: - CharsetSourceEnc charset
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Experimental
    Module: - mod_charset_lite
    +
    top

    CharsetSourceEnc Directive

    Description: + Source charset of files
    Syntax: + CharsetSourceEnc charset
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Experimental
    Module: + mod_charset_lite

    The CharsetSourceEnc directive specifies the source charset of files in the associated container.

    @@ -133,12 +135,12 @@ NoImplicitAdd

    example

    - <Directory "/export/home/trawick/apacheinst/htdocs/convert">
    - CharsetSourceEnc UTF-16BE
    - CharsetDefault ISO8859-1
    +

    example

    + <Directory "/export/home/trawick/apacheinst/htdocs/convert">
    + CharsetSourceEnc UTF-16BE
    + CharsetDefault ISO8859-1
    </Directory> -     +

    The character set names in this example work with the iconv translation support in Solaris 8.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +
    \ No newline at end of file diff --git a/docs/manual/mod/mod_dav.html.en b/docs/manual/mod/mod_dav.html.en index 9ca6566e46..cede15875d 100644 --- a/docs/manual/mod/mod_dav.html.en +++ b/docs/manual/mod/mod_dav.html.en @@ -1,12 +1,14 @@ -mod_dav - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_dav

    Description: - Distributed Authoring and Versioning -(WebDAV) functionality
    Status: - Extension
    Module Identifier: - dav_module

    Summary

    + -->mod_dav - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_dav

    Description: + Distributed Authoring and Versioning +(WebDAV) functionality
    Status: + Extension
    Module Identifier: + dav_module

    Summary

    This module provides class 1 and class 2 WebDAV ('Web-based Distributed Authoring and Versioning') functionality for Apache. This extension to the HTTP protocol allows creating, moving, @@ -16,61 +18,61 @@

    To enable mod_dav, add the following to a container in your httpd.conf file:

    -
    Dav On
    +

    Dav On

    Also, specify a valid filename for the DAV lock database by adding the following to the global section in your httpd.conf file:

    -
    DavLockDB /tmp/DavLock     +

    DavLockDB /tmp/DavLock     (Any web-server writable filename, without an extension) -

    -

    Directives

    Dav Directive

    Description: - Enable WebDAV HTTP methods
    Syntax: - Dav on|off
    Default: - Dav off
    Context: - directory
    Status: - Extension
    Module: - mod_dav
    +

    +
    top

    Dav Directive

    Description: + Enable WebDAV HTTP methods
    Syntax: + Dav on|off
    Default: + Dav off
    Context: + directory
    Status: + Extension
    Module: + mod_dav

    Use the Dav directive to enable the WebDAV HTTP methods for the given container. You may wish to add a - <Limit> clause - inside the <location> directive to limit access to + <Limit> clause + inside the <location> directive to limit access to DAV-enabled locations.

    -

    Example

    - DavLockDB /tmp/DavLock
    -
    - <Location /foo>
    - Dav On
    -
    - AuthType Basic
    - AuthName DAV
    - AuthUserFile user.passwd
    -
    -   <LimitExcept GET HEAD OPTIONS>
    -   require user admin
    -   </LimitExcept>
    - </Location>
    -
    -

    DavDepthInfinity Directive

    Description: - Allow PROPFIND, Depth: Infinity requests
    Syntax: - DavDepthInfinity on|off
    Default: - DavDepthInfinity off
    Context: - directory
    Status: - Extension
    Module: - mod_dav
    +

    Example

    + DavLockDB /tmp/DavLock
    +
    + <Location /foo>
    + Dav On
    +
    + AuthType Basic
    + AuthName DAV
    + AuthUserFile user.passwd
    +
    +   <LimitExcept GET HEAD OPTIONS>
    +   require user admin
    +   </LimitExcept>
    + </Location>
    +

    +
    top

    DavDepthInfinity Directive

    Description: + Allow PROPFIND, Depth: Infinity requests
    Syntax: + DavDepthInfinity on|off
    Default: + DavDepthInfinity off
    Context: + directory
    Status: + Extension
    Module: + mod_dav

    Use the DavDepthInfinity directive to allow the processing of PROPFIND requests containing the header 'Depth: Infinity'. Because this type of request could constitute a denial-of-service attack, by default it is not allowed.

    -

    DavLockDB Directive

    Description: - Location of the DAV lock database
    Syntax: - DavLockDB file-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_dav
    +
    top

    DavLockDB Directive

    Description: + Location of the DAV lock database
    Syntax: + DavLockDB file-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_dav

    Use the DavLockDB directive to specify the full path to the lock database, excluding an extension. The default (file system) implementation of mod_dav uses a SDBM @@ -78,17 +80,17 @@ modules/dav/util/lockview can be used from the server to display all locks in a lock database.

    -

    Example

    +

    Example

    DavLockDB /tmp/DavLock -

    -

    DavMinTimeout Directive

    Description: - Minimum amount of time the server holds a lock on -a DAV resource
    Syntax: - DavMinTimeout seconds
    Default: - DavMinTimeout 0
    Context: - directory
    Status: - Extension
    Module: - mod_dav
    +

    +
    top

    DavMinTimeout Directive

    Description: + Minimum amount of time the server holds a lock on +a DAV resource
    Syntax: + DavMinTimeout seconds
    Default: + DavMinTimeout 0
    Context: + directory
    Status: + Extension
    Module: + mod_dav

    When a client requests a DAV resource lock, it can also specify a time when the lock will be automatically removed by the server. This value is only a request, and the server can @@ -101,9 +103,9 @@ a DAV resource

    Example

    - <Location /MSWord>
    - DavMinTimeout 600
    - </Location>
    -
    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    Example

    + <Location /MSWord>
    + DavMinTimeout 600
    + </Location>
    +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_dav.html.ja.jis b/docs/manual/mod/mod_dav.html.ja.jis index 7113d05dc9..6cdcd12068 100644 --- a/docs/manual/mod/mod_dav.html.ja.jis +++ b/docs/manual/mod/mod_dav.html.ja.jis @@ -1,15 +1,17 @@ -mod_dav - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mod_dav

    $B@bL@(B: - $BJ,;6%*!<%5%j%s%0$H%P!<%8%g%s4IM}(B -(WebDAV) $B5!G=(B
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<(B$B%k<1JL;R(B: - dav_module

    $B35MW(B

    + -->mod_dav - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mod_dav

    $B@bL@(B: + $BJ,;6%*!<%5%j%s%0$H%P!<%8%g%s4IM}(B +(WebDAV) $B5!G=(B
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k<1JL;R(B: + dav_module

    $B35MW(B

    $B$3$N%b%8%e!<%k$O%/%i%9(B 1 $B$H%/%i%9(B 2 $B$N(B WebDAV - ('$B%&%'%V%Y!<%9$NJ,;6%*!<(B$B%5%j%s%0$H%P!<%8%g%s4IM}(B') + ('$B%&%'%V%Y!<%9$NJ,;6%*!<%5%j%s%0$H%P!<%8%g%s4IM}(B') $B5!G=$r(B Apache $B$KDs6!$7$^$9!#(B $B$3$N(B HTTP $B%W%m%H%3%k$N3HD%$K$h$j!"%j%b!<%H$N%&%'%V%5!<%P>e$K$"$k(B $B%j%=!<%9$d%3%l%/%7%g%s$r(B @@ -18,66 +20,66 @@

    mod_dav $B$rM-8z$K$9$k$K$O!"(Bhttpd.conf $B%U%!%$%kCf$N%3%s%F%J$K -

    Dav On
    +

    Dav On

    $BF1;~$K(B httpd.conf $B%U%!%$%k$N(B $B%0%m!<%P%k%;%/%7%g%s$K$r;XDj$7$^$9(B:

    -
    DavLockDB /tmp/DavLock     +

    DavLockDB /tmp/DavLock???? ($B%&%'%V%5!<%P$N=q$-9~$a$k%U%!%$%kL>$G!"(B $B3HD%;R$N$J$$$b$N(B) -

    -

    $B%G%#%l%/%F%#%V(B

    Dav $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - WebDAV HTTP $B%a%=%C%I$rM-8z$K$7(B$B$^$9(B
    $B9=J8(B: - Dav on|off
    $B%G%U%)%k%H(B: - Dav off
    $B%3%s%F%-%9%H(B: - directory
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<%k(B: - mod_dav
    +

    +
    top

    Dav $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + WebDAV HTTP $B%a%=%C%I$rM-8z$K$7$^$9(B
    $B9=J8(B: + Dav on|off
    $B%G%U%)%k%H(B: + Dav off
    $B%3%s%F%-%9%H(B: + directory
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k(B: + mod_dav

    $BM?$($i$l$?%3%s%F%J$G(B WebDAV HTTP $B%a%=%C%I$,;H$($k$h$&$K$9$k$K$O!"(B Dav $B%G%#%l%/%F%#%V$r;H$$$^$9!#(B DAV $B$rM-8z$K$7$?>l=j$X$N%"%/%;%9$r@)8B$9$k$?$a$K$O!"(B - <Location> + <Location> $B%G%#%l%/%F%#%VFbIt$K(B - <Limit> + <Limit> $B@a$r2C$($^$9!#(B

    -

    $BNc(B

    - DavLockDB /tmp/DavLock
    -
    - <Location /foo>
    - Dav On
    -
    - AuthType Basic
    - AuthName DAV
    - AuthUserFile user.passwd
    -
    -   <LimitExcept GET HEAD OPTIONS>
    -   require user admin
    -   </LimitExcept>
    - </Location>
    -
    -

    DavDepthInfinity $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - PROPFIND, Depth: Infinity $B%j%/%(%9%H$r5v2D$7$^$9(B
    $B9=J8(B: - DavDepthInfinity on|off
    $B%G%U%)%k%H(B: - DavDepthInfinity off
    $B%3%s%F%-%9%H(B: - directory
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<%k(B: - mod_dav
    +

    $BNc(B

    + DavLockDB /tmp/DavLock
    +
    + <Location /foo>
    + Dav On
    +
    + AuthType Basic
    + AuthName DAV
    + AuthUserFile user.passwd
    +
    + ??<LimitExcept GET HEAD OPTIONS>
    + ??require user admin
    + ??</LimitExcept>
    + </Location>
    +

    +
    top

    DavDepthInfinity $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + PROPFIND, Depth: Infinity $B%j%/%(%9%H$r5v2D$7$^$9(B
    $B9=J8(B: + DavDepthInfinity on|off
    $B%G%U%)%k%H(B: + DavDepthInfinity off
    $B%3%s%F%-%9%H(B: + directory
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k(B: + mod_dav

    'Depth: Infinity' $B$r4^$s$G$$$k(B - PROPFIND $B%j%/(B$B%(%9%H$r=hM}$G$-$k$h$&$K$9$k$K$O!"(B + PROPFIND $B%j%/%(%9%H$r=hM}$G$-$k$h$&$K$9$k$K$O!"(B DavDepthInfinity $B%G%#%l%/%F%#%V$r;H$$$^$9!#$3$N%?%$%W$N%j%/%(%9%H$O(B denial-of-service $B%"%?%C%/$H$J$j$&$k$N$G!"(B $B%G%U%)%k%H$G$O5v2D$5$l$F$$$^$;$s!#(B

    -

    DavLockDB $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - DAV $B%m%C%/%G!<%?%Y!<%9(B$B$N0LCV$G$9(B
    $B9=J8(B: - DavLockDB file-path
    $B%3%s%F%-%9%H(B: - server config, virtual host
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<%k(B: - mod_dav
    +
    top

    DavLockDB $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + DAV $B%m%C%/%G!<%?%Y!<%9$N0LCV$G$9(B
    $B9=J8(B: + DavLockDB file-path
    $B%3%s%F%-%9%H(B: + server config, virtual host
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k(B: + mod_dav

    $B%m%C%/%G!<%?%Y!<%9$X$N%U%k%Q%9$r!"3HD%;R$r=|$$$?7A$G(B $B;XDj$9$k$K$O!"(BDavLockDB $B$r;H$$$^$9!#%G%U%)%k%H$N(B @@ -87,17 +89,17 @@ modules/dav/util/lockview $B%f!<%F%#%j%F%#$r;HMQ$G$-$^$9!#(B

    -

    $BNc(B

    +

    $BNc(B

    DavLockDB /tmp/DavLock -

    -

    DavMinTimeout $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%5!<%P$,(B DAV $B%j%=!<%9$N%m%C%/$r0];}$9$k:G>.;~4V$G$9!#(B -
    $B9=J8(B: - DavMinTimeout seconds
    $B%G%U%)%k%H(B: - DavMinTimeout 0
    $B%3%s%F%-%9%H(B: - directory
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<%k(B: - mod_dav
    +

    +
    top

    DavMinTimeout $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%5!<%P$,(B DAV $B%j%=!<%9$N%m%C%/$r0];}$9$k:G>.;~4V$G$9!#(B +
    $B9=J8(B: + DavMinTimeout seconds
    $B%G%U%)%k%H(B: + DavMinTimeout 0
    $B%3%s%F%-%9%H(B: + directory
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k(B: + mod_dav

    $B%/%i%$%"%s%H$,(B DAV $B%j%=!<%9%m%C%/$rMW5a$7$?>l9g!"(B $B%m%C%/$,%5!<%P$K$h$C$F<+F0E*$K2r=|$5$l$k$^$G$N;~4V$r(B $BF1;~$K;XDj$9$k$3$H$,$G$-$^$9!#$3$NCM$OC1$J$k%j%/%(%9%H$G$"$C$F!"(B @@ -112,9 +114,9 @@ DavLockDB /tmp/DavLock DavMinTimeout $B$r;H$C$F(B $B$3$l$r$b$C$HBg$-$JCM(B ($BNc$($P(B 600 $BIC(B) $B$K>e=q$-$G$-$^$9!#(B

    -

    $BNc(B

    - <Location /MSWord>
    - DavMinTimeout 600
    - </Location>
    -
    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file +

    $BNc(B

    + <Location /MSWord>
    + DavMinTimeout 600
    + </Location>
    +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_deflate.html.en b/docs/manual/mod/mod_deflate.html.en index 64bf6e1875..9f1d1a83dc 100644 --- a/docs/manual/mod/mod_deflate.html.en +++ b/docs/manual/mod/mod_deflate.html.en @@ -1,17 +1,19 @@ -mod_deflate - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_deflate

    Description: - Compress content before - it is delivered to the client
    Status: - Extension
    Module Identifier: - deflate_module

    Summary

    -

    The mod_deflate module provides + -->mod_deflate - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_deflate

    Description: + Compress content before + it is delivered to the client
    Status: + Extension
    Module Identifier: + deflate_module

    Summary

    +

    The mod_deflate module provides the DEFLATE output filter that allows output from your server to be compressed before being sent to the client over the network.

    -

    Directives

    See also

    Enabling Compression

    +
    top

    Enabling Compression

    Compression is implemented by the DEFLATE filter. The following directive @@ -23,56 +25,56 @@

    If you set this to anything but '1' it will be ignored, so you can do negative matches.

    -
    SetEnv gzip-only-text/html 1
    +

    SetEnv gzip-only-text/html 1
    SetOutputFilter DEFLATE -

    +

    Here is an example of enabling compression for the Apache documentation:

    -
    -<Directory "/your-server-root/manual">
    - SetEnv gzip-only-text/html 1
    - SetOutputFilter DEFLATE
    +

    +<Directory "/your-server-root/manual">
    + SetEnv gzip-only-text/html 1
    + SetOutputFilter DEFLATE
    </Directory> -

    -

    DeflateBufferSize Directive

    Description: - Fragment size to be compressed at one time by zlib
    Syntax: - DeflateBufferSize value
    Default: - DeflateBufferSize 8096
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_deflate
    +

    +
    top

    DeflateBufferSize Directive

    Description: + Fragment size to be compressed at one time by zlib
    Syntax: + DeflateBufferSize value
    Default: + DeflateBufferSize 8096
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_deflate

    The DeflateBufferSize directive specifies the size in bytes of the fragments that zlib should compress at one time.

    -

    DeflateFilterNote Directive

    Description: - Places the compression ratio in a note for logging
    Syntax: - DeflateFilterNote notename
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_deflate
    +
    top

    DeflateFilterNote Directive

    Description: + Places the compression ratio in a note for logging
    Syntax: + DeflateFilterNote notename
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_deflate

    The DeflateFilterNote directive specifies that a note about compression ratios should be attached to the request. The name of the note is the value specified for the directive.

    -

    DeflateMemLevel Directive

    Description: - How much memory should be used by zlib for compression
    Syntax: - DeflateMemLevel value
    Default: - DeflateMemLevel 9
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_deflate
    +
    top

    DeflateMemLevel Directive

    Description: + How much memory should be used by zlib for compression
    Syntax: + DeflateMemLevel value
    Default: + DeflateMemLevel 9
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_deflate

    The DeflateMemLevel directive specifies how much memory should be used by zlib for compression (a value between 1 and 9).

    -

    DeflateWindowSize Directive

    Description: - Zlib compression window size
    Syntax: - DeflateWindowSize value
    Default: - DeflateWindowSize 15
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_deflate
    +
    top

    DeflateWindowSize Directive

    Description: + Zlib compression window size
    Syntax: + DeflateWindowSize value
    Default: + DeflateWindowSize 15
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_deflate

    The DeflateWindowSize directive specifies the zlib compression window size (a value between 1 and 15).

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_deflate.html.ja.jis b/docs/manual/mod/mod_deflate.html.ja.jis index 4321e38f52..597650e4f4 100644 --- a/docs/manual/mod/mod_deflate.html.ja.jis +++ b/docs/manual/mod/mod_deflate.html.ja.jis @@ -1,18 +1,20 @@ -mod_deflate - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mod_deflate

    $B@bL@(B: - $B%/%i%$%"%s%H$XAw$i$l$kA0$K%3%s%F%s(B$B%D$r05=L$9$k(B
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<(B$B%k<1JL;R(B: - deflate_module

    $B35MW(B

    -

    mod_deflate $B%b%8%e!<%k$O(B DEFLATE - $B=PNO%U%#%k%?$rDs6!$7$^$9!#(B$B$3$l$O%5!<%P$+$i$N=PNO$r!"%M%C%H%o!<%/$r(B + -->mod_deflate - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mod_deflate

    $B@bL@(B: + $B%/%i%$%"%s%H$XAw$i$l$kA0$K%3%s%F%s%D$r05=L$9$k(B
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k<1JL;R(B: + deflate_module

    $B35MW(B

    +

    mod_deflate $B%b%8%e!<%k$O(B DEFLATE + $B=PNO%U%#%k%?$rDs6!$7$^$9!#$3$l$O%5!<%P$+$i$N=PNO$r!"%M%C%H%o!<%/$r(B $BDL$7$F%/%i%$%"%s%H$KAw$kA0$K05=L$9$k$3$H$r2DG=$K$7$^$9!#(B

    -

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    $B05=L$rM-8z$K$9$k(B

    +
    top

    $B05=L$rM-8z$K$9$k(B

    $B05=L5!G=$O(B DEFLATE $B%U%#%k%?(B - $B$K$h$j(B$B

    $B$h$/;H$o$l$F$$$k%V%i%&%6$G$O!"$9$Y$F$N%3%s%F%s%D$KBP$9$k(B $B05=L$r07$($k$o$1$G$O$"$j$^$;$s!#$G$9$+$i!"(B'gzip-only-text/html' @@ -20,59 +22,59 @@ $B05=L$,F/$/$h$&$K$7$?J}$,$h$$$+$b$7$l$^$;$s(B ($B0J2<;2>H(B)

    $B$3$NCM$r(B 1 $B0J30$NCM$K@_Dj$7$?>l9g$OL5;k$5$l$^$9$N$G!"(B - $B%M%,%F%#%V%^(B$B%C%A$r9T$J$&$3$H$,$G$-$^$9!#(B

    + $B%M%,%F%#%V%^%C%A$r9T$J$&$3$H$,$G$-$^$9!#(B

    -
    SetEnv gzip-only-text/html 1
    +

    SetEnv gzip-only-text/html 1
    SetOutputFilter DEFLATE -

    +

    $B$3$l$O(B Apache $B$N%I%-%e%a%s%F!<%7%g%s$KBP$7$F05=L$rM-8z$K$9$k@_Dj$G$9(B:

    -
    -<Directory "/your-server-root/manual">
    - SetEnv gzip-only-text/html 1
    - SetOutputFilter DEFLATE
    +

    +<Directory "/your-server-root/manual">
    + SetEnv gzip-only-text/html 1
    + SetOutputFilter DEFLATE
    </Directory> -

    -

    DeflateBufferSize $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - zlib $B$,0lEY$K05=L$9$k2t$NBg$-$5(B
    $B9=J8(B: - DeflateBufferSize value
    $B%G%U%)%k%H(B: - DeflateBufferSize 8096
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<%k(B: - mod_deflate
    +

    +
    top

    DeflateBufferSize $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + zlib $B$,0lEY$K05=L$9$k2t$NBg$-$5(B
    $B9=J8(B: + DeflateBufferSize value
    $B%G%U%)%k%H(B: + DeflateBufferSize 8096
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k(B: + mod_deflate

    DeflateBufferSize $B%G%#%l%/%F%#%V$O(B zlib $B$,0lEY$K05=L$9$k2t$NBg$-$5$r%P%$%HC10L$G;XDj$7$^$9!#(B

    -

    DeflateFilterNote $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%m%.%s%0MQ$K05=LHf$r%a%b$KDI2C(B
    $B9=J8(B: - DeflateFilterNote notename
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<%k(B: - mod_deflate
    +
    top

    DeflateFilterNote $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%m%.%s%0MQ$K05=LHf$r%a%b$KDI2C(B
    $B9=J8(B: + DeflateFilterNote notename
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k(B: + mod_deflate

    DeflateFilterNote $B%G%#%l%/%F%#%V$O(B $B05=LHf$K4X$9$k%a%b$,%j%/%(%9%H$KIU2C$5$l$k$3$H$r;XDj$7$^$9!#(B $B%a%b$NL>A0$O%G%#%l%/%F%#%V$K;XDj$5$l$?CM$G$9!#(B

    -

    DeflateMemLevel $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - zlib $B$,05=L$K;H$&%a%b%j$N%l%Y%k$r;XDj(B
    $B9=J8(B: - DeflateMemLevel value
    $B%G%U%)%k%H(B: - DeflateMemLevel 9
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<%k(B: - mod_deflate
    +
    top

    DeflateMemLevel $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + zlib $B$,05=L$K;H$&%a%b%j$N%l%Y%k$r;XDj(B
    $B9=J8(B: + DeflateMemLevel value
    $B%G%U%)%k%H(B: + DeflateMemLevel 9
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k(B: + mod_deflate

    DeflateMemLevel $B%G%#%l%/%F%#%V$O(B zlib $B$,05=L$K;H$&%a%b%j$N%l%Y%k$r@_Dj$7$^$9(B (1 $B$+$i(B 9 $B$N4V$NCM(B)$B!#(B ($BLuCm(B: 2 $B$rDl$H$9$kBP?t$NCM$K$J$j$^$9!#(B 8 $BDxEY$,NI$$$G$7$g$&!#(B)

    -

    DeflateWindowSize $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - Zlib $B$N05=LMQ%&%#%s%I%&$NBg$-$5(B
    $B9=J8(B: - DeflateWindowSize value
    $B%G%U%)%k%H(B: - DeflateWindowSize 15
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: - Extension
    $B%b%8%e!<%k(B: - mod_deflate
    +
    top

    DeflateWindowSize $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + Zlib $B$N05=LMQ%&%#%s%I%&$NBg$-$5(B
    $B9=J8(B: + DeflateWindowSize value
    $B%G%U%)%k%H(B: + DeflateWindowSize 15
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: + Extension
    $B%b%8%e!<%k(B: + mod_deflate

    DeflateWindowSize $B%G%#%l%/%F%#%V$O(B zlib $B$N05=LMQ%&%#%s%I%&(B ($BLuCm(B: zlib $B$G;HMQ$5$l$kMzNr%P%C%U%!(B) $B$NBg$-$5$r;XDj$7$^$9(B (1 $B$+$i(B 15 $B$N4V$NCM(B)$B!#(B ($BLuCm(B: 2 $B$rDl$H$9$kBP?t$NCM$K$J$j$^$9!#(B 8 $B$+$i(B 15 $B$K$9$k$N$,NI$$$G$7$g$&!#(B)

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_dir.html.en b/docs/manual/mod/mod_dir.html.en index 2c0a671e78..4a41d18ebf 100644 --- a/docs/manual/mod/mod_dir.html.en +++ b/docs/manual/mod/mod_dir.html.en @@ -1,22 +1,24 @@ -mod_dir - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_dir

    Description: - Provides for "trailing slash" redirects and - serving directory index files
    Status: - Base
    Module Identifier: - dir_module

    Summary

    + -->mod_dir - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_dir

    Description: + Provides for "trailing slash" redirects and + serving directory index files
    Status: + Base
    Module Identifier: + dir_module

    Summary

    The index of a directory can come from one of two sources:

    The two functions are separated so that you can completely remove (or replace) automatic index generation should you want @@ -26,18 +28,18 @@ receives a request for a URL http://servername/foo/dirname where dirname is a directory. Directories require a - trailing slash, so mod_dir issues a redirect to + trailing slash, so mod_dir issues a redirect to http://servername/foo/dirname/.

    -

    Directives

    DirectoryIndex Directive

    Description: - List of resources to look for when the client requests -a directory
    Syntax: - DirectoryIndex - local-url [local-url] ...
    Default: - DirectoryIndex index.html
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_dir
    +

    Directives

    top

    DirectoryIndex Directive

    Description: + List of resources to look for when the client requests +a directory
    Syntax: + DirectoryIndex + local-url [local-url] ...
    Default: + DirectoryIndex index.html
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_dir

    The DirectoryIndex directive sets the list of resources to look for, when the client requests an index of the directory by specifying a / at the end of the a directory @@ -49,9 +51,9 @@ a directory

    Example

    +

    Example

    DirectoryIndex index.html -

    +

    then a request for http://myserver/docs/ would return http://myserver/docs/index.html if it @@ -60,8 +62,8 @@ DirectoryIndex index.html

    Note that the documents do not need to be relative to the directory;

    -
    DirectoryIndex index.html index.txt /cgi-bin/index.pl
    +

    DirectoryIndex index.html index.txt /cgi-bin/index.pl

    would cause the CGI script /cgi-bin/index.pl to be executed if neither index.html or index.txt existed in a directory.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_dir.html.ja.jis b/docs/manual/mod/mod_dir.html.ja.jis index b2811d9e90..025489ee69 100644 --- a/docs/manual/mod/mod_dir.html.ja.jis +++ b/docs/manual/mod/mod_dir.html.ja.jis @@ -1,62 +1,64 @@ -mod_dir - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mod_dir

    $B@bL@(B: - $B!V:G8e$N%9%i%C%7%e!W$N%j%@%$%l%/%H$H!"%G%#(B$B%l%/%H%j$N(B -$B%$%s%G%C%/%9%U%!%$%k$r07$&5!G=$rDs6!$9$k(B
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<(B$B%k<1JL;R(B: - dir_module

    $B35MW(B

    -

    $B%G%#%l%/%H(B$B%j%$%s%G%C%/%9$O!" + -->mod_dir - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mod_dir

    $B@bL@(B: + $B!V:G8e$N%9%i%C%7%e!W$N%j%@%$%l%/%H$H!"%G%#%l%/%H%j$N(B +$B%$%s%G%C%/%9%U%!%$%k$r07$&5!G=$rDs6!$9$k(B
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k<1JL;R(B: + dir_module

    $B35MW(B

    +

    $B%G%#%l%/%H%j%$%s%G%C%/%9$O!"

    • $B0l$DL\$O!"%f!<%6$,:n@.$7$?%U%!%$%k$rMQ$$$k$b$N$G!"DL>o(B index.html $B$H$$$&%U%!%$%kL>$r;H$$$^$9!#$3$N%U%!%$%kL>$O!"(B - DirectoryIndex $B%G%#%l%/%F%#%V$G(B - $B;XDj$9$k$3$H$,$G$-$^$9!#$3$N(B$B5!G=$O(B mod_dir + DirectoryIndex $B%G%#%l%/%F%#%V$G(B + $B;XDj$9$k$3$H$,$G$-$^$9!#$3$N5!G=$O(B mod_dir $B%b%8%e!<%k$GDs6!$5$l$^$9!#(B
    • $B$b$&0l$D$NJ}K!$O!"(B $B%5!<%P$K$h$C$F<+F0E*$K@8@.$5$l$k%G%#%l%/%H%j%j%9%H$rMQ$$$k>l9g$G$9!#(B - $B$3$N5!G=$O!"(Bmod_autoindex - $B%b%8%e!<%k$K(B$B$h$jDs6!$5$l$^$9!#(B
      • + $B$3$N5!G=$O!"(Bmod_autoindex + $B%b%8%e!<%k$K$h$jDs6!$5$l$^$9!#(B

    $B<+F0E*$J%$%s%G%C%/%9@8@.5!G=$r:o=|(B ($B$b$7$/$O8r49(B) $B$G$-$k$h$&$K!"$3$NFs$D$N5!G=$OJ,N%$5$l$F$$$^$9!#(B

    $B$J$*(B http://servername/foo/dirname $B$H$$$&(B URL - $B$X$N(B$B%j%/%(%9%H$,$"$C$?:]$K!"(Bdirname + $B$X$N%j%/%(%9%H$,$"$C$?:]$K!"(Bdirname $B$H$$$&%G%#%l%/%H%j$,$"$l$P!"!V:G8e$K%9%i%C%7%e$r$D$1$?7A!W$N(B URL $B$X$N%j%@%$%l%/%H$rAw=P$7$^$9!#(B $B%G%#%l%/%H%j$X$N%"%/%;%9$O%9%i%C%7%e$G=*$o$C$F$$$kI,MW$,$"$j!"(B mod_dir $B$O!"(Bhttp://servername/foo/dirname/ $B$X$N%j%@%$%l%/%H$rAw=P$9$k$3$H$K$J$j$^$9!#(B

    -

    $B%G%#%l%/%F%#%V(B

    DirectoryIndex $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%/%i%$%"%s%H$,%G%#%l%/%H%j$r%j%/%(%9%H$7$?$H$-$KD4$Y$k(B -$B%j%=!<%9$N%j%9%H(B
    $B9=J8(B: - DirectoryIndex - local-url [local-url] ...
    $B%G%U%)%k%H(B: - DirectoryIndex index.html
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - Indexes
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_dir
    +

    $B%G%#%l%/%F%#%V(B

    top

    DirectoryIndex $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%/%i%$%"%s%H$,%G%#%l%/%H%j$r%j%/%(%9%H$7$?$H$-$KD4$Y$k(B +$B%j%=!<%9$N%j%9%H(B
    $B9=J8(B: + DirectoryIndex + local-url [local-url] ...
    $B%G%U%)%k%H(B: + DirectoryIndex index.html
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + Indexes
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_dir

    $B%/%i%$%"%s%H$,!"%G%#%l%/%H%jL>$N:G8e$K!V(B/$B!W(B $B$r;XDj$7$F%G%#%l%/%H%j%$%s%G%C%/%9$rMW5a$9$k>l9g$KC5$9%j%=!<%9$N%j%9%H$r(B DirectoryIndex $B%G%#%l%/%F%#%V$G@_Dj$7$^$9!#(B Local-url - $B$O!"%j%/%(%9%H$5$l$?%G%#%l%/%H%j$KBP1~$9$k!"%5!<%P>e$N%I(B$B%-%e%a%s%H$N(B + $B$O!"%j%/%(%9%H$5$l$?%G%#%l%/%H%j$KBP1~$9$k!"%5!<%P>e$N%I%-%e%a%s%H$N(B (% $B%(%s%3!<%I$5$l$?(B) URL $B$G!"IaDL$O%G%#%l%/%H%jCf$N%U%!%$%k$NL>A0$G$9!#(B $BJ#?t$N(B URL $B$,@_Dj$5$l$?>l9g$K$O!":G=i$K8+$D$+$C$?$b$N$rJV$7$^$9!#(B $B$=$l$i$,8+$D$+$i$:!"(BIndexes $B%*%W%7%g%s$,%;%C%H$5$l$F$$$k>l9g!"%G%#%l%/%H%j$N%j%9%H$r@8@.$7$^$9!#(B

    -

    $BNc(B

    +

    $BNc(B

    DirectoryIndex index.html -

    +

    http://myserver/docs/ $B$X$N%"%/%;%9$,$"$j!"(B http://myserver/docs/index.html @@ -66,8 +68,8 @@ DirectoryIndex index.html

    $BCm(B: $B%I%-%e%a%s%H$,F1$8%G%#%l%/%H%jFb$KB8:_$9$k$OI,MW$"$j$^$;$s!#(B

    -
    DirectoryIndex index.html index.txt /cgi-bin/index.pl
    +

    DirectoryIndex index.html index.txt /cgi-bin/index.pl

    $B$H$7$?>l9g!"(Bindex.html $B$H(B index.txt $B$N$I$A$i$b%G%#%l%/%H%jFb$KB8:_$7$J$$>l9g!"(BCGI $B%9%/%j%W%H(B - /cgi-bin/index.pl $B$, -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file + /cgi-bin/index.pl $B$, + \ No newline at end of file diff --git a/docs/manual/mod/mod_disk_cache.html.en b/docs/manual/mod/mod_disk_cache.html.en index 8e9fb07ea3..3305124c6e 100644 --- a/docs/manual/mod/mod_disk_cache.html.en +++ b/docs/manual/mod/mod_disk_cache.html.en @@ -1,201 +1,203 @@ -mod_disk_cache - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_disk_cache

    Description: - Content cache keyed to URIs
    Status: - Experimental
    Module Identifier: - disk_cache_module

    Summary

    + -->mod_disk_cache - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_disk_cache

    Description: + Content cache keyed to URIs
    Status: + Experimental
    Module Identifier: + disk_cache_module

    Summary

    -
    +
    This module is experimental. Documentation is still under development... -
    -

    mod_disk_cache implements a disk based storage manager for use with mod_proxy.

    +
    +

    mod_disk_cache implements a disk based storage manager for use with mod_proxy.

    Content stored and retrived keyed to the URL. Content with access protections is not cached.

    -
    -

    mod_disk_cache requires the services of mod_cache.

    -
    -

    Directives

    CacheDirLength Directive

    Description: - The number of characters in subdirectory names
    Syntax: - CacheDirLength length
    Default: - CacheDirLength 2
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +
    +

    mod_disk_cache requires the services of mod_cache.

    +
    +
    top

    CacheDirLength Directive

    Description: + The number of characters in subdirectory names
    Syntax: + CacheDirLength length
    Default: + CacheDirLength 2
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache

    The CacheDirLength directive sets the number of characters for each subdirectory in the cache

    -
    +

    CacheDirLevels*CacheDirLength value must not be higher than 20.

    -
    -
    - CacheDirLength 4
    -
    -

    CacheDirLevels Directive

    Description: - The number of levels of subdirectories in the cache
    Syntax: - CacheDirLevels levels
    Default: - CacheDirLevels 3
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +
    +

    + CacheDirLength 4
    +

    +
    top

    CacheDirLevels Directive

    Description: + The number of levels of subdirectories in the cache
    Syntax: + CacheDirLevels levels
    Default: + CacheDirLevels 3
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache

    The CacheDirLevels directive sets the number of subdirectory levels in the cache. Cached data will be saved this many directory levels below CacheRoot

    -
    +

    CacheDirLevels*CacheDirLength value must not be higher than 20.

    -
    -
    - CacheDirLevels 5
    -
    -

    CacheExpiryCheck Directive

    Description: - On if cache observes Expires date when seeking files
    Syntax: - CacheExpiryCheck binary
    Default: - CacheExpiryCheck ?
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +
    +

    + CacheDirLevels 5
    +

    +
    top

    CacheExpiryCheck Directive

    Description: + On if cache observes Expires date when seeking files
    Syntax: + CacheExpiryCheck binary
    Default: + CacheExpiryCheck ?
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache
    -
    - CacheExpiryCheck On
    -
    -
    +

    + CacheExpiryCheck On
    +

    +
    The CacheExpiryCheck directive is currently not implemented. -
    -

    CacheGcClean Directive

    Description: - The time in hours to retain unchanged files that match a url
    Syntax: - CacheGcClean hours
    Default: - CacheGcClean ?
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +
    +
    top

    CacheGcClean Directive

    Description: + The time in hours to retain unchanged files that match a url
    Syntax: + CacheGcClean hours
    Default: + CacheGcClean ?
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache
    -
    - CacheGcClean
    -
    -
    +

    + CacheGcClean
    +

    +
    The CacheGcClean directive is currently not implemented. -
    -

    CacheGcDaily Directive

    Description: - The time of day for garbage collection (24 hour clock)
    Syntax: - CacheGcDaily time
    Default: - CacheGcDaily ?
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +
    +
    top

    CacheGcDaily Directive

    Description: + The time of day for garbage collection (24 hour clock)
    Syntax: + CacheGcDaily time
    Default: + CacheGcDaily ?
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache
    -
    - CacheGcDaily
    -
    -
    +

    + CacheGcDaily
    +

    +
    The CacheGcDaily directive is currently not implemented. -
    -

    CacheGcInterval Directive

    Description: - The interval between garbage collections
    Syntax: - CacheGcInterval hours
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +
    +
    top

    CacheGcInterval Directive

    Description: + The interval between garbage collections
    Syntax: + CacheGcInterval hours
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache
    -
    - CacheGcInterval 24
    -
    -
    +

    + CacheGcInterval 24
    +

    +
    The CacheGcInterval directive is currently not implemented. -
    -

    CacheGcMemUsage Directive

    Description: - The maximum kilobytes of memory used for garbage collection
    Syntax: - CacheGcMemUsage KBytes
    Default: - CacheGcMemUsage ?
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +
    +
    top

    CacheGcMemUsage Directive

    Description: + The maximum kilobytes of memory used for garbage collection
    Syntax: + CacheGcMemUsage KBytes
    Default: + CacheGcMemUsage ?
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache
    -
    - CacheGcMemUsage
    -
    -
    +

    + CacheGcMemUsage
    +

    +
    The CacheGcMemUsage directive is currently not implemented. -
    -

    CacheGcUnused Directive

    Description: - The time in hours to retain unused file that match a url
    Syntax: - CacheGcUnused hours
    Default: - CacheGcUnused ?
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +
    +
    top

    CacheGcUnused Directive

    Description: + The time in hours to retain unused file that match a url
    Syntax: + CacheGcUnused hours
    Default: + CacheGcUnused ?
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache
    -
    - CacheGcUnused
    -
    -
    +

    + CacheGcUnused
    +

    +
    The CacheGcUnused directive is currently not implemented. -
    -

    CacheMaxFileSize Directive

    Description: - The maximum size (in bytes) of a file to be placed in the cache
    Syntax: - CacheMaxFileSize bytes
    Default: - CacheMaxFileSize 1000000
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +
    +
    top

    CacheMaxFileSize Directive

    Description: + The maximum size (in bytes) of a file to be placed in the cache
    Syntax: + CacheMaxFileSize bytes
    Default: + CacheMaxFileSize 1000000
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache

    The CacheMaxFileSize directive sets the maximum size in bytes of a file to be cached.

    -
    - CacheMaxFileSize 64000
    -
    -

    CacheMinFileSize Directive

    Description: - The minimum size (in bytes) of a file to be placed in the cache
    Syntax: - CacheMinFileSize bytes
    Default: - CacheMinFileSize 1
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +

    + CacheMaxFileSize 64000
    +

    +
    top

    CacheMinFileSize Directive

    Description: + The minimum size (in bytes) of a file to be placed in the cache
    Syntax: + CacheMinFileSize bytes
    Default: + CacheMinFileSize 1
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache

    The CacheMinFileSize directive sets the minimum size in bytes of a file to be cached.

    -
    - CacheMinFileSize 64
    -
    -

    CacheRoot Directive

    Description: - The directory to store cache files
    Syntax: - CacheRoot directory
    Default: - none
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +

    + CacheMinFileSize 64
    +

    +
    top

    CacheRoot Directive

    Description: + The directory to store cache files
    Syntax: + CacheRoot directory
    Default: + none
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache

    The CacheRoot directive defines the name of the directory on the disk to contain cache files. What is happening if not set ?

    -
    - CacheRoot c:/cacheroot
    -
    -

    CacheSize Directive

    Description: - The maximum amount of disk space that will be used by the cache in KBytes
    Syntax: - CacheSize KBytes
    Default: - CacheSize 1000000
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +

    + CacheRoot c:/cacheroot
    +

    +
    top

    CacheSize Directive

    Description: + The maximum amount of disk space that will be used by the cache in KBytes
    Syntax: + CacheSize KBytes
    Default: + CacheSize 1000000
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache

    The MCacheSize directive sets the desired disk space usage of the cache, in KBytes (1024-byte units). This directive does not put a hard limit on the size of the cache. The garbage collector will delete files until the usage is at or below the settings. Always use a value that is lower than the available disk space.

    -
    - MCacheSize 5000000
    -
    -

    CacheTimeMargin Directive

    Description: - The minimum time margin to cache a document
    Syntax: - CacheTimeMargin ?
    Default: - CacheTimeMargin ?
    Context: - server config
    Status: - Experimental
    Module: - mod_disk_cache
    +

    + MCacheSize 5000000
    +

    +
    top

    CacheTimeMargin Directive

    Description: + The minimum time margin to cache a document
    Syntax: + CacheTimeMargin ?
    Default: + CacheTimeMargin ?
    Context: + server config
    Status: + Experimental
    Module: + mod_disk_cache
    -
    - CacheTimeMargin
    -
    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    + CacheTimeMargin
    +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_echo.html.en b/docs/manual/mod/mod_echo.html.en index a9f5f98ffe..f5581fdfdd 100644 --- a/docs/manual/mod/mod_echo.html.en +++ b/docs/manual/mod/mod_echo.html.en @@ -1,30 +1,32 @@ -mod_echo - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_echo

    Description: - A simple echo server to illustrate protocol -modules
    Status: - Experimental
    Module Identifier: - echo_module
    Compatibility: - Available in Apache 2.0 and later

    Summary

    + -->mod_echo - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_echo

    Description: + A simple echo server to illustrate protocol +modules
    Status: + Experimental
    Module Identifier: + echo_module
    Compatibility: + Available in Apache 2.0 and later

    Summary

    This module provides an example protocol module to illustrate the concept. It provides a simple echo server. Telnet to it and type stuff, and it will echo it.

    -

    Directives

    ProtocolEcho Directive

    Description: - Turn the echo server on or off
    Syntax: - ProtocolEcho On|Off
    Context: - server config, virtual host
    Status: - Experimental
    Module: - mod_echo
    Compatibility: - ProtocolEcho is only available in 2.0 and -later.
    +

    Directives

    top

    ProtocolEcho Directive

    Description: + Turn the echo server on or off
    Syntax: + ProtocolEcho On|Off
    Context: + server config, virtual host
    Status: + Experimental
    Module: + mod_echo
    Compatibility: + ProtocolEcho is only available in 2.0 and +later.

    The ProtocolEcho directive enables or disables the echo server.

    -

    Example

    +

    Example

    ProtocolEcho On -

    +

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_env.html.en b/docs/manual/mod/mod_env.html.en index 3dac926e83..7eb2f9ec4e 100644 --- a/docs/manual/mod/mod_env.html.en +++ b/docs/manual/mod/mod_env.html.en @@ -1,53 +1,55 @@ -mod_env - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_env

    Description: - Modifies the environment which is - passed to CGI scripts and SSI pages
    Status: - Base
    Module Identifier: - env_module

    Summary

    + -->mod_env - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_env

    Description: + Modifies the environment which is + passed to CGI scripts and SSI pages
    Status: + Base
    Module Identifier: + env_module

    Summary

    This module allows for control of the environment that will be provided to CGI scripts and SSI pages. Environment variables may be passed from the shell which invoked the httpd process. Alternatively, environment variables may be set or unset within the configuration process.

    -

    Directives

    See also

    PassEnv Directive

    Description: - Passes environment variables from the shell
    Syntax: - PassEnv - env-variable [env-variable] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_env
    +
    top

    PassEnv Directive

    Description: + Passes environment variables from the shell
    Syntax: + PassEnv + env-variable [env-variable] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_env

    Specifies one or more environment variables to pass to CGI scripts and SSI pages from the environment of the shell which invoked the httpd process. Example:

    -
    +

    PassEnv LD_LIBRARY_PATH -

    -

    SetEnv Directive

    Description: - Sets environment variables
    Syntax: - SetEnv env-variable value
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_env
    +

    +
    top

    SetEnv Directive

    Description: + Sets environment variables
    Syntax: + SetEnv env-variable value
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_env

    Sets an environment variable, which is then passed on to CGI scripts and SSI pages. Example:

    -
    +

    SetEnv SPECIAL_PATH /foo/bin -

    -

    UnsetEnv Directive

    Description: - Removes variables from the environment
    Syntax: - UnsetEnv env-variable [env-variable] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_env
    +

    +
    top

    UnsetEnv Directive

    Description: + Removes variables from the environment
    Syntax: + UnsetEnv env-variable [env-variable] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_env

    Removes one or more environment variables from those passed on to CGI scripts and SSI pages. Example:

    -
    +

    UnsetEnv LD_LIBRARY_PATH -

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_env.html.ja.jis b/docs/manual/mod/mod_env.html.ja.jis index 836a68e1a5..9aa7f1d584 100644 --- a/docs/manual/mod/mod_env.html.ja.jis +++ b/docs/manual/mod/mod_env.html.ja.jis @@ -1,54 +1,56 @@ -mod_env - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mod_env

    $B@bL@(B: - CGI $B%9%/%j%W%H5Z$S(B SSI - $B%Z!<%8$KEO$5$l$k4D6-JQ?t$rJQ99$9$k5!G=$rDs6!$9$k(B
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<(B$B%k<1JL;R(B: - env_module

    $B35MW(B

    + -->mod_env - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mod_env

    $B@bL@(B: + CGI $B%9%/%j%W%H5Z$S(B SSI + $B%Z!<%8$KEO$5$l$k4D6-JQ?t$rJQ99$9$k5!G=$rDs6!$9$k(B
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k<1JL;R(B: + env_module

    $B35MW(B

    $B$3$N%b%8%e!<%k$K$h$j(B CGI $B%9%/%j%W%H$H(B SSI - $B%Z(B$B!<%8$KE,MQ$5$l$k4D6-JQ?t$r@)8f$9$k$3$H$,$G$-$k$h$&$K$J$j$^$9!#(B + $B%Z!<%8$KE,MQ$5$l$k4D6-JQ?t$r@)8f$9$k$3$H$,$G$-$k$h$&$K$J$j$^$9!#(B $B4D6-JQ?t$O(B httpd $B%W%m%;%9$r5/F0$7$?%7%'%k$+$iEO$5$l$^$9!#$^$?!"(B $B@_Dj%U%!%$%k$G4D6-JQ?t$r@_Dj$7$?$j!":o=|$7$?$j$9$k$3$H$,$G$-$^$9!#(B

    -

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    PassEnv $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%7%'%k$+$i$N4D6-JQ?t$rEO$9(B
    $B9=J8(B: - PassEnv - env-variable [env-variable] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - FileInfo
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_env
    +

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    top

    PassEnv $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%7%'%k$+$i$N4D6-JQ?t$rEO$9(B
    $B9=J8(B: + PassEnv + env-variable [env-variable] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + FileInfo
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_env

    httpd $B%W%m%;%9$r5/F0$7$?%7%'%k$N4D6-$+$i(B CGI $B%9%/%j%W%H$H(B SSI $B%Z!<%8$KEO$94D6-JQ?t$r0l$D0J>e;XDj$7$^$9!#Nc(B:

    -
    +

    PassEnv LD_LIBRARY_PATH -

    -

    SetEnv $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B4D6-JQ?t$r@_Dj$9$k(B
    $B9=J8(B: - SetEnv env-variable value
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - FileInfo
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_env
    +

    +
    top

    SetEnv $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B4D6-JQ?t$r@_Dj$9$k(B
    $B9=J8(B: + SetEnv env-variable value
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + FileInfo
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_env

    $B4D6-JQ?t$r@_Dj$7!"$=$l$r(B CGI $B%9%/%j%W%H$H(B SSI $B%Z!<%8$KEO$9$h$&$K$7$^$9!#Nc(B:

    -
    +

    SetEnv SPECIAL_PATH /foo/bin -

    -

    UnsetEnv $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B4D6-$+$iJQ?t$r
    $B9=J8(B: - UnsetEnv env-variable [env-variable] ...
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: - FileInfo
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_env
    +

    +
    top

    UnsetEnv $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B4D6-$+$iJQ?t$r
    $B9=J8(B: + UnsetEnv env-variable [env-variable] ...
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B, $B%G%#%l%/%H%j(B, .htaccess
    $B>e=q$-(B: + FileInfo
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_env

    CGI $B%9%/%j%W%H$H(B SSI $B%Z!<%8$KEO$5$l$k4D6-JQ?t$+$i;XDj$5$l$?4D6-JQ?t$r -

    +

    UnsetEnv LD_LIBRARY_PATH -

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_example.html.en b/docs/manual/mod/mod_example.html.en index 3291f27354..f3eb13e75b 100644 --- a/docs/manual/mod/mod_example.html.en +++ b/docs/manual/mod/mod_example.html.en @@ -1,17 +1,19 @@ -mod_example - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_example

    Description: - Illustrates the Apache module API
    Status: - Experimental
    Module Identifier: - example_module

    Summary

    -
    + -->mod_example - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_example

    Description: + Illustrates the Apache module API
    Status: + Experimental
    Module Identifier: + example_module

    Summary

    +
    This document has not been updated to take into account changes made in the 2.0 version of the Apache HTTP Server. Some of the information may still be relevant, but please use it with care. -
    +

    The files in the src/modules/example directory under the Apache distribution directory tree are provided as an @@ -28,7 +30,7 @@ location, and then browse to that location, you will see a display of some of the tracing the example module did as the various callbacks were made.

    -

    Directives

    Compiling the example module

    +

    Directives

    Topics

    • Compiling the example module
    • Using the mod_example Module
    top

    Compiling the example module

    To include the example module in your server, follow the steps below:

    @@ -38,13 +40,13 @@ Uncomment the "AddModule modules/example/mod_example" line near the bottom of the src/Configuration file. If there isn't one, add it; it should look like this: -
    +

    AddModule modules/example/mod_example.o -

    +

  • Run the src/Configure script - ("cd src; ./Configure"). This will + ("cd src; ./Configure"). This will build the Makefile for the server itself, and update the src/modules/Makefile for any additional modules you have requested from beneath that subdirectory.
    • @@ -55,7 +57,7 @@

    To add another module of your own:

    -
      +
      1. mkdir src/modules/mymodule
      2. cp src/modules/example/* @@ -66,32 +68,32 @@
      3. Follow steps [1] through [3] above, with appropriate changes.
      -

      Using the mod_example Module

      +
      top

      Using the mod_example Module

      To activate the example module, include a block similar to the following in your srm.conf file:

      -
      - <Location /example-info>
      - SetHandler example-handler
      +

      + <Location /example-info>
      + SetHandler example-handler
      </Location> -

      +

      As an alternative, you can put the following into a .htaccess file and then request the file "test.example" from that location:

      -
      +

      AddHandler example-handler .example -

      +

      After reloading/restarting your server, you should be able to browse to this location and see the brief display mentioned earlier.

      -

      Example Directive

      Description: - Demonstration directive to illustrate the Apache module -API
      Syntax: - Example
      Context: - server config, virtual host, directory, .htaccess
      Status: - Experimental
      Module: - mod_example
      +
      top

      Example Directive

      Description: + Demonstration directive to illustrate the Apache module +API
      Syntax: + Example
      Context: + server config, virtual host, directory, .htaccess
      Status: + Experimental
      Module: + mod_example

      The Example directive just sets a demonstration flag which the example module's content handler displays. It takes no arguments. If you browse to an URL to which the @@ -100,4 +102,4 @@ APIExample directive declared here: YES/NO".

      -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_expires.html.en b/docs/manual/mod/mod_expires.html.en index 3df7c15f9b..f20f454fdd 100644 --- a/docs/manual/mod/mod_expires.html.en +++ b/docs/manual/mod/mod_expires.html.en @@ -1,13 +1,15 @@ -mod_expires - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_expires

    Description: - Generation of + -->mod_expires - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_expires

    Description: + Generation of Expires HTTP headers according to user-specified - criteria
    Status: - Extension
    Module Identifier: - expires_module

    Summary

    + criteria
    Status: + Extension
    Module Identifier: + expires_module

    Summary

    This module controls the setting of the Expires HTTP header in server responses. The expiration date can set to be relative to either the time the source file was last @@ -19,19 +21,20 @@ from the source until this time has passed. After that, the cache copy is considered "expired" and invalid, and a new copy must be obtained from the source.

    -

    Directives

    Alternate Interval +
    top

    Alternate Interval Syntax

    -

    The ExpiresDefault and - ExpiresByType directives +

    The ExpiresDefault and + ExpiresByType directives can also be defined in a more readable syntax of the form:

    -
    +

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

    +

    where <base> is one of:

    @@ -68,33 +71,33 @@ make documents expire 1 month after being accessed, by default:

    -
    - ExpiresDefault "access plus 1 month"
    - ExpiresDefault "access plus 4 weeks"
    +

    + ExpiresDefault "access plus 1 month"
    + ExpiresDefault "access plus 4 weeks"
    ExpiresDefault "access plus 30 days" -

    +

    The expiry time can be fine-tuned by adding several '<num> <type>' clauses:

    -
    +

    ExpiresByType text/html "access plus 1 month 15 - days 2 hours"
    + days 2 hours"
    ExpiresByType image/gif "modification plus 5 hours 3 minutes" -

    +

    Note that if you use a modification date based setting, the Expires header will not be added to content that does not come from a file on disk. This is due to the fact that there is no modification time for such content.

    -

    ExpiresActive Directive

    Description: - Enables generation of Expires headers
    Syntax: - ExpiresActive On|Off
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Extension
    Module: - mod_expires
    +
    top

    ExpiresActive Directive

    Description: + Enables generation of Expires headers
    Syntax: + ExpiresActive On|Off
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Extension
    Module: + mod_expires

    This directive enables or disables the generation of the Expires header for the document realm in question. (That is, if found in an .htaccess file, for @@ -105,23 +108,23 @@ ExpiresByType text/html "access plus 1 month 15 .htaccess file overriding a server config file). If set to On, the header will be added to served documents according to the criteria defined by the - ExpiresByType and - ExpiresDefault directives + ExpiresByType and + ExpiresDefault directives (q.v.).

    Note that this directive does not guarantee that an Expires header will be generated. If the criteria aren't met, no header will be sent, and the effect will be as though this directive wasn't even specified.

    -

    ExpiresByType Directive

    Description: - Value of the Expires header configured -by MIME type
    Syntax: - ExpiresByType - MIME-type <code>seconds
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Extension
    Module: - mod_expires
    +
    top

    ExpiresByType Directive

    Description: + Value of the Expires header configured +by MIME type
    Syntax: + ExpiresByType + MIME-type <code>seconds
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Extension
    Module: + mod_expires

    This directive defines the value of the Expires header generated for documents of the specified type (e.g., text/html). The second argument @@ -147,35 +150,35 @@ by MIME type -# enable expirations
    -ExpiresActive On
    -# expire GIF images after a month in the client's cache
    -ExpiresByType image/gif A2592000
    -# HTML documents are good for a week from the time they were changed
    +

    +# enable expirations
    +ExpiresActive On
    +# expire GIF images after a month in the client's cache
    +ExpiresByType image/gif A2592000
    +# HTML documents are good for a week from the time they were changed
    ExpiresByType text/html M604800 -

    +

    Note that this directive only has effect if ExpiresActive On has been specified. It overrides, for the specified MIME type only, any expiration date - set by the ExpiresDefault + set by the ExpiresDefault directive.

    You can also specify the expiration time calculation using an alternate syntax, described earlier in this document.

    -

    ExpiresDefault Directive

    Description: - Default algorithm for calculating expiration time
    Syntax: - ExpiresDefault <code>seconds
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Extension
    Module: - mod_expires
    +
    top

    ExpiresDefault Directive

    Description: + Default algorithm for calculating expiration time
    Syntax: + ExpiresDefault <code>seconds
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Extension
    Module: + mod_expires

    This directive sets the default algorithm for calculating the expiration time for all documents in the affected realm. It can be - overridden on a type-by-type basis by the ExpiresByType directive. See the + overridden on a type-by-type basis by the ExpiresByType directive. See the description of that directive for details about the syntax of the argument, and the alternate syntax description as well.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +
    \ No newline at end of file diff --git a/docs/manual/mod/mod_ext_filter.html.en b/docs/manual/mod/mod_ext_filter.html.en index 9fff06cb2c..8b76809bde 100644 --- a/docs/manual/mod/mod_ext_filter.html.en +++ b/docs/manual/mod/mod_ext_filter.html.en @@ -1,21 +1,23 @@ -mod_ext_filter - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_ext_filter

    Description: - Pass the response body + -->mod_ext_filter - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_ext_filter

    Description: + Pass the response body through an external program before delivery to the - client
    Status: - Experimental
    Module Identifier: - ext_filter_module

    Summary

    + client
    Status: + Experimental
    Module Identifier: + ext_filter_module

    Summary

    This is an experimental module and should - be used with care. Test your mod_ext_filter + be used with care. Test your mod_ext_filter configuration carefully to ensure that it performs the desired function. You may wish to review this information for background on the Apache filtering model.

    -

    mod_ext_filter presents a simple and familiar +

    mod_ext_filter presents a simple and familiar programming model for filters. With this module, a program which reads from stdin and writes to stdout (i.e., a Unix-style filter command) can be a filter for Apache. This filtering @@ -35,120 +37,111 @@

    Even when the performance characteristics are not suitable - for production use, mod_ext_filter can be used as + for production use, mod_ext_filter can be used as a prototype environment for filters.

    -

    Directives

    Examples

    +

    Directives

    Topics

    • Examples
    top

    Examples

    Generating HTML from some other type of response

    -
    -
    -    # mod_ext_filter directive to define a filter to HTML-ize text/c files 
-    # using the external program /usr/bin/enscript, with the type of the 
-    # result set to text/html
-    ExtFilterDefine c-to-html mode=output intype=text/c outtype=text/html \
-                    cmd="/usr/bin/enscript --color -W html -Ec -o - -"
+
    +# mod_ext_filter directive to define a filter to HTML-ize text/c files 
+# using the external program /usr/bin/enscript, with the type of the 
+# result set to text/html
+ExtFilterDefine c-to-html mode=output intype=text/c outtype=text/html \
+                cmd="/usr/bin/enscript --color -W html -Ec -o - -"
 
-    <Directory "/export/home/trawick/apacheinst/htdocs/c">
+<Directory "/export/home/trawick/apacheinst/htdocs/c">
 
-    # core directive to cause the new filter to be run on output
-    SetOutputFilter c-to-html
+# core directive to cause the new filter to be run on output
+SetOutputFilter c-to-html
 
-    # mod_mime directive to set the type of .c files to text/c
-    AddType text/c .c
+# mod_mime directive to set the type of .c files to text/c
+AddType text/c .c
 
-    # mod_ext_filter directive to set the debug level just high 
-    # enough to see a log message per request showing the configuration
-    # in force
-    ExtFilterOptions DebugLevel=1
+# mod_ext_filter directive to set the debug level just high 
+# enough to see a log message per request showing the configuration
+# in force
+ExtFilterOptions DebugLevel=1
 
-    </Directory>
-
    
-
    +</Directory> +

    Implementing a content encoding filter

    -
    -
    -  # mod_ext_filter directive to define the external filter
-  ExtFilterDefine gzip mode=output cmd=/bin/gzip
+
    +# mod_ext_filter directive to define the external filter
+ExtFilterDefine gzip mode=output cmd=/bin/gzip
 
-  <Location /gzipped>
+<Location /gzipped>
 
-  # core directive to cause the gzip filter to be run on output
-  SetOutputFilter gzip
+# core directive to cause the gzip filter to be run on output
+SetOutputFilter gzip
 
-  # mod_header directive to add "Content-Encoding: gzip" header field
-  Header set Content-Encoding gzip
+# mod_header directive to add "Content-Encoding: gzip" header field
+Header set Content-Encoding gzip
 
-  </Location>
-
    
-
    +</Location> +

    Note: this gzip example is just for the purposes of illustration. - Please refer to mod_deflate for a practical + Please refer to mod_deflate for a practical implementation.

    Slowing down the server

    -
    -
    -  # mod_ext_filter directive to define a filter which runs everything 
-  # through cat; cat doesn't modify anything; it just introduces extra
-  # pathlength and consumes more resources
-  ExtFilterDefine slowdown mode=output cmd=/bin/cat preservescontentlength
+
    +# mod_ext_filter directive to define a filter which runs everything 
+# through cat; cat doesn't modify anything; it just introduces extra
+# pathlength and consumes more resources
+ExtFilterDefine slowdown mode=output cmd=/bin/cat preservescontentlength
 
-  <Location />
+<Location />
 
-  # core directive to cause the slowdown filter to be run several times on 
-  # output
-  SetOutputFilter slowdown slowdown slowdown
+# core directive to cause the slowdown filter to be run several times on 
+# output
+SetOutputFilter slowdown slowdown slowdown
 
-  </Location>
-
    
-
    +</Location> +

    Using sed to replace text in the response

    -
    -
    -  # mod_ext_filter directive to define a filter which replaces text in
-  # the response
-  ExtFilterDefine fixtext mode=output cmd="/bin/sed s/verdana/arial/g" intype=text/html
+
    +# mod_ext_filter directive to define a filter which replaces text in
+# the response
+ExtFilterDefine fixtext mode=output cmd="/bin/sed s/verdana/arial/g" intype=text/html
 
-  <Location />
+<Location />
 
-  # core directive to cause the fixtext filter to be run on output
-  # output
-  SetOutputFilter fixtext
+# core directive to cause the fixtext filter to be run on output
+# output
+SetOutputFilter fixtext
 
-  </Location>
-
    
-
    +</Location> +

    Tracing another filter

    -
    -
    -  # Trace the data read and written by mod_deflate for a particular
-  # client (IP 192.168.1.31) experiencing compression problems.
-  # This filter will trace what goes into mod_deflate.
-  ExtFilterDefine tracebefore cmd="/bin/tracefilter.pl /tmp/tracebefore" \
-    EnableEnv=trace_this_client
-  # This filter will trace what goes after mod_deflate.  Note that without
-  # the ftype parameter, the default filter type of AP_FTYPE_RESOURCE would
-  # cause the filter to be placed *before* mod_deflate in the filter 
-  # chain.  Giving it a numeric value slightly higher than 
-  # AP_FTYPE_CONTENT_SET will ensure that it is placed after mod_deflate.
-  ExtFilterDefine traceafter  cmd="/bin/tracefilter.pl /tmp/traceafter" \
-    EnableEnv=trace_this_client ftype=21
-
-  <Directory /usr/local/docs>
-    SetEnvIf Remote_Addr 192.168.1.31 trace_this_client
-    SetOutputFilter tracebefore;deflate;traceafter
-  </Directory>
-
    -Here is the filter which traces the data: -
    +
    +# Trace the data read and written by mod_deflate for a particular
+# client (IP 192.168.1.31) experiencing compression problems.
+# This filter will trace what goes into mod_deflate.
+ExtFilterDefine tracebefore cmd="/bin/tracefilter.pl /tmp/tracebefore" \
+  EnableEnv=trace_this_client
+# This filter will trace what goes after mod_deflate.  Note that without
+# the ftype parameter, the default filter type of AP_FTYPE_RESOURCE would
+# cause the filter to be placed *before* mod_deflate in the filter 
+# chain.  Giving it a numeric value slightly higher than 
+# AP_FTYPE_CONTENT_SET will ensure that it is placed after mod_deflate.
+ExtFilterDefine traceafter  cmd="/bin/tracefilter.pl /tmp/traceafter" \
+  EnableEnv=trace_this_client ftype=21
+
+<Directory /usr/local/docs>
+  SetEnvIf Remote_Addr 192.168.1.31 trace_this_client
+  SetOutputFilter tracebefore;deflate;traceafter
+</Directory>
+
    
+
+
    Here is the filter which traces the data:
     #!/usr/local/bin/perl -w
 
 use strict;
@@ -162,16 +155,15 @@ while (<STDIN>)
 }
 
 close(SAVE);
-
    
-
    + -

    ExtFilterDefine Directive

    Description: -
    Syntax: - ExtFilterDefine filtername parameters
    Context: - server config
    Status: - Experimental
    Module: - mod_ext_filter
    +
    top

    ExtFilterDefine Directive

    Description: +
    Syntax: + ExtFilterDefine filtername parameters
    Context: + server config
    Status: + Experimental
    Module: + mod_ext_filter

    The ExtFilterDefine directive defines the characteristics of an external filter, including the program to run and its arguments.

    @@ -255,14 +247,14 @@ close(SAVE); which must be set, or the filter will be disabled. -

    ExtFilterOptions Directive

    Description: -
    Syntax: - ExtFilterOptions - option [option] ...
    Default: - ExtFilterOptions DebugLevel=0 NoLogStderr
    Context: - directory
    Status: - Experimental
    Module: - mod_ext_filter
    +
    top

    ExtFilterOptions Directive

    Description: +
    Syntax: + ExtFilterOptions + option [option] ...
    Default: + ExtFilterOptions DebugLevel=0 NoLogStderr
    Context: + directory
    Status: + Experimental
    Module: + mod_ext_filter

    The ExtFilterOptions directive specifies special processing options for mod_ext_filter. Option can be one of

    @@ -294,12 +286,11 @@ close(SAVE); NoLogStderr disables this feature. -

    Example:

    -
    +

    Example

    ExtFilterOptions LogStderr DebugLevel=0 -

    +

    Messages written to the filter's standard error will be stored in the Apache error log. No debug messages will be generated by - mod_ext_filter.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + mod_ext_filter.

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_ext_filter.xml b/docs/manual/mod/mod_ext_filter.xml index 51895dafb9..9cc557f25a 100644 --- a/docs/manual/mod/mod_ext_filter.xml +++ b/docs/manual/mod/mod_ext_filter.xml @@ -39,56 +39,52 @@

    Even when the performance characteristics are not suitable - for production use, mod_ext_filter can be used as + for production use, mod_ext_filter can be used as a prototype environment for filters.

    Examples
    Generating HTML from some other type of response - -
    -    # mod_ext_filter directive to define a filter to HTML-ize text/c files 
-    # using the external program /usr/bin/enscript, with the type of the 
-    # result set to text/html
-    ExtFilterDefine c-to-html mode=output intype=text/c outtype=text/html \
-                    cmd="/usr/bin/enscript --color -W html -Ec -o - -"
+
    +# mod_ext_filter directive to define a filter to HTML-ize text/c files 
+# using the external program /usr/bin/enscript, with the type of the 
+# result set to text/html
+ExtFilterDefine c-to-html mode=output intype=text/c outtype=text/html \
+                cmd="/usr/bin/enscript --color -W html -Ec -o - -"
 
-    <Directory "/export/home/trawick/apacheinst/htdocs/c">
+<Directory "/export/home/trawick/apacheinst/htdocs/c">
 
-    # core directive to cause the new filter to be run on output
-    SetOutputFilter c-to-html
+# core directive to cause the new filter to be run on output
+SetOutputFilter c-to-html
 
-    # mod_mime directive to set the type of .c files to text/c
-    AddType text/c .c
+# mod_mime directive to set the type of .c files to text/c
+AddType text/c .c
 
-    # mod_ext_filter directive to set the debug level just high 
-    # enough to see a log message per request showing the configuration
-    # in force
-    ExtFilterOptions DebugLevel=1
+# mod_ext_filter directive to set the debug level just high 
+# enough to see a log message per request showing the configuration
+# in force
+ExtFilterOptions DebugLevel=1
 
-    </Directory>
-
    
-    
+</Directory>
+
    Implementing a content encoding filter - -
    -  # mod_ext_filter directive to define the external filter
-  ExtFilterDefine gzip mode=output cmd=/bin/gzip
+
    +# mod_ext_filter directive to define the external filter
+ExtFilterDefine gzip mode=output cmd=/bin/gzip
 
-  <Location /gzipped>
+<Location /gzipped>
 
-  # core directive to cause the gzip filter to be run on output
-  SetOutputFilter gzip
+# core directive to cause the gzip filter to be run on output
+SetOutputFilter gzip
 
-  # mod_header directive to add "Content-Encoding: gzip" header field
-  Header set Content-Encoding gzip
+# mod_header directive to add "Content-Encoding: gzip" header field
+Header set Content-Encoding gzip
 
-  </Location>
-
    
-    
+</Location>
+

    Note: this gzip example is just for the purposes of illustration. Please refer to mod_deflate for a practical @@ -96,64 +92,60 @@

    Slowing down the server - -
    -  # mod_ext_filter directive to define a filter which runs everything 
-  # through cat; cat doesn't modify anything; it just introduces extra
-  # pathlength and consumes more resources
-  ExtFilterDefine slowdown mode=output cmd=/bin/cat preservescontentlength
+
    +# mod_ext_filter directive to define a filter which runs everything 
+# through cat; cat doesn't modify anything; it just introduces extra
+# pathlength and consumes more resources
+ExtFilterDefine slowdown mode=output cmd=/bin/cat preservescontentlength
 
-  <Location />
+<Location />
 
-  # core directive to cause the slowdown filter to be run several times on 
-  # output
-  SetOutputFilter slowdown slowdown slowdown
+# core directive to cause the slowdown filter to be run several times on 
+# output
+SetOutputFilter slowdown slowdown slowdown
 
-  </Location>
-
    
-    
+</Location>
+
    Using sed to replace text in the response - -
    -  # mod_ext_filter directive to define a filter which replaces text in
-  # the response
-  ExtFilterDefine fixtext mode=output cmd="/bin/sed s/verdana/arial/g" intype=text/html
+
    +# mod_ext_filter directive to define a filter which replaces text in
+# the response
+ExtFilterDefine fixtext mode=output cmd="/bin/sed s/verdana/arial/g" intype=text/html
 
-  <Location />
+<Location />
 
-  # core directive to cause the fixtext filter to be run on output
-  # output
-  SetOutputFilter fixtext
+# core directive to cause the fixtext filter to be run on output
+# output
+SetOutputFilter fixtext
 
-  </Location>
-
    
-    
+</Location>
+
    Tracing another filter - -
    -  # Trace the data read and written by mod_deflate for a particular
-  # client (IP 192.168.1.31) experiencing compression problems.
-  # This filter will trace what goes into mod_deflate.
-  ExtFilterDefine tracebefore cmd="/bin/tracefilter.pl /tmp/tracebefore" \
-    EnableEnv=trace_this_client
-  # This filter will trace what goes after mod_deflate.  Note that without
-  # the ftype parameter, the default filter type of AP_FTYPE_RESOURCE would
-  # cause the filter to be placed *before* mod_deflate in the filter 
-  # chain.  Giving it a numeric value slightly higher than 
-  # AP_FTYPE_CONTENT_SET will ensure that it is placed after mod_deflate.
-  ExtFilterDefine traceafter  cmd="/bin/tracefilter.pl /tmp/traceafter" \
-    EnableEnv=trace_this_client ftype=21
-
-  <Directory /usr/local/docs>
-    SetEnvIf Remote_Addr 192.168.1.31 trace_this_client
-    SetOutputFilter tracebefore;deflate;traceafter
-  </Directory>
-
    -Here is the filter which traces the data: +
    +# Trace the data read and written by mod_deflate for a particular
+# client (IP 192.168.1.31) experiencing compression problems.
+# This filter will trace what goes into mod_deflate.
+ExtFilterDefine tracebefore cmd="/bin/tracefilter.pl /tmp/tracebefore" \
+  EnableEnv=trace_this_client
+# This filter will trace what goes after mod_deflate.  Note that without
+# the ftype parameter, the default filter type of AP_FTYPE_RESOURCE would
+# cause the filter to be placed *before* mod_deflate in the filter 
+# chain.  Giving it a numeric value slightly higher than 
+# AP_FTYPE_CONTENT_SET will ensure that it is placed after mod_deflate.
+ExtFilterDefine traceafter  cmd="/bin/tracefilter.pl /tmp/traceafter" \
+  EnableEnv=trace_this_client ftype=21
+
+<Directory /usr/local/docs>
+  SetEnvIf Remote_Addr 192.168.1.31 trace_this_client
+  SetOutputFilter tracebefore;deflate;traceafter
+</Directory>
+
     + +Here is the filter which traces the data: 
     #!/usr/local/bin/perl -w
 
@@ -168,8 +160,7 @@ while (<STDIN>)
 }
 
 close(SAVE);
-
    -     +
    @@ -305,8 +296,7 @@ close(SAVE); NoLogStderr disables this feature. -

    Example:

    - +Example ExtFilterOptions LogStderr DebugLevel=0 diff --git a/docs/manual/mod/mod_file_cache.html.en b/docs/manual/mod/mod_file_cache.html.en index 2131622ed4..eb7931bc64 100644 --- a/docs/manual/mod/mod_file_cache.html.en +++ b/docs/manual/mod/mod_file_cache.html.en @@ -1,17 +1,19 @@ -mod_file_cache - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_file_cache

    Description: - Caches a static list of files in memory
    Status: - Experimental
    Module Identifier: - file_cache_module

    Summary

    + -->mod_file_cache - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_file_cache

    Description: + Caches a static list of files in memory
    Status: + Experimental
    Module Identifier: + file_cache_module

    Summary

    -
    +
    This module should be used with care. You can easily create a broken site using mod_file_cache, so read this document carefully. -
    +

    Caching frequently requested files that change very infrequently is a technique for reducing server load. @@ -31,14 +33,14 @@ This module should be used with care. You can easily

    This module is an extension of and borrows heavily from the mod_mmap_static module in Apache 1.3.

    -

    Directives

    Using mod_file_cache

    +

    Directives

    Topics

    • Using mod_file_cache
    top

    Using mod_file_cache

    -

    mod_file_cache caches a list of statically - configured files via MMapFile or CacheFile directives in the +

    mod_file_cache caches a list of statically + configured files via MMapFile or CacheFile directives in the main server configuration.

    Not all platforms support both directives. For example, Apache - on Windows does not currently support the MMapStatic directive, while + on Windows does not currently support the MMapStatic directive, while other platforms, like AIX, support both. You will receive an error message in the server error log if you attempt to use an unsupported directive. If given an unsupported directive, the @@ -48,8 +50,8 @@ This module should be used with care. You can easily

    MmapFile Directive

    -

    The MmapFile - directive of mod_file_cache maps a list of +

    The MmapFile + directive of mod_file_cache maps a list of statically configured files into memory through the system call mmap(). This system call is available on most modern Unix derivates, but not on all. There are sometimes @@ -73,8 +75,8 @@ This module should be used with care. You can easily

    CacheFile Directive

    -

    The CacheFile - directive of mod_file_cache opens an active +

    The CacheFile + directive of mod_file_cache opens an active handle or file descriptor to the file (or files) listed in the configuration directive and places these open file handles in the cache. When the file is requested, the server @@ -95,24 +97,24 @@ This module should be used with care. You can easily mv do this.

    -

    Note

    Don't bother asking for a for a +

    Note

    Don't bother asking for a for a directive which recursively caches all the files in a directory. Try this instead... See the - Include directive, and consider + Include directive, and consider this command: -
    - find /www/htdocs -type f -print \
    +

    + find /www/htdocs -type f -print \
    | sed -e 's/.*/mmapfile &/' > /www/conf/mmap.conf -

    -
    - -

    CacheFile Directive

    Description: -
    Syntax: - CacheFile - file-path [file-path] ...
    Context: - server config
    Status: - Experimental
    Module: - mod_file_cache
    +

    + + +
    top

    CacheFile Directive

    Description: +
    Syntax: + CacheFile + file-path [file-path] ...
    Context: + server config
    Status: + Experimental
    Module: + mod_file_cache

    The CacheFile directive opens handles to one or more files (given as whitespace separated arguments) and places these handles into the cache at server startup @@ -126,18 +128,18 @@ This module should be used with care. You can easily 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.

    + with filenames rewritten by mod_alias or + mod_rewrite.

    -

    Example

    +

    Example

    CacheFile /usr/local/apache/htdocs/index.html -

    -

    MMapFile Directive

    Description: -
    Syntax: - MMapFile file-path [file-path] ...
    Context: - server config
    Status: - Experimental
    Module: - mod_file_cache
    +

    +
    top

    MMapFile Directive

    Description: +
    Syntax: + MMapFile file-path [file-path] ...
    Context: + server config
    Status: + Experimental
    Module: + mod_file_cache

    The MMapFile directive maps one or more files (given as whitespace separated arguments) into memory at server startup time. They are automatically unmapped on a server @@ -151,10 +153,10 @@ This module should be used with care. You can easily 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.

    + with filenames rewritten by mod_alias or + mod_rewrite.

    -

    Example

    +

    Example

    MMapFile /usr/local/apache/htdocs/index.html -

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_headers.html.en b/docs/manual/mod/mod_headers.html.en index da82a83236..58e8c42b60 100644 --- a/docs/manual/mod/mod_headers.html.en +++ b/docs/manual/mod/mod_headers.html.en @@ -1,17 +1,19 @@ -mod_headers - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_headers

    Description: - Customization of HTTP request - and response headers
    Status: - Extension
    Module Identifier: - headers_module
    Compatibility: - RequestHeader is available only in Apache 2.0

    Summary

    + -->mod_headers - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_headers

    Description: + Customization of HTTP request + and response headers
    Status: + Extension
    Module Identifier: + headers_module
    Compatibility: + RequestHeader is available only in Apache 2.0

    Summary

    This module provides directives to control and modify HTTP request and response headers. Headers can be merged, replaced or removed.

    -

    Directives

    Order of Processing

    +

    Directives

    Topics

    • Order of Processing
    • Example
    top

    Order of Processing

    The directives provided by mod_header can occur almost anywhere within the server configuration. They are valid in the @@ -36,22 +38,22 @@

    Order is important. These two headers have a different effect if reversed:

    -
    -RequestHeader append MirrorID "mirror 12"
    +

    +RequestHeader append MirrorID "mirror 12"
    RequestHeader unset MirrorID -

    +

    This way round, the MirrorID header is not set. If reversed, the MirrorID header is set to "mirror 12".

    -

    Example

    +
    top

    Example

    1. Copy all request headers that begin with "TS" to the response headers: -
      +

      Header echo ^TS* -

      2. +

  • Add a header, MyHeader, to the response including a timestamp for when the request was received and how long it @@ -59,24 +61,24 @@ RequestHeader append MirrorID "mirror 12"
    the client to intuit load on the server or in isolating bottlenecks between the client and the server. -
    +

    Header add MyHeader "%D %t" -

    +

    results in this header being added to the response: -
    +

    MyHeader: D=3775428 t=991424704447256 -

    +

  • Say hello to Joe -
    +

    Header add MyHeader "Hello Joe. It took %D microseconds for Apache to serve this request." -

    +

    results in this header being added to the response: -
    +

    MyHeader: Hello Joe. It took D=3775428 microseconds for Apache to serve this request. -

    +

  • Conditionally send MyHeader on the response if and only @@ -85,26 +87,26 @@ RequestHeader append MirrorID "mirror 12"
    stimulus. Note that this example requires the services of the mod_setenvif module. -
    - SetEnvIf MyRequestHeader value HAVE_MyRequestHeader
    +

    + SetEnvIf MyRequestHeader value HAVE_MyRequestHeader
    Header add MyHeader "%D %t mytext" env=HAVE_MyRequestHeader -

    +

    If the header "MyRequestHeader: value" is present on the HTTP request, the response will contain the following header: -
    +

    MyHeader: D=3775428 t=991424704447256 mytext -

    +

    • -

    Header Directive

    Description: - Configure HTTP response headers
    Syntax: - Header set|append|add|unset|echo header -[value]
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Extension
    Module: - mod_headers
    +
    top

    Header Directive

    Description: + Configure HTTP response headers
    Syntax: + Header set|append|add|unset|echo header +[value]
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Extension
    Module: + mod_headers

    This directive can replace, merge or remove HTTP response headers. The header is modified just after the content handler and output filters are run, allowing outgoing headers to be @@ -112,31 +114,31 @@ RequestHeader append MirrorID "mirror 12"
    argument. This can be one of the following values:

      -
    • set
      +
    • set
      The response header is set, replacing any previous header with this name. The value may be a format string.
      • -
    • append
      +
    • append
      The response header is appended to any existing header of the same name. When a new value is merged onto an existing header it is separated from the existing header with a comma. This is the HTTP standard way of giving a header multiple values.
      • -
    • add
      +
    • add
      The response header is added to the existing set of headers, even if this header already exists. This can result in two (or more) headers having the same name. This can lead to unforeseen consequences, and in general "append" should be used instead.
      • -
    • unset
      +
    • unset
      The response header of this name is removed, if it exists. If there are multiple headers of the same name, all will be removed.
      • -
    • echo
      +
    • echo
      Request headers with this name are echoed back in the response headers. header may be a regular expression.
      • @@ -182,14 +184,14 @@ variable FOOBAR. is sent to the network. These means that it is possible to set and/or override most headers, except for those headers added by the header filter.

      -

      RequestHeader Directive

      Description: - Configure HTTP request headers
      Syntax: - RequestHeader set|append|add|unset header -[value]
      Context: - server config, virtual host, directory, .htaccess
      Override: - FileInfo
      Status: - Extension
      Module: - mod_headers
      +
    top

    RequestHeader Directive

    Description: + Configure HTTP request headers
    Syntax: + RequestHeader set|append|add|unset header +[value]
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Extension
    Module: + mod_headers

    This directive can replace, merge or remove HTTP request headers. The header is modified just before the content handler is run, allowing incoming headers to be modified. The action it @@ -197,25 +199,25 @@ variable FOOBAR. of the following values:

      -
    • set
      +
    • set
      The request header is set, replacing any previous header with this name
      • -
    • append
      +
    • append
      The request header is appended to any existing header of the same name. When a new value is merged onto an existing header it is separated from the existing header with a comma. This is the HTTP standard way of giving a header multiple values.
      • -
    • add
      +
    • add
      The request header is added to the existing set of headers, even if this header already exists. This can result in two (or more) headers having the same name. This can lead to unforeseen consequences, and in general "append" should be used instead.
      • -
    • unset
      +
    • unset
      The request header of this name is removed, if it exists. If there are multiple headers of the same name, all will be removed.
      • @@ -232,4 +234,4 @@ variable FOOBAR. just before the request is run by its handler in the fixup phase. This should allow headers generated by the browser, or by Apache input filters to be overridden or modified.

      -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_imap.html.en b/docs/manual/mod/mod_imap.html.en index 8fe2a90914..ee80b1f998 100644 --- a/docs/manual/mod/mod_imap.html.en +++ b/docs/manual/mod/mod_imap.html.en @@ -1,31 +1,33 @@ -mod_imap - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_imap

    Description: - Server-side imagemap processing
    Status: - Base
    Module Identifier: - imap_module

    Summary

    + -->mod_imap - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_imap

    Description: + Server-side imagemap processing
    Status: + Base
    Module Identifier: + imap_module

    Summary

    This module processes .map files, thereby replacing the functionality of the imagemap CGI program. Any directory or document type configured to use the handler imap-file (using either - AddHandler or - SetHandler) + AddHandler or + SetHandler) will be processed by this module.

    The following directive will activate files ending with .map as imagemap files:

    -
    AddHandler imap-file map
    +

    AddHandler imap-file map

    Note that the following is still supported:

    -
    AddType application/x-httpd-imap map
    +

    AddType application/x-httpd-imap map

    However, we are trying to phase out "magic MIME types" so we are deprecating this method.

    -

    Directives

    New Features

    +

    Directives

    Topics

    • New Features
    • Imagemap File
    • Example Mapfile
    • Referencing your mapfile
    top

    New Features

    The imagemap module adds some new features that were not possible with previously distributed imagemap programs.

    @@ -42,16 +44,16 @@
  • Configurable generation of imagemap menus.
    • -

    Imagemap File

    +
    top

    Imagemap File

    The lines in the imagemap files can have one of several formats:

    -
    - directive value [x,y ...]
    - directive value "Menu text" [x,y ...]
    +

    + directive value [x,y ...]
    + directive value "Menu text" [x,y ...]
    directive value x,y ... "Menu text" -

    +

    The directive is one of base, default, poly, circle, rect, or point. The value is an @@ -75,7 +77,7 @@ ImapBase as set in a .htaccess file or in the server configuration files. In the absence of an ImapBase configuration directive, base defaults to - http://server_name/.
    + http://server_name/.
    base_uri is synonymous with base. Note that a trailing slash on the URL is significant. @@ -128,7 +130,7 @@

    The URL can be relative or absolute URL. Relative URLs can contain '..' syntax and will be resolved relative to the - base value.
    + base value.
    base itself will not resolved according to the current value. A statement base mailto: will work properly, though.
    @@ -186,65 +188,65 @@
    After the value or after the coordinates, the line optionally may contain text within double quotes. This string is used as the text for the link if a menu is - generated:
    + generated:
    <a HREF="http://foo.com/">Menu - text</a>
    + text</a>
    If no quoted text is present, the name of the link will be - used as the text:
    + used as the text:
    <a - HREF="http://foo.com/">http://foo.com</a>
    + HREF="http://foo.com/">http://foo.com</a>
    It is impossible to escape double quotes within this text.
    -

    Example Mapfile

    +
    top

    Example Mapfile

    -
    +

    #Comments are printed in a 'formatted' or - 'semiformatted' menu.
    - #And can contain html tags. <hr>
    - base referer
    + 'semiformatted' menu.
    + #And can contain html tags. <hr>
    + base referer
    poly map "Could I have a menu, please?" 0,0 0,10 10,10 - 10,0
    - rect .. 0,0 77,27 "the directory of the referer"
    + 10,0
    + rect .. 0,0 77,27 "the directory of the referer"
    circle http://www.inetnebr.com/lincoln/feedback/ 195,0 - 305,27
    + 305,27
    rect another_file "in same directory as referer" 306,0 - 419,27
    - point http://www.zyzzyva.com/ 100,100
    - point http://www.tripod.com/ 200,200
    - rect mailto:nate@tripod.com 100,150 200,0 "Bugs?"
    -

    + 419,27
    + point http://www.zyzzyva.com/ 100,100
    + point http://www.tripod.com/ 200,200
    + rect mailto:nate@tripod.com 100,150 200,0 "Bugs?"
    +

    -

    Referencing your mapfile

    +
    top

    Referencing your mapfile

    -
    - <A HREF="/maps/imagemap1.map">
    - <IMG ISMAP SRC="/images/imagemap1.gif">
    +

    + <A HREF="/maps/imagemap1.map">
    + <IMG ISMAP SRC="/images/imagemap1.gif">
    </A> -

    -

    ImapBase Directive

    Description: - Default base for imagemap files
    Syntax: - ImapBase map|referer|URL
    Default: - ImapBase http://servername/
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_imap
    +

    +
    top

    ImapBase Directive

    Description: + Default base for imagemap files
    Syntax: + ImapBase map|referer|URL
    Default: + ImapBase http://servername/
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_imap

    The ImapBase directive sets the default base used in the imagemap files. Its value is overridden by a base directive within the imagemap file. If not present, the base defaults to http://servername/.

    -

    ImapDefault Directive

    Description: - Default action when an imagemap is called with coordinates -that are not explicitly mapped
    Syntax: - ImapDefault error|nocontent|map|referer|URL
    Default: - ImapDefault nocontent
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_imap
    +
    top

    ImapDefault Directive

    Description: + Default action when an imagemap is called with coordinates +that are not explicitly mapped
    Syntax: + ImapDefault error|nocontent|map|referer|URL
    Default: + ImapDefault nocontent
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_imap

    The ImapDefault directive sets the default default used in the imagemap files. Its value is overridden by a default directive within the @@ -252,15 +254,15 @@ that are not explicitly mappedImapMenu Directive
    Description: - Action if no coordinates are given when calling -an imagemap
    Syntax: - ImapMenu - none|formatted|semiformatted|unformatted
    Context: - server config, virtual host, directory, .htaccess
    Override: - Indexes
    Status: - Base
    Module: - mod_imap
    +

    top

    ImapMenu Directive

    Description: + Action if no coordinates are given when calling +an imagemap
    Syntax: + ImapMenu + none|formatted|semiformatted|unformatted
    Context: + server config, virtual host, directory, .htaccess
    Override: + Indexes
    Status: + Base
    Module: + mod_imap

    The ImapMenu directive determines the action taken if an imagemap file is called without valid coordinates.

    @@ -296,4 +298,4 @@ an imagemapApache HTTP Server Version 2.0IndexHome \ No newline at end of file +
    \ No newline at end of file diff --git a/docs/manual/mod/mod_include.html.en b/docs/manual/mod/mod_include.html.en index 415a2c0728..303c9d587c 100644 --- a/docs/manual/mod/mod_include.html.en +++ b/docs/manual/mod/mod_include.html.en @@ -1,11 +1,13 @@ -mod_include - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_include

    Description: - Server-parsed html documents (Server Side Includes)
    Status: - Base
    Module Identifier: - include_module

    Summary

    + -->mod_include - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_include

    Description: + Server-parsed html documents (Server Side Includes)
    Status: + Base
    Module Identifier: + include_module

    Summary

    This module provides a filter which will process files before they are sent to the client. The processing is @@ -14,7 +16,7 @@ inclusion of other files or programs, as well as the setting and printing of environment variables.

    -

    Directives

    See also

    Enabling Server-Side Includes

    +

    Directives

    Topics

    See also

    top

    Enabling Server-Side Includes

    Server Side Includes are implemented by the @@ -24,10 +26,10 @@ parse them and assign the resulting document the mime type of text/html:

    -
    - AddType text/html .shtml
    +

    + AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml -

    +

    The following directive must be given for the directories containing the shtml files (typically in a @@ -35,9 +37,9 @@ also valid in .htaccess files if AllowOverride Options is set):

    -
    +

    Options +Includes -

    +

    For backwards compatibility, the server-parsed handler also activates the @@ -49,15 +51,15 @@

    For more information, see our Tutorial on Server Side Includes.

    -

    Basic Elements

    +
    top

    Basic Elements

    The document is parsed as an HTML document, with special commands embedded as SGML comments. A command has the syntax:

    -
    +

    <!--#element attribute=value attribute=value ... --> -

    +

    The value will often be enclosed in double quotes; many commands only allow a single attribute-value pair. Note that @@ -140,8 +142,8 @@

    The exec command executes a given shell command or CGI - script. It requires mod_cgi to be present - in the server. The IncludesNOEXEC Option disables this command + script. It requires mod_cgi to be present + in the server. The IncludesNOEXEC Option disables this command completely. The valid attributes are:
    @@ -155,8 +157,8 @@ invoked as a CGI script, even if the server would not normally recognize it as such. However, the directory containing the script must be enabled for CGI scripts - (with ScriptAlias - or the ExecCGI Option). + (with ScriptAlias + or the ExecCGI Option).

    The CGI script is given the PATH_INFO and query string (QUERY_STRING) of the original request from the @@ -167,7 +169,7 @@

    For example:

    -
    <!--#exec cgi="/cgi-bin/example.cgi" -->
    +

    <!--#exec cgi="/cgi-bin/example.cgi" -->

    If the script returns a Location: header instead of output, then this will be translated into an HTML @@ -181,9 +183,9 @@ cgi, but can be done with include virtual, as shown here:

    -
    +

    <!--#include virtual="/cgi-bin/example.cgi?argument=value" --> -

    +

    @@ -209,9 +211,9 @@ non-suexec configuration on unix, it will not produce the desired result under Win32, or when running suexec:

    -
    +

    <!--#exec cmd="perl /path/to/perlscript arg1 arg2" --> -

    +

    @@ -293,9 +295,9 @@ in the parsed file. You may include a query string in a CGI url:

    -
    +

    <!--#include virtual="/cgi-bin/example.cgi?argument=value" --> -

    +

    include virtual should be used in preference to exec cgi to include the output of CGI @@ -314,9 +316,9 @@

    For example:

    -
    +

    <!--#printenv --> -

    +

    The printenv element is available only in Apache 1.2 and above.

    @@ -337,15 +339,15 @@

    For example:

    -
    +

    <!--#set var="category" value="help" --> -

    +

    The set element is available only in Apache 1.2 and above.

    -

    Include Variables

    +
    top

    Include Variables

    In addition to the variables in the standard CGI environment, @@ -378,7 +380,7 @@

    The last modification date of the document requested by the user.
    -

    Variable Substitution

    +
    top

    Variable Substitution

    Variable substitution is done within quoted strings in most @@ -390,9 +392,9 @@ as the arguments to conditional operators. You can insert a literal dollar sign into the string using backslash quoting:

    -
    +

    <!--#if expr="$a = \$test" --> -

    +

    If a variable reference needs to be substituted in the middle of a character sequence that might otherwise be @@ -400,9 +402,9 @@ disambiguated by enclosing the reference in braces, a la shell substitution:

    -
    +

    <!--#set var="Zed" value="${REMOTE_HOST}_${REQUEST_METHOD}" --> -

    +

    This will result in the Zed variable being set to "X_Y" if REMOTE_HOST is @@ -413,27 +415,27 @@ DOCUMENT_URI is /foo/file.html, "in bar" if it is /bar/file.html and "in neither" otherwise:

    -
    - <!--#if expr="\"$DOCUMENT_URI\" = \"/foo/file.html\"" -->
    -   in foo
    - <!--#elif expr="\"$DOCUMENT_URI\" = \"/bar/file.html\"" -->
    -   in bar
    - <!--#else -->
    -   in neither
    +

    + <!--#if expr="\"$DOCUMENT_URI\" = \"/foo/file.html\"" -->
    +   in foo
    + <!--#elif expr="\"$DOCUMENT_URI\" = \"/bar/file.html\"" -->
    +   in bar
    + <!--#else -->
    +   in neither
    <!--#endif --> -

    -

    Flow Control Elements

    +

    +
    top

    Flow Control Elements

    These are available in Apache 1.2 and above. The basic flow control elements are:

    -
    - <!--#if expr="test_condition" -->
    - <!--#elif expr="test_condition" -->
    - <!--#else -->
    +

    + <!--#if expr="test_condition" -->
    + <!--#elif expr="test_condition" -->
    + <!--#else -->
    <!--#endif --> -

    +

    The if element works like an if statement in a programming language. The test condition is @@ -458,11 +460,11 @@

    true if string is not empty
    -
    string1 = string2
    - string1 != string2
    - string1 < string2
    - string1 <= string2
    - string1 > string2
    +
    string1 = string2
    + string1 != string2
    + string1 < string2
    + string1 <= string2
    + string1 > string2
    string1 >= string2
    Compare string1 with string 2. If string2 has the form @@ -494,10 +496,10 @@ "&&" and "||". "!" binds most tightly. Thus, the following are equivalent:

    -
    - <!--#if expr="$a = test1 && $b = test2" -->
    +

    + <!--#if expr="$a = test1 && $b = test2" -->
    <!--#if expr="($a = test1) && ($b = test2)" --> -

    +

    Anything that's not recognized as a variable or an operator is treated as a string. Strings can also be quoted: @@ -506,52 +508,49 @@ variables. If multiple strings are found in a row, they are concatenated using blanks. So,

    -
    - 
    string1    string2  results in string1 string2
    - 
    'string1    string2' results in string1    string2
    -
    +
    string1    string2  results in string1 string2
    'string1    string2' results in string1    string2
    -

    Using Server Side Includes for ErrorDocuments

    +
    top

    Using Server Side Includes for ErrorDocuments

    There is a document which describes how to use the features of mod_include to offer internationalized customized server error documents.

    -

    PATH_INFO with Server Side Includes

    +
    top

    PATH_INFO with Server Side Includes

    Files processed for server-side includes no longer accept requests with PATH_INFO (trailing pathname information) by - default. You can use the AcceptPathInfo directive to + default. You can use the AcceptPathInfo directive to configure the server to accept requests with PATH_INFO.

    -

    SSIEndTag Directive

    Description: - String that ends an include element
    Syntax: - SSIEndTag tag
    Default: - SSIEndTag "-->"
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_include
    Compatibility: - Available in version 2.0.30 and later. -
    +
    top

    SSIEndTag Directive

    Description: + String that ends an include element
    Syntax: + SSIEndTag tag
    Default: + SSIEndTag "-->"
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_include
    Compatibility: + Available in version 2.0.30 and later. +

    This directive changes the string that mod_include looks for to mark the end of an include element.

    -

    Example

    +

    Example

    SSIEndTag "%>" -

    - -

    See also

    SSIErrorMsg Directive

    Description: - Error message displayed when there is an SSI error
    Syntax: - SSIErrorMsg message
    Default: - SSIErrorMsg -"[an error occurred while processing this directive]"
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Base
    Module: - mod_include
    Compatibility: - Available in version 2.0.30 and later.
    +

    + +

    See also

    top

    SSIErrorMsg Directive

    Description: + Error message displayed when there is an SSI error
    Syntax: + SSIErrorMsg message
    Default: + SSIErrorMsg +"[an error occurred while processing this directive]"
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Base
    Module: + mod_include
    Compatibility: + Available in version 2.0.30 and later.

    The SSIErrorMsg directive changes the error message displayed when mod_include encounters an error. For production servers you may consider changing the default error message to @@ -561,20 +560,20 @@

    This directive has the same effect as the <!--#config errmsg=message --> element.

    -

    Example

    +

    Example

    SSIErrorMsg "<!-- Error -->" -

    - -

    SSIStartTag Directive

    Description: - String that starts an include element
    Syntax: - Changes the string that mod_include looks for to start an -include element
    Default: - SSIStartTag "<!--"
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_include
    Compatibility: - Available in version 2.0.30 and later.
    +

    + +
    top

    SSIStartTag Directive

    Description: + String that starts an include element
    Syntax: + Changes the string that mod_include looks for to start an +include element
    Default: + SSIStartTag "<!--"
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_include
    Compatibility: + Available in version 2.0.30 and later.

    This directive changes the string that mod_include looks for to mark an include element to process.

    @@ -583,31 +582,31 @@ include element

    Example

    +

    Example

    SSIStartTag "<%" -

    +

    The example given above, in conjunction with a matching - SSIEndTag, will + SSIEndTag, will allow you to use SSI directives as shown in the example below:

    -

    SSI directives with alternate start and end tags

    +

    SSI directives with alternate start and end tags

    <%#printenv %> -

    - -

    See also

    SSITimeFormat Directive

    Description: - Configures the format in which date strings are -displayed
    Syntax: - SSITimeFormat formatstring
    Default: - SSITimeFormat "%A, %d-%b-%Y %H:%M:%S %Z"
    Context: - server config, virtual host, directory, .htaccess
    Override: - All
    Status: - Base
    Module: - mod_include
    Compatibility: - Available in version 2.0.30 and later.
    +

    + +

    See also

    top

    SSITimeFormat Directive

    Description: + Configures the format in which date strings are +displayed
    Syntax: + SSITimeFormat formatstring
    Default: + SSITimeFormat "%A, %d-%b-%Y %H:%M:%S %Z"
    Context: + server config, virtual host, directory, .htaccess
    Override: + All
    Status: + Base
    Module: + mod_include
    Compatibility: + Available in version 2.0.30 and later.

    This directive changes the format in which date strings are displayed when echoing DATE environment variables. The formatstring is as in strftime(3) from the C standard library.

    @@ -615,41 +614,41 @@ displayedThis directive has the same effect as the <!--#config timefmt=formatstring --> element.

    -

    Example

    +

    Example

    SSITimeFormat "%R, %B %d, %Y" -

    +

    The above directive would cause times to be displayed in the format "22:26, June 14, 2002".

    -

    SSIUndefinedEcho Directive

    Description: - String displayed when -an unset variable is echoed
    Syntax: - SSIUndefinedEcho tag
    Default: - SSIUndefinedEcho "<!-- undef -->"
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_include
    Compatibility: - Available in version 2.0.34 and later. -
    +
    top

    SSIUndefinedEcho Directive

    Description: + String displayed when +an unset variable is echoed
    Syntax: + SSIUndefinedEcho tag
    Default: + SSIUndefinedEcho "<!-- undef -->"
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_include
    Compatibility: + Available in version 2.0.34 and later. +

    This directive changes the string that mod_include displays when a variable is not set and "echoed".

    -

    Example

    +

    Example

    SSIUndefinedEcho "[ No Value ]" -

    - -

    XBitHack Directive

    Description: - Parse SSI directives in files with the execute -bit set
    Syntax: - XBitHack on|off|full
    Default: - XBitHack off
    Context: - server config, virtual host, directory, .htaccess
    Override: - Options
    Status: - Base
    Module: - mod_include
    +

    + +
    top

    XBitHack Directive

    Description: + Parse SSI directives in files with the execute +bit set
    Syntax: + XBitHack on|off|full
    Default: + XBitHack off
    Context: + server config, virtual host, directory, .htaccess
    Override: + Options
    Status: + Base
    Module: + mod_include

    The XBitHack directives controls the parsing of ordinary html documents. This directive only affects files associated with the MIME type text/html. XBitHack can take on @@ -675,12 +674,12 @@ bit set
    Note: you would not want to use the full +
    Note: you would not want to use the full option, unless you assure the group-execute bit is unset for every SSI script which might #include a CGI or otherwise produces different output on each hit (or could - potentially change on subsequent requests).

    + potentially change on subsequent requests). -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_info.html.en b/docs/manual/mod/mod_info.html.en index 660eebf90c..72ca4280ae 100644 --- a/docs/manual/mod/mod_info.html.en +++ b/docs/manual/mod/mod_info.html.en @@ -1,44 +1,46 @@ -mod_info - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_info

    Description: - Provides a comprehensive overview of the server -configuration
    Status: - Extension
    Module Identifier: - info_module

    Summary

    + -->mod_info - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_info

    Description: + Provides a comprehensive overview of the server +configuration
    Status: + Extension
    Module Identifier: + info_module

    Summary

    -

    To configure mod_info, add the following to your +

    To configure mod_info, add the following to your httpd.conf file.

    -
    -<Location /server-info>
    -SetHandler server-info
    -</Location>
    -
    +

    +<Location /server-info>
    +SetHandler server-info
    +</Location>
    +

    You may wish to add a - <Limit> + <Limit> clause inside the - <location> + <location> directive to limit access to your server configuration information.

    Once configured, the server information is obtained by accessing http://your.host.dom/server-info

    -
    +
    Note that the configuration files are read by the module at run-time, and therefore the display may not reflect the running server's active configuration if the files have been changed since the server was last reloaded. Also, the configuration files must be readable by the user as which the server is running (see the - User directive), or + User directive), or else the directive settings will not be listed.

    It should also be noted that if - mod_info is compiled into the server, its + mod_info is compiled into the server, its handler capability is available in all configuration files, including per-directory files (e.g., .htaccess). This may have security-related @@ -51,21 +53,23 @@ SetHandler server-info
    from it. Therefore, this module should ONLY be used in a controlled environment and always with caution.

    -
    -

    Directives

    AddModuleInfo Directive

    Description: - Allows additional information to be added to the module -information displayed by the server-info handler
    Syntax: - AddModuleInfo module-name string
    Context: - server config, virtual -host
    Status: - Extension
    Module: - mod_info
    Compatibility: - Apache 1.3 and above
    +
    +

    Directives

    top

    AddModuleInfo Directive

    Description: + Allows additional information to be added to the module +information displayed by the server-info handler
    Syntax: + AddModuleInfo module-name string
    Context: + server config, virtual +host
    Status: + Extension
    Module: + mod_info
    Compatibility: + Apache 1.3 and above

    This allows the content of string to be shown as HTML interpreted, Additional Information for the module module-name. Example:

    -
    -AddModuleInfo mod_auth.c 'See <A HREF="http://www.apache.org/docs/mod/mod_auth.html">http://www.apache.org/docs/mod/mod_auth.html</A>' -
    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    +AddModuleInfo mod_auth.c 'See <A \
    + HREF="http://www.apache.org/docs/mod/mod_auth.html">\
    + http://www.apache.org/docs/mod/mod_auth.html</A>' +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_info.xml b/docs/manual/mod/mod_info.xml index 16e2f7e86c..2d3a77b132 100644 --- a/docs/manual/mod/mod_info.xml +++ b/docs/manual/mod/mod_info.xml @@ -74,7 +74,9 @@ host the module module-name. Example:

    -AddModuleInfo mod_auth.c 'See <A HREF="http://www.apache.org/docs/mod/mod_auth.html">http://www.apache.org/docs/mod/mod_auth.html</A>' +AddModuleInfo mod_auth.c 'See <A \
    + HREF="http://www.apache.org/docs/mod/mod_auth.html">\
    + http://www.apache.org/docs/mod/mod_auth.html</A>'     diff --git a/docs/manual/mod/mod_isapi.html.en b/docs/manual/mod/mod_isapi.html.en index ebb011d1dd..8fd7aa26b5 100644 --- a/docs/manual/mod/mod_isapi.html.en +++ b/docs/manual/mod/mod_isapi.html.en @@ -1,12 +1,14 @@ -mod_isapi - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_isapi

    Description: - ISAPI Extensions within Apache for Windows
    Status: - Base
    Module Identifier: - isapi_module
    Compatibility: - Win32 only

    Summary

    + -->mod_isapi - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_isapi

    Description: + ISAPI Extensions within Apache for Windows
    Status: + Base
    Module Identifier: + isapi_module
    Compatibility: + Win32 only

    Summary

    This module implements the Internet Server extension API. It allows Internet Server extensions (e.g. ISAPI .dll modules) to be served by Apache for Windows, subject to the @@ -18,23 +20,23 @@ directly if you are experiencing problems running their ISAPI extention. Please do not post such problems to Apache's lists or bug reporting pages.

    -

    Directives

    Usage

    In the server configuration file, use -the AddHandler directive to +

    top

    Usage

    In the server configuration file, use +the AddHandler directive to associate ISAPI files with the isapi-isa handler, and map it to the with their file extensions. To enable any .dll file to be processed as an ISAPI extention, edit the httpd.conf file and add the following line:

    -
    +

    AddHandler isapi-isa .dll -

    +

    There is no capability within the Apache server to leave a requested module loaded. However, you may preload and keep a specific module loaded by using the following syntax in your httpd.conf:

    -
    +

    ISAPICacheFile c:/WebWork/Scripts/ISAPI/mytest.dll -

    +

    Whether or not you have preloaded an ISAPI extension, all ISAPI extensions are governed by the same permissions and @@ -45,7 +47,7 @@ following line:

    Review the Additional Notes and the Programmer's Journal for additional details and clarification of the specific ISAPI support offered by mod_isapi.

    -

    Additional Notes

    +
    top

    Additional Notes

    Apache's ISAPI implementation conforms to all of the ISAPI 2.0 specification, except for some "Microsoft-specific" @@ -71,27 +73,27 @@ following line:

    it does not support ISAPI Filters. Support for filters may be added at a later date, but no support is planned at this time.

    -

    Programmer's Journal

    +
    top

    Programmer's Journal

    -

    If you are programming Apache 2.0 mod_isapi +

    If you are programming Apache 2.0 mod_isapi modules, you must limit your calls to ServerSupportFunction to the following directives:

    HSE_REQ_SEND_URL_REDIRECT_RESP
    -
    Redirect the user to another location.
    +
    Redirect the user to another location.
    This must be a fully qualified URL (e.g. http://server/location).
    HSE_REQ_SEND_URL
    -
    Redirect the user to another location.
    +
    Redirect the user to another location.
    This cannot be a fully qualified URL, you are not allowed to pass the protocol or a server name (e.g. simply - /location).
    + /location).
    This redirection is handled by the server, not the - browser.
    + browser.
    Warning: in their recent documentation, Microsoft appears to have abandoned the distinction between the two HSE_REQ_SEND_URL functions. Apache continues to treat @@ -172,81 +174,81 @@ following line:

    GetServerVariable, as well as the ALL_HTTP and ALL_RAW values.

    -

    Apache 2.0 mod_isapi supports additional +

    Apache 2.0 mod_isapi supports additional features introduced in later versions of the ISAPI specification, as well as limited emulation of async I/O and the TransmitFile semantics. Apache also supports preloading ISAPI .dlls for performance, neither of which were not available under Apache 1.3 mod_isapi.

    -

    ISAPIAppendLogToErrors Directive

    Description: - Record HSE_APPEND_LOG_PARAMETER requests from ISAPI -extensions to the error log
    Syntax: - ISAPIAppendLogToErrors on|off
    Default: - ISAPIAppendLogToErrors off
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_isapi
    +
    top

    ISAPIAppendLogToErrors Directive

    Description: + Record HSE_APPEND_LOG_PARAMETER requests from ISAPI +extensions to the error log
    Syntax: + ISAPIAppendLogToErrors on|off
    Default: + ISAPIAppendLogToErrors off
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_isapi

    Record HSE_APPEND_LOG_PARAMETER requests from ISAPI extensions to the server error log.

    -

    ISAPIAppendLogToQuery Directive

    Description: - Record HSE_APPEND_LOG_PARAMETER requests from ISAPI -extensions to the query field
    Syntax: - ISAPIAppendLogToQuery on|off
    Default: - ISAPIAppendLogToQuery on
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_isapi
    +
    top

    ISAPIAppendLogToQuery Directive

    Description: + Record HSE_APPEND_LOG_PARAMETER requests from ISAPI +extensions to the query field
    Syntax: + ISAPIAppendLogToQuery on|off
    Default: + ISAPIAppendLogToQuery on
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_isapi

    Record HSE_APPEND_LOG_PARAMETER requests from ISAPI extensions to the query field (appended to the CustomLog %q component).

    -

    ISAPICacheFile Directive

    Description: - ISAPI .dll files to be loaded at startup
    Syntax: - ISAPICacheFile file-path [file-path] ...
    Context: - server config, virtual host
    Status: - Base
    Module: - mod_isapi
    +
    top

    ISAPICacheFile Directive

    Description: + ISAPI .dll files to be loaded at startup
    Syntax: + ISAPICacheFile file-path [file-path] ...
    Context: + server config, virtual host
    Status: + Base
    Module: + mod_isapi

    Specifies a space-separated list of file names to be loaded when the Apache server is launched, and remain loaded until the server is shut down. This directive may be repeated for every ISAPI .dll file desired. The full path name of each file should be specified.

    -

    ISAPIFakeAsync Directive

    Description: - Fake asynchronous support for isapi callbacks
    Syntax: - ISAPIFakeAsync on|off
    Default: - ISAPIFakeAsync off
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_isapi
    +
    top

    ISAPIFakeAsync Directive

    Description: + Fake asynchronous support for isapi callbacks
    Syntax: + ISAPIFakeAsync on|off
    Default: + ISAPIFakeAsync off
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_isapi

    While set to on, asynchronous support for isapi callbacks is simulated.

    -

    ISAPILogNotSupported Directive

    Description: - Log unsupported feature requests from ISAPI -extensions
    Syntax: - ISAPILogNotSupported on|off
    Default: - ISAPILogNotSupported off
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_isapi
    +
    top

    ISAPILogNotSupported Directive

    Description: + Log unsupported feature requests from ISAPI +extensions
    Syntax: + ISAPILogNotSupported on|off
    Default: + ISAPILogNotSupported off
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_isapi

    Logs all requests for unsupported features from ISAPI extensions in the server error log. This may help administrators to track down problems. Once set to on and all desired ISAPI modules are functioning, it should be set back to off.

    -

    ISAPIReadAheadBuffer Directive

    Description: - Size of the Read Ahead Buffer sent to ISAPI -extensions
    Syntax: - ISAPIReadAheadBuffer size
    Default: - ISAPIReadAheadBuffer 49152
    Context: - server config, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_isapi
    +
    top

    ISAPIReadAheadBuffer Directive

    Description: + Size of the Read Ahead Buffer sent to ISAPI +extensions
    Syntax: + ISAPIReadAheadBuffer size
    Default: + ISAPIReadAheadBuffer 49152
    Context: + server config, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_isapi

    Defines the maximum size of the Read Ahead Buffer sent to ISAPI extensions when they are initially invoked. All remaining data must be retrieved using the ReadClient callback; some ISAPI extensions may not support the ReadClient function. Refer questions to the ISAPI extension's author.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_ldap.html.en b/docs/manual/mod/mod_ldap.html.en index 455a709faa..af699c2707 100644 --- a/docs/manual/mod/mod_ldap.html.en +++ b/docs/manual/mod/mod_ldap.html.en @@ -1,13 +1,15 @@ -mod_ldap - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_ldap

    Description: - LDAP connection pooling and result caching -services for use by other LDAP modules
    Status: - experimental
    Module Identifier: - ldap_module
    Compatibility: - Available in version 2.0.41 and later

    Summary

    + -->mod_ldap - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_ldap

    Description: + LDAP connection pooling and result caching +services for use by other LDAP modules
    Status: + experimental
    Module Identifier: + ldap_module
    Compatibility: + Available in version 2.0.41 and later

    Summary

    This module was created to improve the performance of websites relying on backend connections to LDAP servers. In addition to the functions provided by the standard LDAP @@ -18,14 +20,13 @@ services for use by other LDAP modules--with-ldap flag to the ./configure script when building Apache.

    -

    Directives

    Example Configuration

    +
    top

    Example Configuration

    The following is an example configuration that uses -mod_ldap to increase the performance of HTTP Basic -authentication provided by mod_auth_ldap.

    +mod_ldap to increase the performance of HTTP Basic +authentication provided by mod_auth_ldap.

    -
    -
    +
     # Enable the LDAP connection pool and shared memory cache. Enable the
 # LDAP cache status handler. Requires that mod_ldap and mod_auth_ldap
 # be loaded. Change the "yourdomain.example.com" to match your domain.
@@ -46,8 +47,8 @@ authentication provided by mod_auth_ld
         AuthLDAPAuthoritative on
         require valid-user
     </Location>
-
    -

    LDAP Connection Pool

    +
    +
    top

    LDAP Connection Pool

    LDAP connections are pooled from request to request. This allows the LDAP server to remain connected and bound ready for @@ -64,22 +65,22 @@ authentication provided by mod_auth_ld

    There is no need to manually enable connection pooling in the Apache configuration. Any module using this module for access to LDAP services will share the connection pool.

    -

    LDAP Cache

    +
    top

    LDAP Cache

    -

    For improved performance, mod_ldap uses an aggressive +

    For improved performance, mod_ldap uses an aggressive caching strategy to minimize the number of times that the LDAP server must be contacted. Caching can easily double or triple the throughput of Apache when it is serving pages protected with mod_auth_ldap. In addition, the load on the LDAP server will be significantly decreased.

    -

    mod_ldap supports two types of LDAP caching during the +

    mod_ldap supports two types of LDAP caching during the search/bind phase with a search/bind cache and during the compare phase with two operation caches. Each LDAP URL that is used by the server has its own set of these three caches.

    -

    The Search/Bind Cache

    +

    The Search/Bind Cache

    The process of doing a search and then a bind is the most time-consuming aspect of LDAP operation, especially if @@ -92,21 +93,21 @@ authentication provided by mod_auth_ld number of connections, so by not caching invalid credentials, the size of the cache is reduced.

    -

    mod_ldap stores the username, the DN +

    mod_ldap stores the username, the DN retrieved, the password used to bind, and the time of the bind in the cache. Whenever a new connection is initiated with the - same username, mod_ldap compares the password + same username, mod_ldap compares the password of the new connection with the password in the cache. If the passwords match, and if the cached entry is not too old, - mod_ldap bypasses the search/bind phase.

    + mod_ldap bypasses the search/bind phase.

    -

    The search and bind cache is controlled with the LDAPCacheEntries and LDAPCacheTTL directives.

    +

    The search and bind cache is controlled with the LDAPCacheEntries and LDAPCacheTTL directives.

    -

    Operation Caches

    +

    Operation Caches

    During attribute and distinguished name comparison - functions, mod_ldap uses two operation caches + functions, mod_ldap uses two operation caches to cache the compare operations. The first compare cache is used to cache the results of compares done to test for LDAP group membership. The second compare cache is used to cache @@ -114,93 +115,93 @@ authentication provided by mod_auth_ld names.

    The behavior of both of these caches is controlled with - the LDAPOpCacheEntries - and LDAPOpCacheTTL + the LDAPOpCacheEntries + and LDAPOpCacheTTL directives.

    -

    Monitoring the Cache

    +

    Monitoring the Cache

    -

    mod_ldap has a content handler that allows +

    mod_ldap has a content handler that allows administrators to monitor the cache performance. The name of the content handler is ldap-status, so the following directives could be used to access the - mod_ldap cache information:

    -
    +        mod_ldap cache information:
    
+
     <Location /server/cache-info >
  SetHandler ldap-status
 </Location>
-
    +

    By fetching the URL http://servername/cache-info, the administrator can get a status report of every cache that is used by - mod_ldap cache. Note that if Apache does not + mod_ldap cache. Note that if Apache does not support shared memory, then each httpd instance has its own cache, so reloading the URL will result in different information each time, depending on which httpd instance processes the request.

    -

    LDAPCacheEntries Directive

    Description: -
    Syntax: - LDAPCacheEntries number
    Default: - LDAPCacheEntries 1024
    Context: - server config
    Status: - experimental
    Module: - mod_ldap
    +
    top

    LDAPCacheEntries Directive

    Description: +
    Syntax: + LDAPCacheEntries number
    Default: + LDAPCacheEntries 1024
    Context: + server config
    Status: + experimental
    Module: + mod_ldap

    Specifies the maximum size of the primary LDAP cache. This cache contains successful search/binds. Set it to 0 to turn off search/bind caching. The default size is 1024 cached searches.

    -

    LDAPCacheTTL Directive

    Description: -
    Syntax: - LDAPCacheTTL seconds
    Default: - LDAPCacheTTL 600
    Context: - server config
    Status: - experimental
    Module: - mod_ldap
    +
    top

    LDAPCacheTTL Directive

    Description: +
    Syntax: + LDAPCacheTTL seconds
    Default: + LDAPCacheTTL 600
    Context: + server config
    Status: + experimental
    Module: + mod_ldap

    Specifies the time (in seconds) that an item in the search/bind cache remains valid. The default is 600 seconds (10 minutes).

    -

    LDAPCertDBPath Directive

    Description: -
    Syntax: - LDAPCertDBPath directory-path
    Context: - server config
    Status: - experimental
    Module: - mod_ldap
    +
    top

    LDAPCertDBPath Directive

    Description: +
    Syntax: + LDAPCertDBPath directory-path
    Context: + server config
    Status: + experimental
    Module: + mod_ldap

    This directive is only valid if Apache has been linked against the Netscape/iPlanet Directory SDK.

    -

    It specifies in which directory mod_ldap +

    It specifies in which directory mod_ldap should look for the certificate authorities database for SSL support. There should be a file named cert7.db in that directory.

    -

    LDAPOpCacheEntries Directive

    Description: -
    Syntax: - LDAPOpCacheEntries number
    Default: - LDAPOpCacheEntries 1024
    Context: - server config
    Status: - experimental
    Module: - mod_ldap
    -

    This specifies the number of entries mod_ldap +

    top

    LDAPOpCacheEntries Directive

    Description: +
    Syntax: + LDAPOpCacheEntries number
    Default: + LDAPOpCacheEntries 1024
    Context: + server config
    Status: + experimental
    Module: + mod_ldap
    +

    This specifies the number of entries mod_ldap will use to cache LDAP compare operations. The default is 1024 entries. Setting it to 0 disables operation caching.

    -

    LDAPOpCacheTTL Directive

    Description: -
    Syntax: - LDAPOpCacheTTL seconds
    Default: - LDAPOpCacheTTL 600
    Context: - server config
    Status: - experimental
    Module: - mod_ldap
    +
    top

    LDAPOpCacheTTL Directive

    Description: +
    Syntax: + LDAPOpCacheTTL seconds
    Default: + LDAPOpCacheTTL 600
    Context: + server config
    Status: + experimental
    Module: + mod_ldap

    Specifies the time (in seconds) that entries in the operation cache remain valid. The default is 600 seconds.

    -

    LDAPSharedCacheSize Directive

    Description: -
    Syntax: - LDAPSharedCacheSize bytes
    Default: - LDAPSharedCacheSize 102400
    Context: - server config
    Status: - experimental
    Module: - mod_ldap
    +
    top

    LDAPSharedCacheSize Directive

    Description: +
    Syntax: + LDAPSharedCacheSize bytes
    Default: + LDAPSharedCacheSize 102400
    Context: + server config
    Status: + experimental
    Module: + mod_ldap

    Specifies the number of bytes to specify for the shared memory cache. The default is 100kb.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_log_config.html.en b/docs/manual/mod/mod_log_config.html.en index a351240c39..2cf1ad946f 100644 --- a/docs/manual/mod/mod_log_config.html.en +++ b/docs/manual/mod/mod_log_config.html.en @@ -1,11 +1,13 @@ -mod_log_config - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_log_config

    Description: - Logging of the requests made to the server
    Status: - Base
    Module Identifier: - log_config_module

    Summary

    + -->mod_log_config - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_log_config

    Description: + Logging of the requests made to the server
    Status: + Base
    Module Identifier: + log_config_module

    Summary

    This module provides for flexible logging of client requests. Logs are written in a customizable format, and may be @@ -21,7 +23,7 @@ step. The TransferLog and CustomLog directives can be used multiple times in each server to cause each request to be logged to multiple files.

    -

    Directives

    See also

    Custom Log Formats

    +

    Directives

    Topics

    See also

    top

    Custom Log Formats

    The format argument to the LogFormat and @@ -126,13 +128,13 @@ be in strftime(3) format. (potentially localized) %...X: Connection status when response is completed. -

    -'X' = connection aborted before the response completed.
    -'+' = connection may be kept alive after the response is sent.
    +

    +'X' = connection aborted before the response completed.
    +'+' = connection may be kept alive after the response is sent.
    '-' = connection will be closed after the response is sent. -

    -
    (This directive was %...c in late versions of Apache 1.3, but -this conflicted with the historical ssl %...{var}c syntax.)
    +

    +
    (This directive was %...c in late versions of Apache 1.3, but +this conflicted with the historical ssl %...{var}c syntax.)
    @@ -184,7 +186,7 @@ this conflicted with the historical ssl %...{var}c syntax.) -

    Security Considerations

    +
    top

    Security Considerations

    @@ -193,31 +195,31 @@ this conflicted with the historical ssl %...{var}c syntax.) -

    CookieLog Directive

    Description: - Sets filename for the logging of cookies
    Syntax: - CookieLog filename
    Context: - server config, virtual -host
    Status: - Base
    Module: - mod_log_config
    Compatibility: - Only available in Apache 1.2 and above
    +
    top

    CookieLog Directive

    Description: + Sets filename for the logging of cookies
    Syntax: + CookieLog filename
    Context: + server config, virtual +host
    Status: + Base
    Module: + mod_log_config
    Compatibility: + Only available in Apache 1.2 and above

    The CookieLog directive sets the filename for logging of cookies. The filename is relative to the - serverroot. This directive is - included only for compatibility with mod_cookies, + serverroot. This directive is + included only for compatibility with mod_cookies, and is deprecated.

    -

    CustomLog Directive

    Description: - Sets filename and format of log file
    Syntax: - CustomLog +
    top

    CustomLog Directive

    Description: + Sets filename and format of log file
    Syntax: + CustomLog file|pipe format|nickname - [env=[!]environment-variable]
    Context: - server config, virtual -host
    Status: - Base
    Module: - mod_log_config
    Compatibility: - Nickname only available in Apache 1.3 or later. -Conditional logging available in 1.3.5 or later.
    + [env=[!]environment-variable]
    Context: + server config, virtual +host
    Status: + Base
    Module: + mod_log_config
    Compatibility: + Nickname only available in Apache 1.3 or later. +Conditional logging available in 1.3.5 or later.

    The CustomLog directive is used to log requests to the server. A log format is specified, and the logging can optionally be made conditional on request @@ -251,14 +253,14 @@ Conditional logging available in 1.3.5 or later.For example, the following two sets of directives have exactly the same effect:

    -
    - # CustomLog with format nickname
    - LogFormat "%h %l %u %t \"%r\" %>s %b" common
    - CustomLog logs/access_log common
    -
    - # CustomLog with explicit format string
    - CustomLog logs/access_log "%h %l %u %t \"%r\" %>s %b"
    -
    +

    + # CustomLog with format nickname
    + LogFormat "%h %l %u %t \"%r\" %>s %b" common
    + CustomLog logs/access_log common
    +
    + # CustomLog with explicit format string
    + CustomLog logs/access_log "%h %l %u %t \"%r\" %>s %b"
    +

    The third argument is optional and allows the decision on whether or not to log a particular request to be based on the @@ -269,28 +271,28 @@ Conditional logging available in 1.3.5 or later.

    Environment variables can be set on a per-request - basis using the mod_setenvif - and/or mod_rewrite modules. For + basis using the mod_setenvif + and/or mod_rewrite modules. For example, if you want to record requests for all GIF images on your server in a separate logfile but not in your main log, you can use:

    -
    - SetEnvIf Request_URI \.gif$ gif-image
    - CustomLog gif-requests.log common env=gif-image
    +

    + SetEnvIf Request_URI \.gif$ gif-image
    + CustomLog gif-requests.log common env=gif-image
    CustomLog nongif-requests.log common env=!gif-image -

    -

    LogFormat Directive

    Description: - Describes a format for use in a log file
    Syntax: - LogFormat - format|nickname [nickname]
    Default: - LogFormat "%h %l %u %t \"%r\" %>s %b"
    Context: - server config, virtual -host
    Status: - Base
    Module: - mod_log_config
    Compatibility: - Nickname only available in Apache 1.3 or later. -
    +

    +
    top

    LogFormat Directive

    Description: + Describes a format for use in a log file
    Syntax: + LogFormat + format|nickname [nickname]
    Default: + LogFormat "%h %l %u %t \"%r\" %>s %b"
    Context: + server config, virtual +host
    Status: + Base
    Module: + mod_log_config
    Compatibility: + Nickname only available in Apache 1.3 or later. +

    This directive specifies the format of the access log file.

    @@ -322,17 +324,17 @@ hostFor example:

    -
    LogFormat "%v %h %l %u %t \"%r\" %>s %b" - vhost_common
    +

    LogFormat "%v %h %l %u %t \"%r\" %>s %b" + vhost_common

    -

    TransferLog Directive

    Description: - Specifly location of a log file
    Syntax: - TransferLog file|pipe
    Context: - server config, virtual -host
    Status: - Base
    Module: - mod_log_config
    Compatibility: -
    +
    top

    TransferLog Directive

    Description: + Specifly location of a log file
    Syntax: + TransferLog file|pipe
    Context: + server config, virtual +host
    Status: + Base
    Module: + mod_log_config
    Compatibility: +

    This directive has exactly the same arguments and effect as the CustomLog directive, with the @@ -344,9 +346,9 @@ host

    Example:

    -
    - LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\""
    +

    + LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\""
    TransferLog logs/access_log -

    +

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_mem_cache.html.en b/docs/manual/mod/mod_mem_cache.html.en index fcdbcb1bb2..0f4329a245 100644 --- a/docs/manual/mod/mod_mem_cache.html.en +++ b/docs/manual/mod/mod_mem_cache.html.en @@ -1,113 +1,115 @@ -mod_mem_cache - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_mem_cache

    Description: - Content cache keyed to URIs
    Status: - Experimental
    Module Identifier: - mem_cache_module

    Summary

    + -->mod_mem_cache - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_mem_cache

    Description: + Content cache keyed to URIs
    Status: + Experimental
    Module Identifier: + mem_cache_module

    Summary

    -
    +
    This module is experimental. Documentation is still under development... -
    +

    mod_mem_cache implements an in-memory based storage manager. mod_mem_cache can be configured to operate in two modes: caching open file descriptors or caching objects in heap storage. mod_mem_cache is most useful when used to cache locally generated content or to cache - backend server content for mod_proxy configured for ProxyPass + backend server content for mod_proxy configured for ProxyPass (aka reverse proxy)

    -
    -

    mod_mem_cache requires the services of mod_cache.

    -
    +
    +

    mod_mem_cache requires the services of mod_cache.

    +

    Content stored and retrived keyed to the URL. Content with access protections is not cached.

    -

    Directives

    MCacheMaxObjectCount Directive

    Description: - The maximum number of objects allowed to be placed in the cache
    Syntax: - MCacheMaxObjectCount value
    Default: - MCacheMaxObjectCount 1009
    Context: - server config
    Status: - Experimental
    Module: - mod_mem_cache
    +
    top

    MCacheMaxObjectCount Directive

    Description: + The maximum number of objects allowed to be placed in the cache
    Syntax: + MCacheMaxObjectCount value
    Default: + MCacheMaxObjectCount 1009
    Context: + server config
    Status: + Experimental
    Module: + mod_mem_cache

    The MCacheMaxObjectCount directive sets the maximum number of objects to be cached. If a new entry needs to be inserted in the cache and the maximum number of objects is reached, an entry will be removed to allow the new entry be cached.

    -
    +
    The size must be greater than MCacheMinObjectSize. -
    +
    -
    +
    The value of MCacheMaxObjectCount is used to create the open hash table. -
    -
    - MCacheMaxObjectCount 13001
    -
    -

    MCacheMaxObjectSize Directive

    Description: - The maximum size (in bytes) of an object to be placed in the cache
    Syntax: - MCacheMaxObjectSize bytes
    Default: - MCacheMaxObjectSize 10000
    Context: - server config
    Status: - Experimental
    Module: - mod_mem_cache
    + +

    + MCacheMaxObjectCount 13001
    +

    +
    top

    MCacheMaxObjectSize Directive

    Description: + The maximum size (in bytes) of an object to be placed in the cache
    Syntax: + MCacheMaxObjectSize bytes
    Default: + MCacheMaxObjectSize 10000
    Context: + server config
    Status: + Experimental
    Module: + mod_mem_cache

    The MCacheMaxObjectSize directive sets the maximum size of an object to be cached.

    -
    - MCacheMaxObjectSize 6400000
    -
    -

    MCacheMinObjectSize Directive

    Description: - The minimum size (in bytes) of an object to be placed in the cache
    Syntax: - MCacheMinObjectSize bytes
    Default: - MCacheMinObjectSize 0
    Context: - server config
    Status: - Experimental
    Module: - mod_mem_cache
    +

    + MCacheMaxObjectSize 6400000
    +

    +
    top

    MCacheMinObjectSize Directive

    Description: + The minimum size (in bytes) of an object to be placed in the cache
    Syntax: + MCacheMinObjectSize bytes
    Default: + MCacheMinObjectSize 0
    Context: + server config
    Status: + Experimental
    Module: + mod_mem_cache

    The MCacheMinObjectSize directive sets the minimum size in bytes of an object to be cached.

    -
    - MCacheMinObjectSize 10000
    -
    -

    MCacheRemovalAlgorithm Directive

    Description: - The algorithm used to remove entries from the cache
    Syntax: - MCacheRemovalAlgorithm algorithm
    Default: - MCacheRemovalAlgorithm GDSF
    Context: - server config
    Status: - Experimental
    Module: - mod_mem_cache
    +

    + MCacheMinObjectSize 10000
    +

    +
    top

    MCacheRemovalAlgorithm Directive

    Description: + The algorithm used to remove entries from the cache
    Syntax: + MCacheRemovalAlgorithm algorithm
    Default: + MCacheRemovalAlgorithm GDSF
    Context: + server config
    Status: + Experimental
    Module: + mod_mem_cache

    The MCacheRemovalAlgorithm directive sets the algorithm used to remove entries from the cache. - Two choices are available:
    + Two choices are available:
    LRU (Least Recently Used): LRU removes the objects that have not been - accessed for the longest time.
    + accessed for the longest time.
    GDSF (GreadyDual-Size): This algorithm assigns priority to cached objects based on the coast of a cache miss and the size of the object. Objects with smallest priority are removed first.

    -
    - MCacheRemovalAlgorithm GDSF
    - MCacheRemovalAlgorithm LRU
    -
    -

    MCacheSize Directive

    Description: - The maximum amount of memory used by the cache in KBytes
    Syntax: - MCacheSize KBytes
    Default: - MCacheSize 100
    Context: - server config
    Status: - Experimental
    Module: - mod_mem_cache
    +

    + MCacheRemovalAlgorithm GDSF
    + MCacheRemovalAlgorithm LRU
    +

    +
    top

    MCacheSize Directive

    Description: + The maximum amount of memory used by the cache in KBytes
    Syntax: + MCacheSize KBytes
    Default: + MCacheSize 100
    Context: + server config
    Status: + Experimental
    Module: + mod_mem_cache

    The MCacheSize directive sets the desired space usage of the cache, in KBytes (1024-byte units). If a new entry needs to be inserted in the cache and the size of the entry is greather than the remaining size, entries will be removed until the new entry could be cached. The removed entry is decided base on the MCacheRemovalAlgorithm algorithm

    -
    +
    The size must be greater than MCacheMaxObjectSize. -
    +
    -
    - MCacheSize 700000
    -
    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    + MCacheSize 700000
    +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_mime.html.en b/docs/manual/mod/mod_mime.html.en index 58663cf3d5..389b7853b0 100644 --- a/docs/manual/mod/mod_mime.html.en +++ b/docs/manual/mod/mod_mime.html.en @@ -1,14 +1,16 @@ -mod_mime - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_mime

    Description: - Associates the requested filename's extensions + -->mod_mime - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_mime

    Description: + Associates the requested filename's extensions with the file's behavior (handlers and filters) and content (mime-type, language, character set and - encoding)
    Status: - Base
    Module Identifier: - mime_module

    Summary

    + encoding)
    Status: + Base
    Module Identifier: + mime_module

    Summary

    This module is used to associate various bits of "meta information" with files by their filename extensions. This information relates the filename of the document to it's @@ -16,28 +18,28 @@ information is sent to the browser, and participates in content negotiation, so the user's preferences are respected when choosing one of several possible files to serve. See - mod_negotiation for more information + mod_negotiation for more information about content negotiation.

    -

    The directives AddCharset, AddEncoding, AddLanguage and AddType are all used to map file +

    The directives AddCharset, AddEncoding, AddLanguage and AddType are all used to map file extensions onto the meta-information for that file. Respectively they set the character set, content-encoding, content-language, - and MIME-type (content-type) of documents. The directive TypesConfig is used to specify a + and MIME-type (content-type) of documents. The directive TypesConfig is used to specify a file which also maps extensions onto MIME types.

    -

    In addition, mod_mime may define the handler and filters that originate and process - content. The directives AddHandler, AddOutputFilter, and AddInputFilter control the modules - or scripts that serve the document. The MultiviewsMatch directive allows - mod_negotiation to consider these file extensions +

    In addition, mod_mime may define the handler and filters that originate and process + content. The directives AddHandler, AddOutputFilter, and AddInputFilter control the modules + or scripts that serve the document. The MultiviewsMatch directive allows + mod_negotiation to consider these file extensions to be included when testing Multiviews matches.

    -

    While mod_mime associates meta-information - with filename extensions, the core server +

    While mod_mime associates meta-information + with filename extensions, the core server provides directives that are used to associate all the files in a - given container (e.g., <location>, <directory>, or <Files>) with particular - meta-information. These directives include ForceType, SetHandler, SetInputFilter, and SetOutputFilter. The core directives + given container (e.g., <location>, <directory>, or <Files>) with particular + meta-information. These directives include ForceType, SetHandler, SetInputFilter, and SetOutputFilter. The core directives override any filename extension mappings defined in - mod_mime.

    + mod_mime.

    Note that changing the meta-information for a file does not change the value of the Last-Modified header. @@ -47,7 +49,7 @@ encoding) you may need to 'touch' affected files (updating their last modified date) to ensure that all visitors are receive the corrected content headers.

    -

    Directives

    See also

    Files with Multiple Extensions

    +
    top

    Files with Multiple Extensions

    Files can have more than one extension, and the order of the @@ -73,7 +75,7 @@ MIME-type. When it is processed, the "imap-file" handler will be used, and so it will be treated as a mod_imap imagemap file.

    -

    Content encoding

    +
    top

    Content encoding

    A file of a particular MIME type can additionally be encoded a particular way to simplify transmission over the Internet. @@ -85,7 +87,7 @@

    The MIME RFC puts it this way:

    -
    +
    The Content-Encoding entity-header field is used as a modifier to the media-type. When present, its value indicates what additional content coding has been applied to the @@ -94,7 +96,7 @@ header field. The Content-Encoding is primarily used to allow a document to be compressed without losing the identity of its underlying media type. -
    +

    By using more than one file extension (see section above about multiple file extensions), you can indicate that a file is of a @@ -113,9 +115,9 @@ resource, in order to tell the client browser about the encoding method.

    -
    Content-encoding: pkzip
    +

    Content-encoding: pkzip

    -

    Character sets and languages

    +
    top

    Character sets and languages

    @@ -129,16 +131,16 @@

    The character set, language encoding and mime type are all used in the process of content negotiation (See - mod_negotiation) to determine + mod_negotiation) to determine which document to give to the client, when there are alternative documents in more than one character set, language, encoding or mime type. All filename extensions associations - created with AddCharset, AddEncoding, - AddLanguage and AddType directives - (and extensions listed in the MimeMagicFile) + created with AddCharset, AddEncoding, + AddLanguage and AddType directives + (and extensions listed in the MimeMagicFile) participate in this select process. Filename extensions that - are only associated using the AddHandler, - AddInputFilter or AddOutputFilter + are only associated using the AddHandler, + AddInputFilter or AddOutputFilter directives may be included or excluded from matching by using the MultiviewsMatch directive.

    @@ -152,26 +154,26 @@ particular character set that should be used to correctly render the information.

    -
    -Content-Language: en, fr
    +

    +Content-Language: en, fr
    Content-Type: text/plain; charset=ISO-8859-2 -

    +

    The language specification is the two-letter abbreviation for the language. The charset is the name of the particular character set which should be used.

    -

    AddCharset Directive

    Description: - Maps the given filename extensions - to the specified content charset
    Syntax: - AddCharset charset extension -[extension] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_mime
    Compatibility: - AddCharset is only available in Apache -1.3.10 and later
    +
    top

    AddCharset Directive

    Description: + Maps the given filename extensions + to the specified content charset
    Syntax: + AddCharset charset extension +[extension] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_mime
    Compatibility: + AddCharset is only available in Apache +1.3.10 and later

    The AddCharset directive maps the given filename extensions to the specified content charset. charset is the MIME @@ -180,12 +182,12 @@ Content-Type: text/plain; charset=ISO-8859-2 mappings that already exist for the same extension.

    Example:

    -
    - AddLanguage ja .ja
    - AddCharset EUC-JP .euc
    - AddCharset ISO-2022-JP .jis
    +

    + AddLanguage ja .ja
    + AddCharset EUC-JP .euc
    + AddCharset ISO-2022-JP .jis
    AddCharset SHIFT_JIS .sjis -

    +

    Then the document xxxx.ja.jis will be treated as being a Japanese document whose charset is ISO-2022-JP (as @@ -199,15 +201,15 @@ Content-Type: text/plain; charset=ISO-8859-2

    The extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    See also

    AddEncoding Directive

    Description: - Maps the given filename extensions - to the specified encoding type
    Syntax: - AddEncoding - MIME-enc extension [extension] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_mime
    +

    See also

    top

    AddEncoding Directive

    Description: + Maps the given filename extensions + to the specified encoding type
    Syntax: + AddEncoding + MIME-enc extension [extension] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_mime

    The AddEncoding directive maps the given filename extensions to the specified encoding type. MIME-enc is the MIME @@ -216,10 +218,10 @@ Content-Type: text/plain; charset=ISO-8859-2 force, overriding any mappings that already exist for the same extension. Example:

    -
    - AddEncoding x-gzip .gz
    +

    + AddEncoding x-gzip .gz
    AddEncoding x-compress .Z -

    +

    This will cause filenames containing the .gz extension to be marked as encoded using the x-gzip encoding, and filenames @@ -244,15 +246,15 @@ Content-Type: text/plain; charset=ISO-8859-2

    The extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    AddHandler Directive

    Description: - Maps the filename extensions -to the specified handler
    Syntax: - AddHandler - handler-name extension [extension] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_mime
    +
    top

    AddHandler Directive

    Description: + Maps the filename extensions +to the specified handler
    Syntax: + AddHandler + handler-name extension [extension] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_mime

    Files having the name extension will be served by the specified handler-name. This mapping is added to any already in force, overriding any mappings that already @@ -260,9 +262,9 @@ exist for the same extension. For example, to activate CGI scripts with the file extension ".cgi", you might use:

    -
    +

    AddHandler cgi-script .cgi -

    +

    Once that has been put into your srm.conf or httpd.conf file, any file containing the ".cgi" extension @@ -271,18 +273,18 @@ use:

    The extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    See also

    AddInputFilter Directive

    Description: - Maps filename extensions +

    See also

    top

    AddInputFilter Directive

    Description: + Maps filename extensions to the filters that will process - client requests
    Syntax: - AddInputFilter + client requests
    Syntax: + AddInputFilter filter[;filter...] extension - [extension ...]
    Context: - server config, virtual host, directory, .htaccess
    Status: - Base
    Module: - mod_mime
    Compatibility: - AddInputFilter - is only available in Apache 2.0.26 and later.
    + [extension ...]
    Context: + server config, virtual host, directory, .htaccess
    Status: + Base
    Module: + mod_mime
    Compatibility: + AddInputFilter + is only available in Apache 2.0.26 and later.

    AddInputFilter maps the filename extensions extension to the filters which will process @@ -298,15 +300,15 @@ use:

    case-insensitive, and the extension may be specified with or without a leading dot.

    -

    AddLanguage Directive

    Description: - Maps the given filename extension -to the specified content language
    Syntax: - AddLanguage - MIME-lang extension [extension] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_mime
    +
    top

    AddLanguage Directive

    Description: + Maps the given filename extension +to the specified content language
    Syntax: + AddLanguage + MIME-lang extension [extension] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_mime

    The AddLanguage directive maps the given filename extension to the specified content language. MIME-lang is the @@ -317,11 +319,11 @@ to the specified content language - AddEncoding x-compress .Z
    - AddLanguage en .en
    +

    + AddEncoding x-compress .Z
    + AddLanguage en .en
    AddLanguage fr .fr -

    +

    Then the document xxxx.en.Z will be treated as being a compressed English document (as will the document @@ -335,11 +337,11 @@ to the specified content language - AddLanguage en .en
    - AddLanguage en-uk .en
    +

    + AddLanguage en .en
    + AddLanguage en-uk .en
    AddLanguage en-us .en -     +

    documents with the extension ".en" would be treated as being "en-us".

    @@ -347,37 +349,37 @@ to the specified content language    mod_negotiation

    AddOutputFilter Directive

    Description: - maps the filename +

    See also

    top

    AddOutputFilter Directive

    Description: + maps the filename extensions to the filters that will process -responses from the server
    Syntax: - AddOutputFilter +responses from the server
    Syntax: + AddOutputFilter filter[;filter...] extension - [extension ...]
    Context: - server config, virtual host, directory, .htaccess
    Override: -
    Status: - Base
    Module: - mod_mime
    Compatibility: - AddOutputFilter - is only available in Apache 2.0.26 and later.
    + [extension ...]
    Context: + server config, virtual host, directory, .htaccess
    Override: +
    Status: + Base
    Module: + mod_mime
    Compatibility: + AddOutputFilter + is only available in Apache 2.0.26 and later.

    The AddOutputFilter directive maps the filename extensions extension to the filters which will process responses from the server before they are sent to the client. This is in addition to any filters defined elsewhere, including the - SetOutputFilter + SetOutputFilter directive. This mapping is merged over any already in force, overriding any mappings that already exist for the same extension.

    For example, the following configuration will process all .shtml files for server-side includes and will then compress - the output using mod_deflate.

    + the output using mod_deflate.

    -
    +

    AddOutputFilter INCLUDES;DEFLATE shtml -

    +

    If more than one filter is specified, they must be separated by semicolons in the order in which they should process the @@ -385,15 +387,15 @@ responses from the serverRemoveOutputFilter

    AddType Directive

    Description: - Maps the given filename extensions -onto the specified content type
    Syntax: - AddType MIME-type - extension [extension] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_mime
    +

    See also

    top

    AddType Directive

    Description: + Maps the given filename extensions +onto the specified content type
    Syntax: + AddType MIME-type + extension [extension] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_mime

    The AddType directive maps the given filename extensions onto the specified content type. MIME-type is the MIME type to @@ -401,33 +403,33 @@ onto the specified content typeTypesConfig + TypesConfig directive).

    Example:

    -
    +

    AddType image/gif .gif -

    +

    -
    It is recommended that new MIME types be added using the +
    It is recommended that new MIME types be added using the AddType directive rather than changing the - TypesConfig file.
    + TypesConfig file.

    The extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    See also

    DefaultLanguage Directive

    Description: - Sets all files in the given scope to the -specified language
    Syntax: - DefaultLanguage - MIME-lang
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_mime
    Compatibility: - DefaultLanguage - is only available in Apache 1.3.4 and later.
    +

    See also

    top

    DefaultLanguage Directive

    Description: + Sets all files in the given scope to the +specified language
    Syntax: + DefaultLanguage + MIME-lang
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_mime
    Compatibility: + DefaultLanguage + is only available in Apache 1.3.4 and later.

    The DefaultLanguage directive tells Apache that all files in the directive's scope (e.g., all files covered by the @@ -446,21 +448,21 @@ specified language

    Example

    +

    Example

    DefaultLanguage en - - -

    See also

    MultiviewsMatch Directive

    Description: - The types of files that will be included when -searching for a matching file with MultiViews
    Syntax: - MultiviewsMatch - [NegotiatedOnly] [Handlers] [Filters] [Any]
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_mime
    Compatibility: - Available - in Apache 2.0.26 and later.
    +

    + +

    See also

    top

    MultiviewsMatch Directive

    Description: + The types of files that will be included when +searching for a matching file with MultiViews
    Syntax: + MultiviewsMatch + [NegotiatedOnly] [Handlers] [Filters] [Any]
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_mime
    Compatibility: + Available + in Apache 2.0.26 and later.

    MultiviewsMatch permits three different behaviors for mod_negotiation's Multiviews @@ -490,20 +492,20 @@ searching for a matching file with MultiViews<

    For example, the following configuration will allow handlers and filters to participate in Multviews, but will exclude unknown files:

    -
    +

    MultiviewsMatch Handlers Filters -

    - -

    See also

    RemoveCharset Directive

    Description: - Removes any character set associations for a set of file -extensions
    Syntax: - RemoveCharset - extension [extension] ...
    Context: - directory, .htaccess
    Status: - Base
    Module: - mod_mime
    Compatibility: - RemoveCharset is - only available in Apache 2.0.24 and later.
    +

    + +

    See also

    top

    RemoveCharset Directive

    Description: + Removes any character set associations for a set of file +extensions
    Syntax: + RemoveCharset + extension [extension] ...
    Context: + directory, .htaccess
    Status: + Base
    Module: + mod_mime
    Compatibility: + RemoveCharset is + only available in Apache 2.0.24 and later.

    The RemoveCharset directive removes any character set associations for files with the given extensions. This allows .htaccess files in subdirectories to @@ -513,20 +515,20 @@ extensionsThe extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    Example

    +

    Example

    RemoveCharset .html .shtml -

    - -

    RemoveEncoding Directive

    Description: - Removes any content encoding associations for a set of file -extensions
    Syntax: - RemoveEncoding - extension [extension] ...
    Context: - directory, .htaccess
    Status: - Base
    Module: - mod_mime
    Compatibility: - RemoveEncoding - is only available in Apache 1.3.13 and later.
    +

    + +
    top

    RemoveEncoding Directive

    Description: + Removes any content encoding associations for a set of file +extensions
    Syntax: + RemoveEncoding + extension [extension] ...
    Context: + directory, .htaccess
    Status: + Base
    Module: + mod_mime
    Compatibility: + RemoveEncoding + is only available in Apache 1.3.13 and later.

    The RemoveEncoding directive removes any encoding associations for files with the given extensions. This @@ -535,17 +537,13 @@ extensions -

    -
    -
    /foo/.htaccess:
    -
    AddEncoding x-gzip .gz
    - AddType text/plain .asc
    - <Files *.gz.asc>
    -     RemoveEncoding - .gz
    - </Files>
    -
    -
    +

    /foo/.htaccess:

    +AddEncoding x-gzip .gz
+AddType text/plain .asc
+<Files *.gz.asc>
+  RemoveEncoding .gz
+</Files>
+

    This will cause foo.gz to be marked as being encoded with the gzip method, but foo.gz.asc as an @@ -558,16 +556,16 @@ extensionsThe extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    RemoveHandler Directive

    Description: - Removes any handler associations for a set of file -extensions
    Syntax: - RemoveHandler - extension [extension] ...
    Context: - directory, .htaccess
    Status: - Base
    Module: - mod_mime
    Compatibility: - RemoveHandler is - only available in Apache 1.3.4 and later.
    +
    top

    RemoveHandler Directive

    Description: + Removes any handler associations for a set of file +extensions
    Syntax: + RemoveHandler + extension [extension] ...
    Context: + directory, .htaccess
    Status: + Base
    Module: + mod_mime
    Compatibility: + RemoveHandler is + only available in Apache 1.3.4 and later.

    The RemoveHandler directive removes any handler associations for files with the given extensions. This allows @@ -575,17 +573,13 @@ extensions -

    -
    -
    /foo/.htaccess:
    +

    /foo/.htaccess:

    +AddHandler server-parsed .html +

    -
    AddHandler server-parsed .html
    - -
    /foo/bar/.htaccess:
    - -
    RemoveHandler .html
    -
    -
    +

    /foo/bar/.htaccess:

    +RemoveHandler .html +

    This has the effect of returning .html files in the /foo/bar directory to being treated as normal @@ -594,16 +588,16 @@ extensionsThe extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    RemoveInputFilter Directive

    Description: - Removes any input filter associations for a set of file -extensions
    Syntax: - RemoveInputFilter - extension [extension] ...
    Context: - directory, .htaccess
    Status: - Base
    Module: - mod_mime
    Compatibility: - RemoveInputFilter is only available in Apache -2.0.26 and later.
    +
    top

    RemoveInputFilter Directive

    Description: + Removes any input filter associations for a set of file +extensions
    Syntax: + RemoveInputFilter + extension [extension] ...
    Context: + directory, .htaccess
    Status: + Base
    Module: + mod_mime
    Compatibility: + RemoveInputFilter is only available in Apache +2.0.26 and later.

    The RemoveInputFilter directive removes any input filter associations for files with the given extensions. @@ -614,16 +608,16 @@ extensionsThe extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    RemoveLanguage Directive

    Description: - Removes any language associations for a set of file -extensions
    Syntax: - RemoveLanguage - extension [extension] ...
    Context: - directory, .htaccess
    Status: - Base
    Module: - mod_mime
    Compatibility: - RemoveLanguage - is only available in Apache 2.0.24 and later.
    +
    top

    RemoveLanguage Directive

    Description: + Removes any language associations for a set of file +extensions
    Syntax: + RemoveLanguage + extension [extension] ...
    Context: + directory, .htaccess
    Status: + Base
    Module: + mod_mime
    Compatibility: + RemoveLanguage + is only available in Apache 2.0.24 and later.

    The RemoveLanguage directive removes any language associations for files with the given extensions. This @@ -633,17 +627,17 @@ extensionsThe extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    RemoveOutputFilter Directive

    Description: - Removes any output filter associations for a set of file -extensions
    Syntax: - RemoveOutputFilter - extension [extension] ...
    Context: - directory, .htaccess
    Override: -
    Status: - Base
    Module: - mod_mime
    Compatibility: - RemoveOutputFilter is only available in Apache -2.0.26 and later.
    +
    top

    RemoveOutputFilter Directive

    Description: + Removes any output filter associations for a set of file +extensions
    Syntax: + RemoveOutputFilter + extension [extension] ...
    Context: + directory, .htaccess
    Override: +
    Status: + Base
    Module: + mod_mime
    Compatibility: + RemoveOutputFilter is only available in Apache +2.0.26 and later.

    The RemoveOutputFilter directive removes any output filter associations for files with the given extensions. @@ -654,53 +648,49 @@ extensionsThe extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    Example

    +

    Example

    RemoveOutputFilter shtml -

    -

    See also

    RemoveType Directive

    Description: - Removes any content type associations for a set of file -extensions
    Syntax: - RemoveType - extension [extension] ...
    Context: - directory, .htaccess
    Override: -
    Status: - Base
    Module: - mod_mime
    Compatibility: - RemoveType is - only available in Apache 1.3.13 and later.
    +

    +

    See also

    top

    RemoveType Directive

    Description: + Removes any content type associations for a set of file +extensions
    Syntax: + RemoveType + extension [extension] ...
    Context: + directory, .htaccess
    Override: +
    Status: + Base
    Module: + mod_mime
    Compatibility: + RemoveType is + only available in Apache 1.3.13 and later.

    The RemoveType directive removes any MIME type associations for files with the given extensions. This allows .htaccess files in subdirectories to undo any associations inherited from parent directories or the server config files. An example of its use might be:

    -
    -
    -
    /foo/.htaccess:
    - -
    RemoveType .cgi
    -
    -
    +

    /foo/.htaccess:

    +RemoveType .cgi +

    This will remove any special handling of .cgi files in the /foo/ directory and any beneath it, causing the files to be treated as being of the default type.

    -
    Note:RemoveType directives +
    Note:RemoveType directives are processed after any AddType directives, so it is possible they may undo the effects of the latter if both occur within the same directory - configuration.
    + configuration.

    The extension argument is case-insensitive, and can be specified with or without a leading dot.

    -

    TypesConfig Directive

    Description: - The location of the mime.types file
    Syntax: - TypesConfig file-path
    Default: - TypesConfig conf/mime.types
    Context: - server config
    Status: - Base
    Module: - mod_mime
    +
    top

    TypesConfig Directive

    Description: + The location of the mime.types file
    Syntax: + TypesConfig file-path
    Default: + TypesConfig conf/mime.types
    Context: + server config
    Status: + Base
    Module: + mod_mime

    The TypesConfig directive sets the location of the MIME types configuration file. Filename is relative to the ServerRoot. This file sets the @@ -712,28 +702,28 @@ extensionshttp://www.isi.edu/in-notes/iana/assignments/media-types/media-types. This simplifies the httpd.conf file by providing the majority of media-type definitions, and may be overridden by - AddType directives as + AddType directives as needed. You should not edit the mime.types file, because it may be replaced when you upgrade your server.

    The file contains lines in the format of the arguments to - an AddType directive:

    + an AddType directive:

    -
    +

    MIME-type extension extension ... -

    +

    The case of the extension does not matter. Blank lines, and lines beginning with a hash character (`#') are ignored.

    -
    Please do not send requests to the Apache HTTP Server Project +
    Please do not send requests to the Apache HTTP Server Project to add any new entries in the distributed mime.types file unless (1) they are already registered with IANA, and (2) they use widely accepted, non-conflicting filename extensions across platforms. category/x-subtype requests will be automatically rejected, as will any new two-letter extensions as they will likely conflict later with the already crowded language and - character set namespace.
    + character set namespace. -

    See also

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    See also

    \ No newline at end of file diff --git a/docs/manual/mod/mod_mime.xml b/docs/manual/mod/mod_mime.xml index 61a604c09e..1d8b1be9c8 100644 --- a/docs/manual/mod/mod_mime.xml +++ b/docs/manual/mod/mod_mime.xml @@ -688,17 +688,14 @@ extensions server config files. An example of its use might be:

    - -
    -
    /foo/.htaccess:
    -
    AddEncoding x-gzip .gz
    - AddType text/plain .asc
    - <Files *.gz.asc>
    -     RemoveEncoding - .gz
    - </Files>
    -
    -     +/foo/.htaccess: +
    +AddEncoding x-gzip .gz
+AddType text/plain .asc
+<Files *.gz.asc>
+  RemoveEncoding .gz
+</Files>
+

    This will cause foo.gz to be marked as being encoded with the gzip method, but foo.gz.asc as an @@ -736,16 +733,12 @@ extensions associations inherited from parent directories or the server config files. An example of its use might be:

    - -
    -
    /foo/.htaccess:
    - -
    AddHandler server-parsed .html
    - -
    /foo/bar/.htaccess:
    +/foo/.htaccess: +AddHandler server-parsed .html + -
    RemoveHandler .html
    -
    +/foo/bar/.htaccess: +RemoveHandler .html

    This has the effect of returning .html files in @@ -869,12 +862,8 @@ extensions associations inherited from parent directories or the server config files. An example of its use might be:

    - -
    -
    /foo/.htaccess:
    - -
    RemoveType .cgi
    -
    +/foo/.htaccess: +RemoveType .cgi

    This will remove any special handling of .cgi diff --git a/docs/manual/mod/mod_mime_magic.html.en b/docs/manual/mod/mod_mime_magic.html.en index f5dbb26d8c..0000f409f5 100644 --- a/docs/manual/mod/mod_mime_magic.html.en +++ b/docs/manual/mod/mod_mime_magic.html.en @@ -1,16 +1,18 @@ -mod_mime_magic - Apache HTTP Server

    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_mime_magic

    Description: - Determines the MIME type of a file - by looking at a few bytes of its contents
    Status: - Extension
    Module Identifier: - mime_magic_module

    Summary

    + -->mod_mime_magic - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_mime_magic

    Description: + Determines the MIME type of a file + by looking at a few bytes of its contents
    Status: + Extension
    Module Identifier: + mime_magic_module

    Summary

    This module determines the MIME type of files in the same way the Unix file(1) command works: it looks at the first few bytes of the file. It is intended as a "second line of defense" - for cases that mod_mime can't + for cases that mod_mime can't resolve. To assure that mod_mime gets first try at determining a file's MIME type, be sure to list mod_mime_magic before mod_mime in the configuration.

    @@ -19,15 +21,15 @@ file(1) command for Unix, which uses "magic numbers" and other hints from a file's contents to figure out what the contents are. This module is active only if the magic - file is specified by the MimeMagicFile directive.

    -

    Directives

    Format of the Magic File

    + file is specified by the MimeMagicFile directive.

    +

    Directives

    Topics

    • Format of the Magic File
    • Performance Issues
    • Notes
    top

    Format of the Magic File

    The contents of the file are plain ASCII text in 4-5 columns. Blank lines are allowed but ignored. Commented lines use a hash mark "#". The remaining lines are parsed for the following columns:

    - +
    @@ -37,7 +39,7 @@ - @@ -48,7 +50,7 @@
    Column
    1byte number to begin checking from
    +     		byte number to begin checking from
    ">" indicates a dependency upon the previous non-">" line
    type of data to match - +
    @@ -140,8 +142,7 @@

    For example, the following magic file lines would recognize some audio formats.

    -
    byte
    -
    +
     # Sun/NeXT audio data
 0       string          .snd
 >12     belong          1               audio/basic
@@ -152,13 +153,11 @@
 >12     belong          6               audio/basic
 >12     belong          7               audio/basic
 >12     belong          23              audio/x-adpcm
-
    
-
    +

    Or these would recognize the difference between "*.doc" files containing Microsoft Word or FrameMaker documents. (These are incompatible file formats which use the same file suffix.)

    -
    -
    +
     # Frame
 0       string          \<MakerFile     application/x-frame
 0       string          \<MIFFile       application/x-frame
@@ -172,18 +171,15 @@
 0       string          \376\067\0\043                  application/msword
 0       string          \320\317\021\340\241\261        application/msword
 0       string          \333\245-\0\0\0                 application/msword
-
    
-
    +

    An optional MIME encoding can be included as a fifth column. For example, this can recognize gzipped files and set the encoding for them.

    -
    -
    +
     # gzip (GNU zip, not to be confused with [Info-ZIP/PKWARE] zip archiver)
 0       string          \037\213        application/octet-stream        x-gzip
-
    
-
    -

    Performance Issues

    + +
    top

    Performance Issues

    This module is not for every system. If your system is barely keeping up with its load or if you're performing a web server benchmark, you may not want to enable this because the @@ -206,7 +202,7 @@ this one is used only as a last resort, just like it was designed to.

    -

    Notes

    +
    top

    Notes

    The following notes apply to the mod_mime_magic module and are included here for compliance with contributors' copyright @@ -270,13 +266,13 @@ * */ -

    MimeMagicFile Directive

    Description: - Enable MIME-type determination based on file contents -using the specified magic file
    Syntax: - MimeMagicFile file-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_mime_magic
    +
    top

    MimeMagicFile Directive

    Description: + Enable MIME-type determination based on file contents +using the specified magic file
    Syntax: + MimeMagicFile file-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_mime_magic

    The MimeMagicFile directive can be used to enable this module, the default file is distributed at conf/magic. Non-rooted paths are relative to the @@ -286,6 +282,6 @@ using the specified magic file

    MimeMagicFile conf/magic
    +

    MimeMagicFile conf/magic

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_negotiation.html.en b/docs/manual/mod/mod_negotiation.html.en index 20d6a5ec3a..acd8d40384 100644 --- a/docs/manual/mod/mod_negotiation.html.en +++ b/docs/manual/mod/mod_negotiation.html.en @@ -1,11 +1,13 @@ -mod_negotiation - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_negotiation

    Description: - Provides for content negotiation
    Status: - Base
    Module Identifier: - negotiation_module

    Summary

    + -->mod_negotiation - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_negotiation

    Description: + Provides for content negotiation
    Status: + Base
    Module Identifier: + negotiation_module

    Summary

    Content negotiation, or more accurately content selection, is the selection of the document that best matches the clients capabilities, from one of several available documents. There @@ -16,11 +18,11 @@ type-map) which explicitly lists the files containing the variants. -

  • A MultiViews search (enabled by the MultiViews Options, where the server does an +
  • A MultiViews search (enabled by the MultiViews Options, where the server does an implicit filename pattern match, and choose from amongst the results.
    • -

    Directives

    See also

    Type maps

    +
    top

    Type maps

    A type map has the same format as RFC822 mail headers. It contains document descriptions separated by blank lines, with lines beginning with a hash character ('#') treated as @@ -36,7 +38,7 @@

    Content-Encoding:
    The encoding of the file. Apache only recognizes - encodings that are defined by an AddEncoding directive. + encodings that are defined by an AddEncoding directive. This normally includes the encodings x-compress for compress'd files, and x-gzip for gzip'd files. The x- prefix is ignored for encoding @@ -83,7 +85,7 @@ Example: -
    Content-Type: image/jpeg; qs=0.8
    +

    Content-Type: image/jpeg; qs=0.8

    URI:
    @@ -105,20 +107,20 @@ delimiter string is found.

    Example:

    -
    -Body:----xyz----
    -<html>
    -<body>
    -<p>Content of the page.</p>
    -</body>
    -</html>
    +

    +Body:----xyz----
    +<html>
    +<body>
    +<p>Content of the page.</p>
    +</body>
    +</html>
    ----xyz---- -

    +

    -

    MultiViews

    +
    top

    MultiViews

    -

    A MultiViews search is enabled by the MultiViews Options. If the server receives a +

    A MultiViews search is enabled by the MultiViews Options. If the server receives a request for /some/dir/foo and /some/dir/foo does not exist, then the server reads the directory looking for all files named @@ -127,15 +129,15 @@ Body:----xyz----
    content-encodings it would have if the client had asked for one of them by name. It then chooses the best match to the client's requirements, and returns that document.

    -

    CacheNegotiatedDocs Directive

    Description: - Allows content-negotiated documents to be -cached by proxy servers
    Syntax: - CacheNegotiatedDocs on|off
    Default: - CacheNegotiatedDocs off
    Context: - server config
    Status: - Base
    Module: - mod_negotiation
    Compatibility: - The syntax changed in version 2.0.
    +
    top

    CacheNegotiatedDocs Directive

    Description: + Allows content-negotiated documents to be +cached by proxy servers
    Syntax: + CacheNegotiatedDocs on|off
    Default: + CacheNegotiatedDocs off
    Context: + server config
    Status: + Base
    Module: + mod_negotiation
    Compatibility: + The syntax changed in version 2.0.

    If set, this directive allows content-negotiated documents to be cached by proxy servers. This could mean that clients behind those proxys could retrieve versions of the documents @@ -151,18 +153,18 @@ cached by proxy serversCacheNegotiatedDocs did not take an argument; it was turned on by the presence of the directive by itself.

    -

    ForceLanguagePriority Directive

    Description: - Action to take if a single acceptable document is not -found
    Syntax: - ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback]
    Default: - ForceLanguagePriority Prefer
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_negotiation
    Compatibility: - Available in version 2.0.30 and later
    +
    top

    ForceLanguagePriority Directive

    Description: + Action to take if a single acceptable document is not +found
    Syntax: + ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback]
    Default: + ForceLanguagePriority Prefer
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_negotiation
    Compatibility: + Available in version 2.0.30 and later

    The ForceLanguagePriority directive uses - the given LanguagePriority to satisfy + the given LanguagePriority to satisfy negotation where the server could otherwise not return a single matching document.

    @@ -174,10 +176,10 @@ found -
    - LanguagePriority en fr de
    +

    + LanguagePriority en fr de
    ForceLanguagePriority Prefer -

    +

    ForceLanguagePriority Fallback uses LanguagePriority to serve a valid result, rather than @@ -187,31 +189,31 @@ found -

    - LanguagePriority en fr de
    +

    + LanguagePriority en fr de
    ForceLanguagePriority Fallback -

    +

    Both options, Prefer and Fallback, may be specified, so either the first matching variant from LanguagePriority will be served if more that one variant is acceptable, or first available document will be served if none of the variants matched the client's acceptable list of languages.

    -

    LanguagePriority Directive

    Description: - The precendence of language variants for cases where -the client does not express a preference
    Syntax: - LanguagePriority MIME-lang [MIME-lang] ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Base
    Module: - mod_negotiation
    +
    top

    LanguagePriority Directive

    Description: + The precendence of language variants for cases where +the client does not express a preference
    Syntax: + LanguagePriority MIME-lang [MIME-lang] ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Base
    Module: + mod_negotiation

    The LanguagePriority sets the precedence of language variants for the case where the client does not express a preference, when handling a MultiViews request. The list of MIME-lang are in order of decreasing preference. Example:

    -
    LanguagePriority en fr de
    +

    LanguagePriority en fr de

    For a request for foo.html, where foo.html.fr and foo.html.de both @@ -219,7 +221,7 @@ the client does not express a preferencefoo.html.fr would be returned.

    Note that this directive only has an effect if a 'best' - language cannot be determined by any other means or the ForceLanguagePriority directive + language cannot be determined by any other means or the ForceLanguagePriority directive is not None. Correctly implemented HTTP/1.1 requests will mean this directive has no effect.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en index c56279f47a..594233f337 100644 --- a/docs/manual/mod/mod_proxy.html.en +++ b/docs/manual/mod/mod_proxy.html.en @@ -1,17 +1,19 @@ -mod_proxy - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_proxy

    Description: - HTTP/1.1 proxy/gateway server
    Status: - Extension
    Module Identifier: - proxy_module

    Summary

    -

    Warning

    + -->mod_proxy - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_proxy

    Description: + HTTP/1.1 proxy/gateway server
    Status: + Extension
    Module Identifier: + proxy_module

    Summary

    +

    Warning

    This document has been updated to take into account changes made in the 2.0 version of the Apache HTTP Server. Some of the information may still be inaccurate, please use it with care. -
    +

    This module implements a proxy/gateway for Apache. It implements proxying capability for @@ -35,12 +37,12 @@ mod_proxy and will be incorporated into a new module, mod_cache.

    If you need to use SSL when contacting remote servers, have a look at the SSLProxy* directives in mod_ssl.

    -

    Do not enable proxying with ProxyRequests until you have +

    Do not enable proxying with ProxyRequests until you have secured your server. Open proxy servers are -dangerous both to your network and to the Internet at large.

    +dangerous both to your network and to the Internet at large.

    -

    Directives

    Common configuration topics

    +
    top

    Common configuration topics

    -

    Forward and Reverse Proxies

    +

    Forward and Reverse Proxies

    Apache can be configured in both a forward and reverse proxy configuration.

    @@ -68,9 +70,9 @@ can also be used to cache data, reducing load on the networks between the forward proxy and the remote webserver.

    Apache's mod_proxy can be figured to behave like a forward proxy -using the ProxyRemote +using the ProxyRemote directive. In addition, caching of data can be achieved by configuring -Apache mod_cache. Other dedicated forward proxy +Apache mod_cache. Other dedicated forward proxy packages include Squid.

    A reverse proxy is a webserver system that is capable of serving webpages @@ -88,46 +90,46 @@ backends. Complex multi-tier webserver systems can be constructed using an Apache mod_proxy frontend and any number of backend webservers.

    The reverse proxy is configured using the -ProxyPass and ProxyPassReverse directives. Caching can be +ProxyPass and ProxyPassReverse directives. Caching can be enabled using mod_cache as with the forward proxy.

    -

    Controlling access to your proxy

    +

    Controlling access to your proxy

    You can control who can access your proxy via the -<Proxy> +<Proxy> control block using the following example:

    -
    -<Proxy *>
    -Order Deny,Allow
    -Deny from all
    -Allow from 192.168.0
    +

    +<Proxy *>
    +Order Deny,Allow
    +Deny from all
    +Allow from 192.168.0
    </Proxy> -

    +

    When configuring a reverse proxy, access control takes on the -attributes of the normal server <directory> configuration.

    +attributes of the normal server <directory> configuration.

    -

    Why doesn't file type xxx +

    Why doesn't file type xxx download via FTP?

    You probably don't have that particular file type defined as application/octet-stream in your proxy's mime.types configuration file. A useful line can be

    -
    +

    application/octet-stream bin dms lha lzh exe class tgz taz -

    +

    -

    How can I force an FTP ASCII download of +

    How can I force an FTP ASCII download of File xxx?

    In the rare situation where you must download a specific file using the FTP @@ -137,7 +139,7 @@ suffixing the request with ;type=a to force an ASCII transfer. (FTP Directory listings are always executed in ASCII mode, however.)

    -

    How can I access FTP files outside +

    How can I access FTP files outside of my home directory?

    @@ -153,10 +155,10 @@ directory).

    Example: To retrieve the file /etc/motd, you would use the URL

    -
    ftp://user@host/%2f/etc/motd
    +

    ftp://user@host/%2f/etc/motd

    -

    How can I hide the FTP cleartext password +

    How can I hide the FTP cleartext password in my browser's URL line?

    @@ -164,10 +166,10 @@ To log in to an FTP server by username and password, Apache uses different strategies. In absense of a user name and password in the URL altogether, Apache sends an anomymous login to the FTP server, i.e.,

    -
    -user: anonymous
    +

    +user: anonymous
    password: apache_proxy@ -

    +

    This works for all popular FTP servers which are configured for anonymous access.

    @@ -184,7 +186,7 @@ display the password in cleartext (which it would if you had used ftp://username:password@host/myfile in the first place).

    -

    Note

    +

    Note

    The password which is transmitted in such a way is not encrypted on its way. It travels between your browser and the Apache proxy server in a base64-encoded cleartext string, and @@ -193,13 +195,13 @@ therefore think twice before accessing your FTP server via HTTP (or before accessing your personal files via FTP at all!) When using unsecure channels, an eavesdropper might intercept your password on its way. -
    + -

    Why does Apache start more slowly when +

    Why does Apache start more slowly when using the proxy module?

    -

    If you're using the ProxyBlock +

    If you're using the ProxyBlock directive, hostnames' IP addresses are looked up and cached during startup for later match test. This may take a few seconds (or more) depending on the speed with which the hostname lookups occur.

    @@ -207,13 +209,13 @@ depending on the speed with which the hostname lookups occur.

    -

    What other functions are useful for an +

    What other functions are useful for an intranet proxy server?

    An Apache proxy server situated in an intranet needs to forward external requests through the company's firewall. However, when it has to access resources within the intranet, it can bypass the firewall -when accessing hosts. The NoProxy directive is useful for +when accessing hosts. The NoProxy directive is useful for specifying which hosts belong to the intranet and should be accessed directly.

    @@ -221,50 +223,50 @@ directly.

    WWW requests, thus requesting "http://somehost/" instead of "http://somehost.my.dom.ain/". Some commercial proxy servers let them get away with this and simply serve the request, implying a configured -local domain. When the ProxyDomain directive +local domain. When the ProxyDomain directive is used and the server is configured for proxy service, Apache can return a redirect response and send the client to the correct, fully qualified, server address. This is the preferred method since the user's bookmark files will then contain fully qualified hosts.

    -

    How can I make the proxy talk HTTP/1.0 and +

    How can I make the proxy talk HTTP/1.0 and disable keepalives?

    For circumstances where you have a application server which doesn't implement keepalives or HTTP/1.1 properly, there are 2 environment variables which when -set send a HTTP/1.0 with no keepalive. These are set via the SetEnv directive.

    +set send a HTTP/1.0 with no keepalive. These are set via the SetEnv directive.

    These are the 'force-proxy-request-1.0' and 'proxy-nokeepalive' notes.

    -
    -<location /buggyappserver/ >
    -ProxyPass http://buggyappserver:7001/foo/
    -SetEnv force-proxy-request-1.0 1
    -SetEnv proxy-nokeepalive 1
    +

    +<location /buggyappserver/ >
    +ProxyPass http://buggyappserver:7001/foo/
    +SetEnv force-proxy-request-1.0 1
    +SetEnv proxy-nokeepalive 1
    </location> -

    +

    -

    AllowCONNECT Directive

    Description: - Ports that are allowed to CONNECT through -the proxy
    Syntax: - AllowCONNECT port [port] ...
    Default: - AllowCONNECT 443 563
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +
    top

    AllowCONNECT Directive

    Description: + Ports that are allowed to CONNECT through +the proxy
    Syntax: + AllowCONNECT port [port] ...
    Default: + AllowCONNECT 443 563
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    The AllowCONNECT directive specifies a list of port numbers to which the proxy CONNECT method may connect. Today's browsers use this method when a https connection is requested and proxy tunneling over http is in -effect.
    By default, only the default https port (443) and the +effect.
    By default, only the default https port (443) and the default snews port (563) are enabled. Use the AllowCONNECT directive to overrride this default and allow connections to the listed ports only.

    -

    NoProxy Directive

    Description: - Hosts, domains, or networks that will be connected -to directly
    Syntax: - NoProxy +
    top

    NoProxy Directive

    Description: + Hosts, domains, or networks that will be connected +to directly
    Syntax: + NoProxy Domain| SubNet| IpAddr| @@ -272,21 +274,21 @@ to directly
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    + Hostname] ...
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    This directive is only useful for Apache proxy servers within intranets. The NoProxy directive specifies a list of subnets, IP addresses, hosts and/or domains, separated by spaces. A request to a host which matches one or more of these is always served directly, without forwarding to the configured -ProxyRemote proxy server(s).

    +ProxyRemote proxy server(s).

    -

    Example

    - ProxyRemote * http://firewall.mycompany.com:81
    +

    Example

    + ProxyRemote * http://firewall.mycompany.com:81
    NoProxy .mycompany.com 192.168.112.0/21 -

    +

    The arguments to the NoProxy directive are one of the following type list:

    @@ -297,12 +299,12 @@ always served directly, without forwarding to the configured by a period. It represents a list of hosts which logically belong to the same DNS domain or zone (i.e., the suffixes of the hostnames are all ending in - Domain).
    - Examples: .com .apache.org.
    + Domain).
    + Examples: .com .apache.org.
    To distinguish Domains from Hostnames (both syntactically and semantically; a DNS domain can have a DNS A record, too!), Domains are always written - with a leading period.
    + with a leading period.
    Note: Domain name comparisons are done without regard to the case, and Domains are always assumed to be anchored in the root of the DNS tree, therefore two domains .MyDomain.com and @@ -320,7 +322,7 @@ always served directly, without forwarding to the configured be reached over a common network interface. In the absence of the explicit net mask it is assumed that omitted (or zero valued) trailing digits specify the mask. (In this case, the netmask can - only be multiples of 8 bits wide.)
    + only be multiples of 8 bits wide.)
    Examples:
    192.168 or 192.168.0.0
    @@ -341,8 +343,8 @@ always served directly, without forwarding to the configured
    A IPAddr represents a fully qualified internet address in numeric (dotted quad) form. Usually, this address represents a host, but there need not necessarily be a DNS domain name - connected with the address.
    - Example: 192.168.123.7
    + connected with the address.
    + Example: 192.168.123.7
    Note: An IPAddr does not need to be resolved by the DNS system, so it can result in more effective apache performance.
    @@ -354,28 +356,28 @@ always served directly, without forwarding to the configured It represents a logical host (in contrast to Domains, see above) and must be resolvable to at least one IPAddr (or often to a list of hosts - with different IPAddr's).
    + with different IPAddr's).
    Examples: prep.ai.mit.edu - www.apache.org.
    + www.apache.org.
    Note: In many situations, it is more effective to specify an IPAddr in place of a Hostname since a DNS lookup can be avoided. Name resolution in Apache can take a remarkable deal of time when the connection to the name server uses a slow PPP - link.
    + link.
    Note: Hostname comparisons are done without regard to the case, and Hostnames are always assumed to be anchored in the root of the DNS tree, therefore two hosts WWW.MyDomain.com and www.mydomain.com. (note the trailing period) are considered equal.
    -

    See also

    <Proxy> Directive

    Description: - Container for directives applied to proxied -resources
    Syntax: - <Proxy wildcard-url> ...</Proxy>
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +

    See also

    top

    <Proxy> Directive

    Description: + Container for directives applied to proxied +resources
    Syntax: + <Proxy wildcard-url> ...</Proxy>
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    Directives placed in <Proxy> sections apply only to matching proxied content. Shell-style wildcards are allowed.

    @@ -384,31 +386,31 @@ wildcards are allowed.

    yournetwork.example.com to access content via your proxy server:

    -
    -<Proxy *>
    -  Order Deny,Allow
    -  Deny from all
    -  Allow from yournetwork.example.com
    +

    +<Proxy *>
    +  Order Deny,Allow
    +  Deny from all
    +  Allow from yournetwork.example.com
    </Proxy> -

    +

    The following example will process all files in the foo directory of example.com through the INCLUDES filter when they are sent through the proxy server:

    -
    -<Proxy http://example.com/foo/*>
    -  SetOutputFilter INCLUDES
    +

    +<Proxy http://example.com/foo/*>
    +  SetOutputFilter INCLUDES
    </Proxy> -

    -

    ProxyBlock Directive

    Description: - Words, hosts, or domains that are banned from being -proxied
    Syntax: - ProxyBlock *|word|host|domain -[word|host|domain] ...
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +

    +
    top

    ProxyBlock Directive

    Description: + Words, hosts, or domains that are banned from being +proxied
    Syntax: + ProxyBlock *|word|host|domain +[word|host|domain] ...
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    The ProxyBlock directive specifies a list of words, hosts and/or domains, separated by spaces. HTTP, HTTPS, and FTP document requests to sites whose names contain matched words, @@ -417,9 +419,9 @@ module will also attempt to determine IP addresses of list items which may be hostnames during startup, and cache them for match test as well. Example:

    -
    +

    ProxyBlock joes-garage.com some-host.co.uk rocky.wotsamattau.edu -

    +

    'rocky.wotsamattau.edu' would also be matched if referenced by IP address.

    @@ -429,18 +431,18 @@ address.

    Note also that

    -
    +

    ProxyBlock * -

    +

    blocks connections to all sites.

    -

    ProxyDomain Directive

    Description: - Default domain name for proxied requests
    Syntax: - ProxyDomain Domain
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +
    top

    ProxyDomain Directive

    Description: + Default domain name for proxied requests
    Syntax: + ProxyDomain Domain
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    This directive is only useful for Apache proxy servers within intranets. The ProxyDomain directive specifies the default domain which the apache proxy server will belong to. If a @@ -448,66 +450,66 @@ request to a host without a domain name is encountered, a redirection response to the same host with the configured Domain appended will be generated.

    -

    Example

    - ProxyRemote * http://firewall.mycompany.com:81
    - NoProxy .mycompany.com 192.168.112.0/21
    +

    Example

    + ProxyRemote * http://firewall.mycompany.com:81
    + NoProxy .mycompany.com 192.168.112.0/21
    ProxyDomain .mycompany.com -

    -

    ProxyErrorOverride Directive

    Description: - Override error pages for proxied content
    Syntax: - ProxyErrorOverride On|Off
    Default: - ProxyErrorOverride Off
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    Compatibility: - Available in version 2.0 and later
    +

    +
    top

    ProxyErrorOverride Directive

    Description: + Override error pages for proxied content
    Syntax: + ProxyErrorOverride On|Off
    Default: + ProxyErrorOverride Off
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy
    Compatibility: + Available in version 2.0 and later

    This directive is useful for reverse-proxy setups, where you want to have a common look and feel on the error pages seen by the end user. This also allows for included files (via mod_include's SSI) to get the error code and act accordingly (default behavior would display the error page of the proxied server, turning this on shows the SSI Error message).

    -

    ProxyIOBufferSize Directive

    Description: - IO buffer size for outgoing HTTP and FTP -connections
    Syntax: - ProxyIOBufferSize bytes
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    - -

    <ProxyMatch> Directive

    Description: - Container for directives applied to regular-expression-matched -proxied resources
    Syntax: - <Proxy regex> ...</Proxy>
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +
    top

    ProxyIOBufferSize Directive

    Description: + IO buffer size for outgoing HTTP and FTP +connections
    Syntax: + ProxyIOBufferSize bytes
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy
    + +
    top

    <ProxyMatch> Directive

    Description: + Container for directives applied to regular-expression-matched +proxied resources
    Syntax: + <Proxy regex> ...</Proxy>
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    The <ProxyMatch> directive is -identical to the <Proxy> directive, except it matches URLs +identical to the <Proxy> directive, except it matches URLs using regular expressions.

    -

    ProxyMaxForwards Directive

    Description: - Maximium number of proxies that a request can be forwarded -through
    Syntax: - ProxyMaxForwards number
    Default: - ProxyMaxForwards 10
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    Compatibility: - Available in Apache 2.0 and later
    +
    top

    ProxyMaxForwards Directive

    Description: + Maximium number of proxies that a request can be forwarded +through
    Syntax: + ProxyMaxForwards number
    Default: + ProxyMaxForwards 10
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy
    Compatibility: + Available in Apache 2.0 and later

    The ProxyMaxForwards directive specifies the maximum number of proxies through which a request may pass. This is set to prevent infinite proxy loops, or a DoS attack.

    -

    Example

    +

    Example

    ProxyMaxForwards 10 -

    -

    ProxyPass Directive

    Description: - Maps remote servers into the local server -URL-space
    Syntax: - ProxyPass [path] !|url
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +

    +
    top

    ProxyPass Directive

    Description: + Maps remote servers into the local server +URL-space
    Syntax: + ProxyPass [path] !|url
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    This directive allows remote servers to be mapped into the space of the local server; the local server does not act as a proxy in the conventional sense, but appears to be a mirror of the remote @@ -517,9 +519,9 @@ include a query string.

    Suppose the local server has address http://wibble.org/; then

    -
    +

    ProxyPass /mirror/foo/ http://foo.com/ -

    +

    will cause a local request for the <http://wibble.org/mirror/foo/bar> to be internally converted into a proxy request to @@ -527,45 +529,45 @@ internally converted into a proxy request to

    The ! directive is useful in situations where you don't want to reverse-proxy a subdirectory. eg.

    -
    - ProxyPass /mirror/foo/i !
    +

    + ProxyPass /mirror/foo/i !
    ProxyPass /mirror/foo http://foo.com -

    +

    will proxy all requests to /mirror/foo to foo.com EXCEPT requests made to /mirror/foo/i

    -
    NB: order is important. you need to put the exclusions BEFORE the general proxypass directive
    +
    NB: order is important. you need to put the exclusions BEFORE the general proxypass directive
    -

    When used inside a <Location> section, the first argument is -ommitted and the local directory is obtained from the <Location>.

    +

    When used inside a <Location> section, the first argument is +ommitted and the local directory is obtained from the <Location>.

    If you require a more flexible reverse-proxy configuration, see -the RewriteRule directive +the RewriteRule directive with the [P] flag.

    -

    ProxyPassReverse Directive

    Description: - Adjusts the URL in HTTP response headers sent from -a reverse proxied server
    Syntax: - ProxyPassReverse [path] url
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +
    top

    ProxyPassReverse Directive

    Description: + Adjusts the URL in HTTP response headers sent from +a reverse proxied server
    Syntax: + ProxyPassReverse [path] url
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    This directive lets Apache adjust the URL in the Location, Content-Location and URI headers on HTTP redirect responses. This is essential when Apache is used as a reverse proxy to avoid by-passing the reverse proxy because of HTTP redirects on the backend servers which stay behind the reverse proxy.

    -

    path is the name of a local virtual path.
    +

    path is the name of a local virtual path.
    url is a partial URL for the remote server - the same way they are -used for the ProxyPass directive.

    +used for the ProxyPass directive.

    -Example:
    +Example:
    Suppose the local server has address http://wibble.org/; then

    -
    - ProxyPass /mirror/foo/ http://foo.com/
    +

    + ProxyPass /mirror/foo/ http://foo.com/
    ProxyPassReverse /mirror/foo/ http://foo.com/ -

    +

    will not only cause a local request for the <http://wibble.org/mirror/foo/bar> to be internally converted into a proxy request to <http://foo.com/bar> (the @@ -578,49 +580,49 @@ redirect response to the client.

    Note that this ProxyPassReverse directive can also be used in conjunction with the proxy pass-through feature ("RewriteRule ... [P]") from -mod_rewrite because its doesn't depend on a -corresponding ProxyPass +mod_rewrite because its doesn't depend on a +corresponding ProxyPass directive.

    -

    When used inside a <Location> section, the first argument is -ommitted and the local directory is obtained from the <Location>.

    - -

    ProxyPreserveHost Directive

    Description: - Use incoming Host HTTP request header for -proxy request
    Syntax: - ProxyPreserveHost on|off
    Default: - ProxyPreserveHost Off
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    Compatibility: - Available in -Apache 2.0.31 and later.
    +

    When used inside a <Location> section, the first argument is +ommitted and the local directory is obtained from the <Location>.

    + +
    top

    ProxyPreserveHost Directive

    Description: + Use incoming Host HTTP request header for +proxy request
    Syntax: + ProxyPreserveHost on|off
    Default: + ProxyPreserveHost Off
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy
    Compatibility: + Available in +Apache 2.0.31 and later.

    When enabled, this option will pass the Host: line from the incoming request to the proxied host, instead of the hostname specified in the proxypass line.

    This option should normally be turned 'off'.

    -

    ProxyReceiveBufferSize Directive

    Description: - Network buffer size for outgoing HTTP and FTP -connections
    Syntax: - ProxyReceiveBufferSize bytes
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +
    top

    ProxyReceiveBufferSize Directive

    Description: + Network buffer size for outgoing HTTP and FTP +connections
    Syntax: + ProxyReceiveBufferSize bytes
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    The ProxyReceiveBufferSize directive specifies an explicit network buffer size for outgoing HTTP and FTP connections, for increased throughput. It has to be greater than 512 or set to 0 to indicate that the system's default buffer size should be used.

    -

    Example

    +

    Example

    ProxyReceiveBufferSize 2048 -

    -

    ProxyRemote Directive

    Description: - Remote proxy used to handle certain requests
    Syntax: - ProxyRemote match remote-server
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +

    +
    top

    ProxyRemote Directive

    Description: + Remote proxy used to handle certain requests
    Syntax: + ProxyRemote match remote-server
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    This defines remote proxies to this proxy. match is either the name of a URL-scheme that the remote server supports, or a partial URL for which the remote server should be used, or '*' to indicate the @@ -636,11 +638,11 @@ with the remote server; only "http" is supported by this module.

    Example:

    -
    - ProxyRemote http://goodguys.com/ http://mirrorguys.com:8000
    - ProxyRemote * http://cleversite.com
    +

    + ProxyRemote http://goodguys.com/ http://mirrorguys.com:8000
    + ProxyRemote * http://cleversite.com
    ProxyRemote ftp http://ftpproxy.mydomain.com:8080 -

    +

    In the last example, the proxy will forward FTP requests, encapsulated as yet another HTTP proxy request, to another proxy which can handle @@ -649,57 +651,57 @@ them.

    This option also supports reverse proxy configuration - a backend webserver can be embedded within a virtualhost URL space even if that server is hidden by another forward proxy.

    -

    ProxyRemoteMatch Directive

    Description: - Remote proxy used to handle requests -matched by regular expressions
    Syntax: - ProxyRemote regex remote-server
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +
    top

    ProxyRemoteMatch Directive

    Description: + Remote proxy used to handle requests +matched by regular expressions
    Syntax: + ProxyRemote regex remote-server
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    The ProxyRemoteMatch is identical -to the ProxyRemote +to the ProxyRemote directive, except the first argument is a regular expression match against the requested URL.

    -

    ProxyRequests Directive

    Description: - Enables forward (standard) proxy requests
    Syntax: - ProxyRequests on|off
    Default: - ProxyRequests Off
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +
    top

    ProxyRequests Directive

    Description: + Enables forward (standard) proxy requests
    Syntax: + ProxyRequests on|off
    Default: + ProxyRequests Off
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    This allows or prevents Apache from functioning as a forward proxy server. (Setting ProxyRequests to 'off' does not disable use of the -ProxyPass directive.)

    +ProxyPass directive.)

    In a typical reverse proxy configuration, this option should be set to 'off'.

    -

    Do not enable proxying with ProxyRequests until you have +

    Do not enable proxying with ProxyRequests until you have secured your server. Open proxy servers are -dangerous both to your network and to the Internet at large.

    - -

    ProxyTimeout Directive

    Description: - Network timeout for proxied requests
    Syntax: - ProxyTimeout seconds
    Default: - ProxyTimeout 300
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    Compatibility: - Available in -Apache 2.0.31 and later
    +dangerous both to your network and to the Internet at large.

    + +
    top

    ProxyTimeout Directive

    Description: + Network timeout for proxied requests
    Syntax: + ProxyTimeout seconds
    Default: + ProxyTimeout 300
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy
    Compatibility: + Available in +Apache 2.0.31 and later

    This directive allows a user to specifiy a timeout on proxy requests. This is usefull when you have a slow/buggy appserver which hangs, and you would rather just return a timeout and fail gracefully instead of waiting however long it takes the server to return

    -

    ProxyVia Directive

    Description: - Information provided in the Via HTTP response -header for proxied requests
    Syntax: - ProxyVia on|off|full|block
    Default: - ProxyVia off
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_proxy
    +
    top

    ProxyVia Directive

    Description: + Information provided in the Via HTTP response +header for proxied requests
    Syntax: + ProxyVia on|off|full|block
    Default: + ProxyVia off
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_proxy

    This directive controls the use of the Via: HTTP header by the proxy. Its intended use is to control the flow of of proxy requests along a chain of proxy servers. See RFC2068 (HTTP/1.1) @@ -722,4 +724,4 @@ line will additionally have the Apache server version shown as a proxy request will have all its Via: header lines removed. No new Via: header will be generated. -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_rewrite.html.en b/docs/manual/mod/mod_rewrite.html.en index 76eee96b75..a52c779809 100644 --- a/docs/manual/mod/mod_rewrite.html.en +++ b/docs/manual/mod/mod_rewrite.html.en @@ -1,33 +1,35 @@ -mod_rewrite - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_rewrite

    Description: - Provides a rule-based rewriting engine to rewrite requested -URLs on the fly
    Status: - Extension
    Module Identifier: - rewrite_module
    Compatibility: - Available in Apache 1.3 and later

    Summary

    + -->mod_rewrite - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_rewrite

    Description: + Provides a rule-based rewriting engine to rewrite requested +URLs on the fly
    Status: + Extension
    Module Identifier: + rewrite_module
    Compatibility: + Available in Apache 1.3 and later

    Summary

    - ``The great thing about mod_rewrite is it gives you +

    ``The great thing about mod_rewrite is it gives you all the configurability and flexibility of Sendmail. The downside to mod_rewrite is that it gives you all - the configurability and flexibility of Sendmail.''
    + the configurability and flexibility of Sendmail.''

    -      -- Brian Behlendorf
    -      Apache Group +

    -- Brian Behlendorf
    + Apache Group

    - `` Despite the tons of examples and docs, +

    `` Despite the tons of examples and docs, mod_rewrite is voodoo. Damned cool voodoo, but still - voodoo. ''
    + voodoo. ''

    -     -- Brian Moore
    -      bem@news.cmc.net +

    -- Brian Moore
    + bem@news.cmc.net

    -
    +

    Welcome to mod_rewrite, the Swiss Army Knife of URL @@ -60,20 +62,20 @@ URLs on the fly Ralf S. - Engelschall
    - rse@engelschall.com
    + Engelschall
    + rse@engelschall.com
    www.engelschall.com - -

    Directives

    Interal Processing

    +

    +
    top

    Interal Processing

    The internal processing of this module is very complex but needs to be explained once even to the average user to avoid common mistakes and to let you exploit its full functionality.

    -

    API Phases

    +

    API Phases

    First you have to understand that when Apache processes a HTTP request it does this in phases. A hook for each of these @@ -142,7 +144,7 @@ URLs on the flyRuleset Processing +

    Ruleset Processing

    Now when mod_rewrite is triggered in these two API phases, it reads the configured rulesets from its configuration @@ -158,16 +160,16 @@ URLs on the flyRewriteRule directives) and + through the ruleset rule by rule (RewriteRule directives) and when a particular rule matches it optionally loops through existing corresponding conditions (RewriteCond directives). For historical reasons the conditions are given first, and so the control flow is a little bit long-winded. See Figure 1 for more details.

    -
    - [Needs graphics capability to display] -

    Figure 1:The control flow through the rewriting ruleset

    -
    +

    + [Needs graphics capability to display]
    + Figure 1:The control flow through the rewriting ruleset +

    As you can see, first the URL is matched against the Pattern of each rule. When it fails mod_rewrite immediately stops processing this rule and continues with the @@ -191,7 +193,7 @@ URLs on the flyQuoting Special Characters +

    Quoting Special Characters

    As of Apache 1.3.20, special characters in TestString and Substitution strings can be @@ -203,7 +205,7 @@ URLs on the flyRegex Back-Reference Availability +

    Regex Back-Reference Availability

    One important thing here has to be remembered: Whenever you use parentheses in Pattern or in one of the @@ -214,17 +216,17 @@ URLs on the fly -

    Figure 2: The back-reference flow through a rule.

    - +

    + [Needs graphics capability to display]
    + Figure 2: The back-reference flow through a rule. +

    We know this was a crash course on mod_rewrite's internal processing. But you will benefit from this knowledge when reading the following documentation of the available directives.

    -

    Environment Variables

    +
    top

    Environment Variables

    This module keeps track of two additional (non-standard) CGI/SSI environment variables named SCRIPT_URL @@ -240,35 +242,31 @@ URLs on the fly -

    +
    Example
     SCRIPT_NAME=/sw/lib/w3s/tree/global/u/rse/.www/index.html
 SCRIPT_FILENAME=/u/rse/.www/index.html
 SCRIPT_URL=/u/rse/
 SCRIPT_URI=http://en1.engelschall.com/u/rse/
-
    
-    
+
    -

    Practical Solutions

    +
    top

    Practical Solutions

    We also have an URL Rewriting Guide available, which provides a collection of practical solutions for URL-based problems. There you can find real-life rulesets and additional information about mod_rewrite.

    -

    RewriteBase Directive

    Description: - Sets the base URL for per-directory rewrites
    Syntax: - RewriteBase URL-path
    Default: - See usage for information.
    Context: - directory, .htaccess
    Override: - FileInfo
    Status: - Extension
    Module: - mod_rewrite
    +
    top

    RewriteBase Directive

    Description: + Sets the base URL for per-directory rewrites
    Syntax: + RewriteBase URL-path
    Default: + See usage for information.
    Context: + directory, .htaccess
    Override: + FileInfo
    Status: + Extension
    Module: + mod_rewrite

    The RewriteBase directive explicitly sets the base URL for per-directory rewrites. As you will see - below, RewriteRule + below, RewriteRule can be used in per-directory config files (.htaccess). There it will act locally, i.e., the local directory prefix is stripped at this @@ -286,16 +284,15 @@ SCRIPT_URI=http://en1.engelschall.com/u/rse/ use the RewriteBase directive to specify the correct URL-prefix.

    -
    If your webserver's URLs are not directly +
    If your webserver's URLs are not directly related to physical file paths, you have to use RewriteBase in every .htaccess -files where you want to use RewriteRule directives. -
    +files where you want to use RewriteRule directives. +

    For example, assume the following per-directory config file:

    -
    -
    +
     #
 #  /abc/def/.htaccess -- per-dir config file for directory /abc/def
 #  Remember: /abc/def is the physical path of /xyz, i.e., the server
@@ -310,14 +307,13 @@ RewriteBase   /xyz
 
 #  now the rewriting rules
 RewriteRule   ^oldstuff\.html$  newstuff.html
-
    
-
    +

    In the above example, a request to /xyz/oldstuff.html gets correctly rewritten to the physical file /abc/def/newstuff.html.

    -

    For Apache Hackers

    +

    For Apache Hackers

    The following list gives detailed information about the internal processing steps:

    @@ -344,20 +340,20 @@ Result:
               procedure is used by many other operations inside
               Apache. So, you can be sure the design and
               implementation is correct.
    
-
    - -

    RewriteCond Directive

    Description: - Defines a condition under which rewriting will take place -
    Syntax: - RewriteCond - TestString CondPattern
    Default: - None
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Extension
    Module: - mod_rewrite
    + + +
    top

    RewriteCond Directive

    Description: + Defines a condition under which rewriting will take place +
    Syntax: + RewriteCond + TestString CondPattern
    Default: + None
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Extension
    Module: + mod_rewrite

    The RewriteCond directive defines a - rule condition. Precede a RewriteRule directive with one + rule condition. Precede a RewriteRule directive with one or more RewriteCond directives. The following rewriting rule is only used if its pattern matches the current state of the URI and if these additional @@ -371,9 +367,9 @@ Result: RewriteRule backreferences: These are backreferences of the form -

    +

    $N -

    +

    (0 <= N <= 9) which provide access to the grouped parts (parenthesis!) of the pattern from the corresponding RewriteRule directive (the one @@ -385,9 +381,9 @@ Result: RewriteCond backreferences: These are backreferences of the form -
    +

    %N -

    +

    (1 <= N <= 9) which provide access to the grouped parts (parentheses!) of the pattern from the last matched RewriteCond directive in the current bunch @@ -398,9 +394,9 @@ Result: RewriteMap expansions: These are expansions of the form -
    +

    ${mapname:key|default} -

    +

    See the documentation for RewriteMap for more details. @@ -409,86 +405,81 @@ Result: Server-Variables: These are variables of the form -
    +

    %{ NAME_OF_VARIABLE } -

    +

    where NAME_OF_VARIABLE can be a string taken from the following list: - +
    - + + + + + - + + + +
    - HTTP headers: - -

    HTTP_USER_AGENT
    - HTTP_REFERER
    - HTTP_COOKIE
    - HTTP_FORWARDED
    - HTTP_HOST
    - HTTP_PROXY_CONNECTION
    - HTTP_ACCEPT
    -

    +     		HTTP headers: connection & request: +
    + HTTP_USER_AGENT
    + HTTP_REFERER
    + HTTP_COOKIE
    + HTTP_FORWARDED
    + HTTP_HOST
    + HTTP_PROXY_CONNECTION
    + HTTP_ACCEPT
    		 - connection & request: - -

    REMOTE_ADDR
    - REMOTE_HOST
    - REMOTE_USER
    - REMOTE_IDENT
    - REQUEST_METHOD
    - SCRIPT_FILENAME
    - PATH_INFO
    - QUERY_STRING
    - AUTH_TYPE
    -

    + REMOTE_ADDR
    + REMOTE_HOST
    + REMOTE_USER
    + REMOTE_IDENT
    + REQUEST_METHOD
    + SCRIPT_FILENAME
    + PATH_INFO
    + QUERY_STRING
    + AUTH_TYPE
    - server internals: - -

    DOCUMENT_ROOT
    - SERVER_ADMIN
    - SERVER_NAME
    - SERVER_ADDR
    - SERVER_PORT
    - SERVER_PROTOCOL
    - SERVER_SOFTWARE
    -

    +     		server internals: system stuff: specials:
    + DOCUMENT_ROOT
    + SERVER_ADMIN
    + SERVER_NAME
    + SERVER_ADDR
    + SERVER_PORT
    + SERVER_PROTOCOL
    + SERVER_SOFTWARE
    		 - system stuff: - -

    TIME_YEAR
    - TIME_MON
    - TIME_DAY
    - TIME_HOUR
    - TIME_MIN
    - TIME_SEC
    - TIME_WDAY
    - TIME
    -

    + TIME_YEAR
    + TIME_MON
    + TIME_DAY
    + TIME_HOUR
    + TIME_MIN
    + TIME_SEC
    + TIME_WDAY
    + TIME
    		 - specials: - -

    API_VERSION
    - THE_REQUEST
    - REQUEST_URI
    - REQUEST_FILENAME
    - IS_SUBREQ
    -

    + API_VERSION
    + THE_REQUEST
    + REQUEST_URI
    + REQUEST_FILENAME
    + IS_SUBREQ
    -
    +

    These variables all correspond to the similarly named HTTP MIME-headers, C variables of the Apache server or @@ -536,7 +527,7 @@ Result:

    The full local filesystem path to the file or script matching the request.
    -
    +
    @@ -612,21 +603,21 @@ Result:
    • '<CondPattern' (is lexically - lower)
      + lower)
      Treats the CondPattern as a plain string and compares it lexically to TestString. True if TestString is lexically lower than CondPattern.
    • '>CondPattern' (is lexically - greater)
      + greater)
      Treats the CondPattern as a plain string and compares it lexically to TestString. True if TestString is lexically greater than CondPattern.
    • '=CondPattern' (is lexically - equal)
      + equal)
      Treats the CondPattern as a plain string and compares it lexically to TestString. True if TestString is lexically equal to @@ -636,28 +627,28 @@ Result: compares TestString to the empty string.
    • '-d' (is - directory)
      + directory)
      Treats the TestString as a pathname and tests if it exists and is a directory.
    • '-f' (is regular - file)
      + file)
      Treats the TestString as a pathname and tests if it exists and is a regular file.
    • '-s' (is regular file with - size)
      + size)
      Treats the TestString as a pathname and tests if it exists and is a regular file with size greater than zero.
    • '-l' (is symbolic - link)
      + link)
      Treats the TestString as a pathname and tests if it exists and is a symbolic link.
    • '-F' (is existing file via - subrequest)
      + subrequest)
      Checks if TestString is a valid file and accessible via all the server's currently-configured access controls for that path. This uses an internal @@ -665,7 +656,7 @@ Result: because it decreases your servers performance!
    • '-U' (is existing URL via - subrequest)
      + subrequest)
      Checks if TestString is a valid URL and accessible via all the server's currently-configured access controls for that path. This uses an internal @@ -673,20 +664,20 @@ Result: because it decreases your server's performance!
    -

    Notice

    +

    Notice

    All of these tests can also be prefixed by an exclamation mark ('!') to negate their meaning. -
    +

    Additionally you can set special flags for CondPattern by appending

    -
    +

    [flags] -

    +

    as the third argument to the RewriteCond directive. Flags is a comma-separated list of the @@ -694,7 +685,7 @@ Result:

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_ssl.html.en b/docs/manual/mod/mod_ssl.html.en index 03f4c2f93c..485639e302 100644 --- a/docs/manual/mod/mod_ssl.html.en +++ b/docs/manual/mod/mod_ssl.html.en @@ -1,12 +1,14 @@ -mod_ssl - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_ssl

    Description: - Strong cryptography using the Secure Sockets -Layer (SSL) and Transport Layer Security (TLS) protocols
    Status: - Extension
    Module Identifier: - ssl_module

    Summary

    + -->mod_ssl - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_ssl

    Description: + Strong cryptography using the Secure Sockets +Layer (SSL) and Transport Layer Security (TLS) protocols
    Status: + Extension
    Module Identifier: + ssl_module

    Summary

    This module provides SSL v2/v3 and TLS v1 support for the Apache HTTP Server. It was contributed by Ralf S. Engeschall based on his mod_ssl project and originally derived from work by Ben Laurie.

    @@ -16,7 +18,7 @@ to provide the cryptography engine.

    Further details, discussion, and examples are provided in the SSL documentation.

    -

    Directives

    Environment Variables

    +
    top

    Environment Variables

    This module provides a lot of SSL information as additional environment variables to the SSI and CGI namespace. The generated variables are listed in @@ -24,16 +26,11 @@ the table below. For backward compatibility the information can be made available under different names, too. Look in the Compatibility chapter for details on the compatibility variables.

    - - -
    - - -
    - +
    - - - + + + @@ -68,17 +65,14 @@ compatibility variables.

    +
    Variable Name:Value Type:Description:Variable Name:Value Type:Description:
    HTTPS flag HTTPS is being used.
    SSL_PROTOCOL string The SSL protocol version (SSLv2, SSLv3, TLSv1)
    SSL_SERVER_A_SIG string Algorithm used for the signature of server's certificate
    SSL_SERVER_A_KEY string Algorithm used for the public key of server's certificate
    SSL_SERVER_CERT string PEM-encoded server certificate
    [ where x509 is a component of a X.509 DN: + C,ST,L,O,OU,CN,T,I,G,S,D,UID,Email ]
    -[ where x509 is a component of a X.509 DN: - C,ST,L,O,OU,CN,T,I,G,S,D,UID,Email ] -
    -
    -

    Custom Log Formats

    +
    top

    Custom Log Formats

    -

    When mod_ssl is built into Apache or at least +

    When mod_ssl is built into Apache or at least loaded (under DSO situation) additional functions exist for the Custom Log Format of -mod_log_config. First there is an +mod_log_config. First there is an additional ``%{varname}x'' eXtension format function which can be used to expand any variables provided by any module, especially those provided by mod_ssl which can @@ -89,34 +83,34 @@ For backward compatibility there is additionally a special provided. Information about this function is provided in the Compatibility chapter.

    Example:

    -
    +

    CustomLog logs/ssl_request_log \ "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" -

    -

    SSLCACertificateFile Directive

    Description: - File of concatenated PEM-encoded CA Certificates -for Client Auth
    Syntax: - SSLCACertificateFile file-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLCACertificateFile Directive

    Description: + File of concatenated PEM-encoded CA Certificates +for Client Auth
    Syntax: + SSLCACertificateFile file-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the all-in-one file where you can assemble the Certificates of Certification Authorities (CA) whose clients you deal with. These are used for Client Authentication. Such a file is simply the concatenation of the various PEM-encoded Certificate files, in order of preference. This can be used alternatively and/or additionally to -SSLCACertificatePath.

    -

    Example

    +SSLCACertificatePath.

    +

    Example

    SSLCACertificateFile /usr/local/apache/conf/ssl.crt/ca-bundle-client.crt -

    -

    SSLCACertificatePath Directive

    Description: - Directory of PEM-encoded CA Certificates for -Client Auth
    Syntax: - SSLCACertificatePath directory-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLCACertificatePath Directive

    Description: + Directory of PEM-encoded CA Certificates for +Client Auth
    Syntax: + SSLCACertificatePath directory-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the directory where you keep the Certificates of Certification Authorities (CAs) whose clients you deal with. These are used to @@ -128,33 +122,33 @@ there: you also have to create symbolic links named hash-value.N. And you should always make sure this directory contains the appropriate symbolic links. Use the Makefile which comes with mod_ssl to accomplish this task.

    -

    Example

    +

    Example

    SSLCACertificatePath /usr/local/apache/conf/ssl.crt/ -

    -

    SSLCARevocationFile Directive

    Description: - File of concatenated PEM-encoded CA CRLs for -Client Auth
    Syntax: - SSLCARevocationFile file-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLCARevocationFile Directive

    Description: + File of concatenated PEM-encoded CA CRLs for +Client Auth
    Syntax: + SSLCARevocationFile file-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the all-in-one file where you can assemble the Certificate Revocation Lists (CRL) of Certification Authorities (CA) whose clients you deal with. These are used for Client Authentication. Such a file is simply the concatenation of the various PEM-encoded CRL files, in order of preference. This can be -used alternatively and/or additionally to SSLCARevocationPath.

    -

    Example

    +used alternatively and/or additionally to SSLCARevocationPath.

    +

    Example

    SSLCARevocationFile /usr/local/apache/conf/ssl.crl/ca-bundle-client.crl -

    -

    SSLCARevocationPath Directive

    Description: - Directory of PEM-encoded CA CRLs for -Client Auth
    Syntax: - SSLCARevocationPath directory-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLCARevocationPath Directive

    Description: + Directory of PEM-encoded CA CRLs for +Client Auth
    Syntax: + SSLCARevocationPath directory-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the directory where you keep the Certificate Revocation Lists (CRL) of Certification Authorities (CAs) whose clients you deal with. @@ -165,16 +159,16 @@ hash filenames. So usually you have not only to place the CRL files there. Additionally you have to create symbolic links named hash-value.rN. And you should always make sure this directory contains the appropriate symbolic links. Use the Makefile which -comes with mod_ssl to accomplish this task.

    -

    Example

    +comes with mod_ssl to accomplish this task.

    +

    Example

    SSLCARevocationPath /usr/local/apache/conf/ssl.crl/ -

    -

    SSLCertificateChainFile Directive

    Description: - File of PEM-encoded Server CA Certificates
    Syntax: - SSLCertificateChainFile file-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLCertificateChainFile Directive

    Description: + File of PEM-encoded Server CA Certificates
    Syntax: + SSLCertificateChainFile file-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the optional all-in-one file where you can assemble the certificates of Certification Authorities (CA) which form the @@ -183,12 +177,12 @@ certificate of of the server certificate and can range up to the root CA certificate. Such a file is simply the concatenation of the various PEM-encoded CA Certificate files, usually in certificate chain order.

    -This should be used alternatively and/or additionally to SSLCACertificatePath for explicitly +This should be used alternatively and/or additionally to SSLCACertificatePath for explicitly constructing the server certificate chain which is sent to the browser in addition to the server certificate. It is especially useful to avoid conflicts with CA certificates when using client authentication. Because although placing a CA certificate of the -server certificate chain into SSLCACertificatePath has the same effect +server certificate chain into SSLCACertificatePath has the same effect for the certificate chain construction, it has the side-effect that client certificates issued by this same CA certificate are also accepted on client authentication. That's usually not one expect.

    @@ -198,15 +192,15 @@ But be careful: Providing the certificate chain works only if you are using a using a coupled RSA+DSA certificate pair, this will work only if actually both certificates use the same certificate chain. Else the browsers will be confused in this situation.

    -

    Example

    +

    Example

    SSLCertificateChainFile /usr/local/apache/conf/ssl.crt/ca.crt -

    -

    SSLCertificateFile Directive

    Description: - Server PEM-encoded X.509 Certificate file
    Syntax: - SSLCertificateFile file-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLCertificateFile Directive

    Description: + Server PEM-encoded X.509 Certificate file
    Syntax: + SSLCertificateFile file-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive points to the PEM-encoded Certificate file for the server and optionally also to the corresponding RSA or DSA Private Key file for it @@ -214,15 +208,15 @@ optionally also to the corresponding RSA or DSA Private Key file for it Pass Phrase dialog is forced at startup time. This directive can be used up to two times (referencing different filenames) when both a RSA and a DSA based server certificate is used in parallel.

    -

    Example

    +

    Example

    SSLCertificateFile /usr/local/apache/conf/ssl.crt/server.crt -

    -

    SSLCertificateKeyFile Directive

    Description: - Server PEM-encoded Private Key file
    Syntax: - SSLCertificateKeyFile file-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLCertificateKeyFile Directive

    Description: + Server PEM-encoded Private Key file
    Syntax: + SSLCertificateKeyFile file-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive points to the PEM-encoded Private Key file for the server. If the Private Key is not combined with the Certificate in the @@ -236,18 +230,18 @@ contained Private Key is encrypted, the Pass Phrase dialog is forced at startup time. This directive can be used up to two times (referencing different filenames) when both a RSA and a DSA based private key is used in parallel.

    -

    Example

    +

    Example

    SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server.key -

    -

    SSLCipherSuite Directive

    Description: - Cipher Suite available for negotiation in SSL -handshake
    Syntax: - SSLCipherSuite cipher-spec
    Default: - SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
    Context: - server config, virtual host, directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLCipherSuite Directive

    Description: + Cipher Suite available for negotiation in SSL +handshake
    Syntax: + SSLCipherSuite cipher-spec
    Default: + SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
    Context: + server config, virtual host, directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_ssl

    This complex directive uses a colon-separated cipher-spec string consisting of OpenSSL cipher specifications to configure the Cipher Suite the @@ -261,16 +255,16 @@ response is sent.

    An SSL cipher specification in cipher-spec is composed of 4 major attributes plus a few extra minor ones:

      -
    • Key Exchange Algorithm:
      +
    • Key Exchange Algorithm:
      RSA or Diffie-Hellman variants.
      • -
    • Authentication Algorithm:
      +
    • Authentication Algorithm:
      RSA, Diffie-Hellman, DSS or none.
      • -
    • Cipher/Encryption Algorithm:
      +
    • Cipher/Encryption Algorithm:
      DES, Triple-DES, RC4, RC2, IDEA or none.
      • -
    • MAC Digest Algorithm:
      +
    • MAC Digest Algorithm:
      MD5, SHA or SHA1.
    @@ -280,13 +274,8 @@ one can either specify all the Ciphers, one at a time, or use aliases to specify the preference and order for the ciphers (see Table 1).

    - - -
    - - -
    - - +
    Tag Description
    + @@ -325,9 +314,6 @@ specify the preference and order for the ciphers (see Table
    Tag Description
    Key Exchange Algorithm:
    kRSA RSA key exchange
    kDHr Diffie-Hellman key exchange with RSA key
    DSS all ciphers using DSS authentication
    NULL all ciphers using no encryption
    -
    -

    Now where this becomes interesting is that these can be put together to specify the order and ciphers you wish to use. To speed this up @@ -350,8 +336,7 @@ authenticate, i.e. for SSL only the Anonymous Diffie-Hellman ciphers. Next, use ciphers using RC4 and RSA. Next include the high, medium and then the low security ciphers. Finally pull all SSLv2 and export ciphers to the end of the list.

    -
    -
    +
     $ openssl ciphers -v 'ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP'
 NULL-SHA                SSLv3 Kx=RSA      Au=RSA  Enc=None      Mac=SHA1
 NULL-MD5                SSLv3 Kx=RSA      Au=RSA  Enc=None      Mac=MD5
@@ -360,80 +345,71 @@ EDH-RSA-DES-CBC3-SHA    SSLv3 Kx=DH       Au=RSA  Enc=3DES(168) Mac=SHA1
 EXP-RC4-MD5             SSLv3 Kx=RSA(512) Au=RSA  Enc=RC4(40)   Mac=MD5  export
 EXP-RC2-CBC-MD5         SSLv2 Kx=RSA(512) Au=RSA  Enc=RC2(40)   Mac=MD5  export
 EXP-RC4-MD5             SSLv2 Kx=RSA(512) Au=RSA  Enc=RC4(40)   Mac=MD5  export
-
    
-
    +

    The complete list of particular RSA & DH ciphers for SSL is given in Table 2.

    -

    Example

    +

    Example

    SSLCipherSuite RSA:!EXP:!NULL:+HIGH:+MEDIUM:-LOW -

    - - -
    - - -
    - - +

    +
    Cipher-Tag Protocol Key Ex. Auth. Enc. MAC Type
    + - - - - - - - - - - - + + + + + + + + + + + - - + + - - - - - - - + + + + + + +
    Cipher-Tag Protocol Key Ex. Auth. Enc. MAC Type
    RSA Ciphers:
    DES-CBC3-SHA SSLv3 RSA RSA 3DES(168) SHA1  
    DES-CBC3-MD5 SSLv2 RSA RSA 3DES(168) MD5  
    IDEA-CBC-SHA SSLv3 RSA RSA IDEA(128) SHA1  
    RC4-SHA SSLv3 RSA RSA RC4(128) SHA1  
    RC4-MD5 SSLv3 RSA RSA RC4(128) MD5  
    IDEA-CBC-MD5 SSLv2 RSA RSA IDEA(128) MD5  
    RC2-CBC-MD5 SSLv2 RSA RSA RC2(128) MD5  
    RC4-MD5 SSLv2 RSA RSA RC4(128) MD5  
    DES-CBC-SHA SSLv3 RSA RSA DES(56) SHA1  
    RC4-64-MD5 SSLv2 RSA RSA RC4(64) MD5  
    DES-CBC-MD5 SSLv2 RSA RSA DES(56) MD5  
    DES-CBC3-SHA SSLv3 RSA RSA 3DES(168) SHA1
    DES-CBC3-MD5 SSLv2 RSA RSA 3DES(168) MD5
    IDEA-CBC-SHA SSLv3 RSA RSA IDEA(128) SHA1
    RC4-SHA SSLv3 RSA RSA RC4(128) SHA1
    RC4-MD5 SSLv3 RSA RSA RC4(128) MD5
    IDEA-CBC-MD5 SSLv2 RSA RSA IDEA(128) MD5
    RC2-CBC-MD5 SSLv2 RSA RSA RC2(128) MD5
    RC4-MD5 SSLv2 RSA RSA RC4(128) MD5
    DES-CBC-SHA SSLv3 RSA RSA DES(56) SHA1
    RC4-64-MD5 SSLv2 RSA RSA RC4(64) MD5
    DES-CBC-MD5 SSLv2 RSA RSA DES(56) MD5
    EXP-DES-CBC-SHA SSLv3 RSA(512) RSA DES(40) SHA1 export
    EXP-RC2-CBC-MD5 SSLv3 RSA(512) RSA RC2(40) MD5 export
    EXP-RC4-MD5 SSLv3 RSA(512) RSA RC4(40) MD5 export
    EXP-RC2-CBC-MD5 SSLv2 RSA(512) RSA RC2(40) MD5 export
    EXP-RC4-MD5 SSLv2 RSA(512) RSA RC4(40) MD5 export
    NULL-SHA SSLv3 RSA RSA None SHA1  
    NULL-MD5 SSLv3 RSA RSA None MD5  
    NULL-SHA SSLv3 RSA RSA None SHA1
    NULL-MD5 SSLv3 RSA RSA None MD5
    Diffie-Hellman Ciphers:
    ADH-DES-CBC3-SHA SSLv3 DH None 3DES(168) SHA1  
    ADH-DES-CBC-SHA SSLv3 DH None DES(56) SHA1  
    ADH-RC4-MD5 SSLv3 DH None RC4(128) MD5  
    EDH-RSA-DES-CBC3-SHA SSLv3 DH RSA 3DES(168) SHA1  
    EDH-DSS-DES-CBC3-SHA SSLv3 DH DSS 3DES(168) SHA1  
    EDH-RSA-DES-CBC-SHA SSLv3 DH RSA DES(56) SHA1  
    EDH-DSS-DES-CBC-SHA SSLv3 DH DSS DES(56) SHA1  
    ADH-DES-CBC3-SHA SSLv3 DH None 3DES(168) SHA1
    ADH-DES-CBC-SHA SSLv3 DH None DES(56) SHA1
    ADH-RC4-MD5 SSLv3 DH None RC4(128) MD5
    EDH-RSA-DES-CBC3-SHA SSLv3 DH RSA 3DES(168) SHA1
    EDH-DSS-DES-CBC3-SHA SSLv3 DH DSS 3DES(168) SHA1
    EDH-RSA-DES-CBC-SHA SSLv3 DH RSA DES(56) SHA1
    EDH-DSS-DES-CBC-SHA SSLv3 DH DSS DES(56) SHA1
    EXP-EDH-RSA-DES-CBC-SHA SSLv3 DH(512) RSA DES(40) SHA1 export
    EXP-EDH-DSS-DES-CBC-SHA SSLv3 DH(512) DSS DES(40) SHA1 export
    EXP-ADH-DES-CBC-SHA SSLv3 DH(512) None DES(40) SHA1 export
    EXP-ADH-RC4-MD5 SSLv3 DH(512) None RC4(40) MD5 export
    -
    -
    -

    SSLEngine Directive

    Description: - SSL Engine Operation Switch
    Syntax: - SSLEngine on|off
    Default: - SSLEngine off
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +
    top

    SSLEngine Directive

    Description: + SSL Engine Operation Switch
    Syntax: + SSLEngine on|off
    Default: + SSLEngine off
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive toggles the usage of the SSL/TLS Protocol Engine. This -is usually used inside a <VirtualHost> section to enable SSL/TLS for a +is usually used inside a <VirtualHost> section to enable SSL/TLS for a particular virtual host. By default the SSL/TLS Protocol Engine is disabled for both the main server and all configured virtual hosts.

    -

    Example

    -<VirtualHost _default_:443>
    -SSLEngine on
    -...
    +

    Example

    +<VirtualHost _default_:443>
    +SSLEngine on
    +...
    </VirtualHost> -

    -

    SSLMutex Directive

    Description: - Semaphore for internal mutual exclusion of -operations
    Syntax: - SSLMutex type
    Default: - SSLMutex none
    Context: - server config
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLMutex Directive

    Description: + Semaphore for internal mutual exclusion of +operations
    Syntax: + SSLMutex type
    Default: + SSLMutex none
    Context: + server config
    Status: + Extension
    Module: + mod_ssl

    This configures the SSL engine's semaphore (aka. lock) which is used for mutual exclusion of operations which have to be done in a synchronized way between the @@ -467,16 +443,16 @@ The following Mutex types are available:

    when possible. It is only available when the underlying platform supports it.

    -

    Example

    +

    Example

    SSLMutex file:/usr/local/apache/logs/ssl_mutex -

    -

    SSLOptions Directive

    Description: - Configure various SSL engine run-time options
    Syntax: - SSLOptions [+|-]option ...
    Context: - server config, virtual host, directory, .htaccess
    Override: - Options
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLOptions Directive

    Description: + Configure various SSL engine run-time options
    Syntax: + SSLOptions [+|-]option ...
    Context: + server config, virtual host, directory, .htaccess
    Override: + Options
    Status: + Extension
    Module: + mod_ssl

    This directive can be used to control various run-time options on a per-directory basis. Normally, if multiple SSLOptions @@ -558,24 +534,24 @@ The available options are:

    per-directory basis only, please.

    -

    Example

    -SSLOptions +FakeBasicAuth -StrictRequire
    -<Files ~ "\.(cgi|shtml)$">
    - SSLOptions +StdEnvVars +CompatEnvVars -ExportCertData
    +

    Example

    +SSLOptions +FakeBasicAuth -StrictRequire
    +<Files ~ "\.(cgi|shtml)$">
    + SSLOptions +StdEnvVars +CompatEnvVars -ExportCertData
    <Files> -

    -

    SSLPassPhraseDialog Directive

    Description: - Type of pass phrase dialog for encrypted private -keys
    Syntax: - SSLPassPhraseDialog type
    Default: - SSLPassPhraseDialog builtin
    Context: - server config
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLPassPhraseDialog Directive

    Description: + Type of pass phrase dialog for encrypted private +keys
    Syntax: + SSLPassPhraseDialog type
    Default: + SSLPassPhraseDialog builtin
    Context: + server config
    Status: + Extension
    Module: + mod_ssl

    When Apache starts up it has to read the various Certificate (see -SSLCertificateFile) and -Private Key (see SSLCertificateKeyFile) files of the +SSLCertificateFile) and +Private Key (see SSLCertificateKeyFile) files of the SSL-enabled virtual servers. Because for security reasons the Private Key files are usually encrypted, mod_ssl needs to query the administrator for a Pass Phrase in order to decrypt those files. This @@ -625,17 +601,17 @@ query can be done in two ways which can be configured by

    Example:

    -
    +

    SSLPassPhraseDialog exec:/usr/local/apache/sbin/pp-filter -

    -

    SSLProtocol Directive

    Description: - Configure usable SSL protocol flavors
    Syntax: - SSLProtocol [+|-]protocol ...
    Default: - SSLProtocol all
    Context: - server config, virtual host
    Override: - Options
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProtocol Directive

    Description: + Configure usable SSL protocol flavors
    Syntax: + SSLProtocol [+|-]protocol ...
    Default: + SSLProtocol all
    Context: + server config, virtual host
    Override: + Options
    Status: + Extension
    Module: + mod_ssl

    This directive can be used to control the SSL protocol flavors mod_ssl should use when establishing its server environment. Clients then can only connect @@ -669,34 +645,34 @@ The available (case-insensitive) protocols are:

    combination with the minus sign on a protocol as the example above shows.

    -

    Example

    -# enable SSLv3 and TLSv1, but not SSLv2
    +

    Example

    +# enable SSLv3 and TLSv1, but not SSLv2
    SSLProtocol all -SSLv2 -

    -

    SSLProxyCACertificateFile Directive

    Description: - File of concatenated PEM-encoded CA Certificates -for Remote Server Auth
    Syntax: - SSLProxyCACertificateFile file-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProxyCACertificateFile Directive

    Description: + File of concatenated PEM-encoded CA Certificates +for Remote Server Auth
    Syntax: + SSLProxyCACertificateFile file-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the all-in-one file where you can assemble the Certificates of Certification Authorities (CA) whose remote servers you deal with. These are used for Remote Server Authentication. Such a file is simply the concatenation of the various PEM-encoded Certificate files, in order of preference. This can be used alternatively and/or additionally to -SSLProxyCACertificatePath.

    -

    Example

    +SSLProxyCACertificatePath.

    +

    Example

    SSLProxyCACertificateFile /usr/local/apache/conf/ssl.crt/ca-bundle-remote-server.crt -

    -

    SSLProxyCACertificatePath Directive

    Description: - Directory of PEM-encoded CA Certificates for -Remote Server Auth
    Syntax: - SSLProxyCACertificatePath directory-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProxyCACertificatePath Directive

    Description: + Directory of PEM-encoded CA Certificates for +Remote Server Auth
    Syntax: + SSLProxyCACertificatePath directory-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the directory where you keep the Certificates of Certification Authorities (CAs) whose remote servers you deal with. These are used to @@ -708,33 +684,33 @@ there: you also have to create symbolic links named hash-value.N. And you should always make sure this directory contains the appropriate symbolic links. Use the Makefile which comes with mod_ssl to accomplish this task.

    -

    Example

    +

    Example

    SSLProxyCACertificatePath /usr/local/apache/conf/ssl.crt/ -

    -

    SSLProxyCARevocationFile Directive

    Description: - File of concatenated PEM-encoded CA CRLs for -Remote Server Auth
    Syntax: - SSLProxyCARevocationFile file-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProxyCARevocationFile Directive

    Description: + File of concatenated PEM-encoded CA CRLs for +Remote Server Auth
    Syntax: + SSLProxyCARevocationFile file-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the all-in-one file where you can assemble the Certificate Revocation Lists (CRL) of Certification Authorities (CA) whose remote servers you deal with. These are used for Remote Server Authentication. Such a file is simply the concatenation of the various PEM-encoded CRL files, in order of preference. This can be -used alternatively and/or additionally to SSLProxyCARevocationPath.

    -

    Example

    +used alternatively and/or additionally to SSLProxyCARevocationPath.

    +

    Example

    SSLProxyCARevocationFile /usr/local/apache/conf/ssl.crl/ca-bundle-remote-server.crl -

    -

    SSLProxyCARevocationPath Directive

    Description: - Directory of PEM-encoded CA CRLs for -Remote Server Auth
    Syntax: - SSLProxyCARevocationPath directory-path
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProxyCARevocationPath Directive

    Description: + Directory of PEM-encoded CA CRLs for +Remote Server Auth
    Syntax: + SSLProxyCARevocationPath directory-path
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the directory where you keep the Certificate Revocation Lists (CRL) of Certification Authorities (CAs) whose remote servers you deal with. @@ -745,48 +721,48 @@ hash filenames. So usually you have not only to place the CRL files there. Additionally you have to create symbolic links named hash-value.rN. And you should always make sure this directory contains the appropriate symbolic links. Use the Makefile which -comes with mod_ssl to accomplish this task.

    -

    Example

    +comes with mod_ssl to accomplish this task.

    +

    Example

    SSLProxyCARevocationPath /usr/local/apache/conf/ssl.crl/ -

    -

    SSLProxyCipherSuite Directive

    Description: - Cipher Suite available for negotiation in SSL -proxy handshake
    Syntax: - SSLProxyCipherSuite cipher-spec
    Default: - SSLProxyCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
    Context: - server config, virtual host, directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProxyCipherSuite Directive

    Description: + Cipher Suite available for negotiation in SSL +proxy handshake
    Syntax: + SSLProxyCipherSuite cipher-spec
    Default: + SSLProxyCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
    Context: + server config, virtual host, directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_ssl

    Equivalent to SSLCipherSuite, but for the proxy connection. -Please refer to SSLCipherSuite +Please refer to SSLCipherSuite for additional information.

    -

    SSLProxyEngine Directive

    Description: - SSL Proxy Engine Operation Switch
    Syntax: - SSLProxyEngine on|off
    Default: - SSLProxyEngine off
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +
    top

    SSLProxyEngine Directive

    Description: + SSL Proxy Engine Operation Switch
    Syntax: + SSLProxyEngine on|off
    Default: + SSLProxyEngine off
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive toggles the usage of the SSL/TLS Protocol Engine for proxy. This -is usually used inside a <VirtualHost> section to enable SSL/TLS for proxy +is usually used inside a <VirtualHost> section to enable SSL/TLS for proxy usage in a particular virtual host. By default the SSL/TLS Protocol Engine is disabled for proxy image both for the main server and all configured virtual hosts.

    -

    Example

    -<VirtualHost _default_:443>
    -SSLProxyEngine on
    -...
    +

    Example

    +<VirtualHost _default_:443>
    +SSLProxyEngine on
    +...
    </VirtualHost> -

    -

    SSLProxyMachineCertificateFile Directive

    Description: - File of concatenated PEM-encoded CA certificates for proxy server client certificates
    Syntax: - SSLProxyMachineCertificateFile filename
    Default: - None
    Context: - server config
    Override: - Not applicable
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProxyMachineCertificateFile Directive

    Description: + File of concatenated PEM-encoded CA certificates for proxy server client certificates
    Syntax: + SSLProxyMachineCertificateFile filename
    Default: + None
    Context: + server config
    Override: + Not applicable
    Status: + Extension
    Module: + mod_ssl

    This directive sets the all-in-one file where you keep the certificates of Certification Authorities (CAs) whose proxy client certificates are used for @@ -799,17 +775,17 @@ or additionally to SSLProxyMachineCertificatePath.

    Example:

    -
    +

    SSLProxyMachineCertificatePath /usr/local/apache/conf/ssl.crt/ -

    -

    SSLProxyMachineCertificatePath Directive

    Description: - Directory of PEM-encoded CA certificates for proxy server client certificates
    Syntax: - SSLProxyMachineCertificatePath directory
    Default: - None
    Context: - server config
    Override: - Not applicable
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProxyMachineCertificatePath Directive

    Description: + Directory of PEM-encoded CA certificates for proxy server client certificates
    Syntax: + SSLProxyMachineCertificatePath directory
    Default: + None
    Context: + server config
    Override: + Not applicable
    Status: + Extension
    Module: + mod_ssl

    This directive sets the directory where you keep the certificates of Certification Authorities (CAs) whose proxy client certificates are used for @@ -823,33 +799,33 @@ comes with mod_ssl to accomplish this task.

    Example:

    -
    +

    SSLProxyMachineCertificatePath /usr/local/apache/conf/ssl.crt/ -

    -

    SSLProxyProtocol Directive

    Description: - Configure usable SSL protocol flavors for proxy usage
    Syntax: - SSLProxyProtocol [+|-]protocol ...
    Default: - SSLProxyProtocol all
    Context: - server config, virtual host
    Override: - Options
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProxyProtocol Directive

    Description: + Configure usable SSL protocol flavors for proxy usage
    Syntax: + SSLProxyProtocol [+|-]protocol ...
    Default: + SSLProxyProtocol all
    Context: + server config, virtual host
    Override: + Options
    Status: + Extension
    Module: + mod_ssl

    This directive can be used to control the SSL protocol flavors mod_ssl should use when establishing its server environment for proxy . It will only connect to servers using one of the provided protocols.

    -

    Please refer to SSLProtocol +

    Please refer to SSLProtocol for additional information.

    -

    SSLProxyVerify Directive

    Description: - Type of remote server Certificate verification
    Syntax: - SSLProxyVerify level
    Default: - SSLProxyVerify none
    Context: - server config, virtual host, directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_ssl
    +
    top

    SSLProxyVerify Directive

    Description: + Type of remote server Certificate verification
    Syntax: + SSLProxyVerify level
    Default: + SSLProxyVerify none
    Context: + server config, virtual host, directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_ssl

    This directive sets the Certificate verification level for the remote server Authentication. Notice that this directive can be used both in per-server and @@ -868,7 +844,7 @@ The following levels are available for level:

  • require: the remote server has to present a valid Certificate
  • optional_no_ca: - the remote server may present a valid Certificate
    + the remote server may present a valid Certificate
    but it need not to be (successfully) verifiable.

    • In practice only levels none and @@ -876,18 +852,18 @@ The following levels are available for level:

    optional doesn't work with all servers and level optional_no_ca is actually against the idea of authentication (but can be used to establish SSL test pages, etc.)

    -

    Example

    +

    Example

    SSLProxyVerify require -

    -

    SSLProxyVerifyDepth Directive

    Description: - Maximum depth of CA Certificates in Remote Server -Certificate verification
    Syntax: - SSLVerifyDepth number
    Default: - SSLVerifyDepth 1
    Context: - server config, virtual host, directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLProxyVerifyDepth Directive

    Description: + Maximum depth of CA Certificates in Remote Server +Certificate verification
    Syntax: + SSLVerifyDepth number
    Default: + SSLVerifyDepth 1
    Context: + server config, virtual host, directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_ssl

    This directive sets how deeply mod_ssl should verify before deciding that the remote server does not have a valid certificate. Notice that this directive can be @@ -903,18 +879,18 @@ verifying the remote server certificate. A depth of 0 means that self-signed remote server certificates are accepted only, the default depth of 1 means the remote server certificate can be self-signed or has to be signed by a CA which is directly known to the server (i.e. the CA's certificate is under -SSLProxyCACertificatePath), etc.

    -

    Example

    +SSLProxyCACertificatePath), etc.

    +

    Example

    SSLProxyVerifyDepth 10 -

    -

    SSLRandomSeed Directive

    Description: - Pseudo Random Number Generator (PRNG) seeding -source
    Syntax: - SSLRandomSeed context source -[bytes]
    Context: - server config
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLRandomSeed Directive

    Description: + Pseudo Random Number Generator (PRNG) seeding +source
    Syntax: + SSLRandomSeed context source +[bytes]
    Context: + server config
    Status: + Extension
    Module: + mod_ssl

    This configures one or more sources for seeding the Pseudo Random Number Generator (PRNG) in OpenSSL at startup time (context is @@ -988,23 +964,23 @@ The following source variants are available:

    /crypto/) to seed the PRNG. Use this if no random device exists on your platform.

    -

    Example

    -SSLRandomSeed startup builtin
    -SSLRandomSeed startup file:/dev/random
    -SSLRandomSeed startup file:/dev/urandom 1024
    -SSLRandomSeed startup exec:/usr/local/bin/truerand 16
    -SSLRandomSeed connect builtin
    -SSLRandomSeed connect file:/dev/random
    -SSLRandomSeed connect file:/dev/urandom 1024
    -
    -

    SSLRequire Directive

    Description: - Allow access only when an arbitrarily complex -boolean expression is true
    Syntax: - SSLRequire expression
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_ssl
    +

    Example

    +SSLRandomSeed startup builtin
    +SSLRandomSeed startup file:/dev/random
    +SSLRandomSeed startup file:/dev/urandom 1024
    +SSLRandomSeed startup exec:/usr/local/bin/truerand 16
    +SSLRandomSeed connect builtin
    +SSLRandomSeed connect file:/dev/random
    +SSLRandomSeed connect file:/dev/urandom 1024
    +

    +
    top

    SSLRequire Directive

    Description: + Allow access only when an arbitrarily complex +boolean expression is true
    Syntax: + SSLRequire expression
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_ssl

    This directive specifies a general access requirement which has to be fulfilled in order to allow access. It's a very powerful directive because the @@ -1062,20 +1038,15 @@ Per-Server Class context expression is parsed at startup time and at runtime only the machine representation is executed. For Per-Directory context this is different: here expression has to be parsed and immediately executed for every request.

    -

    Example

    -SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)-/ \
    - and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
    - and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
    - and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
    - and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
    +

    Example

    +SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)-/ \
    + and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
    + and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
    + and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
    + and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
    or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ -

    - - -
    - -
    - -
    +

    +
    Standard CGI/1.0 and Apache variables: 
     HTTP_USER_AGENT        PATH_INFO             AUTH_TYPE
@@ -1133,34 +1104,31 @@ SSL_VERSION_INTERFACE  SSL_CLIENT_S_DN_OU     SSL_SERVER_S_DN_OU
                        SSL_CLIENT_VERIFY
    -
    -
    -

    SSLRequireSSL Directive

    Description: - Deny access when SSL is not used for the -HTTP request
    Syntax: - SSLRequireSSL
    Context: - directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_ssl
    +
    top

    SSLRequireSSL Directive

    Description: + Deny access when SSL is not used for the +HTTP request
    Syntax: + SSLRequireSSL
    Context: + directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_ssl

    This directive forbids access unless HTTP over SSL (i.e. HTTPS) is enabled for the current connection. This is very handy inside the SSL-enabled virtual host or directories for defending against configuration errors that expose stuff that should be protected. When this directive is present all requests are denied which are not using SSL.

    -

    Example

    +

    Example

    SSLRequireSSL -

    -

    SSLSessionCache Directive

    Description: - Type of the global/inter-process SSL Session -Cache
    Syntax: - SSLSessionCache type
    Default: - SSLSessionCache none
    Context: - server config
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLSessionCache Directive

    Description: + Type of the global/inter-process SSL Session +Cache
    Syntax: + SSLSessionCache type
    Default: + SSLSessionCache none
    Context: + server config
    Status: + Extension
    Module: + mod_ssl

    This configures the storage type of the global/inter-process SSL Session Cache. This cache is an optional facility which speeds up parallel request @@ -1193,34 +1161,34 @@ The following two storage types are currently supported:

    platforms. See the mod_ssl INSTALL document for details on how to build Apache+EAPI with shared memory support.

    -

    Examples

    -SSLSessionCache dbm:/usr/local/apache/logs/ssl_gcache_data
    +

    Examples

    +SSLSessionCache dbm:/usr/local/apache/logs/ssl_gcache_data
    SSLSessionCache shm:/usr/local/apache/logs/ssl_gcache_data(512000) -

    -

    SSLSessionCacheTimeout Directive

    Description: - Number of seconds before an SSL session expires -in the Session Cache
    Syntax: - SSLSessionCacheTimeout seconds
    Default: - SSLSessionCacheTimeout 300
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLSessionCacheTimeout Directive

    Description: + Number of seconds before an SSL session expires +in the Session Cache
    Syntax: + SSLSessionCacheTimeout seconds
    Default: + SSLSessionCacheTimeout 300
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_ssl

    This directive sets the timeout in seconds for the information stored in the global/inter-process SSL Session Cache and the OpenSSL internal memory cache. It can be set as low as 15 for testing, but should be set to higher values like 300 in real life.

    -

    Example

    +

    Example

    SSLSessionCacheTimeout 600 -

    -

    SSLVerifyClient Directive

    Description: - Type of Client Certificate verification
    Syntax: - SSLVerifyClient level
    Default: - SSLVerifyClient none
    Context: - server config, virtual host, directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLVerifyClient Directive

    Description: + Type of Client Certificate verification
    Syntax: + SSLVerifyClient level
    Default: + SSLVerifyClient none
    Context: + server config, virtual host, directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_ssl

    This directive sets the Certificate verification level for the Client Authentication. Notice that this directive can be used both in per-server and @@ -1239,7 +1207,7 @@ The following levels are available for level:

  • require: the client has to present a valid Certificate
  • optional_no_ca: - the client may present a valid Certificate
    + the client may present a valid Certificate
    but it need not to be (successfully) verifiable.

    • In practice only levels none and @@ -1247,18 +1215,18 @@ The following levels are available for level:

    optional doesn't work with all browsers and level optional_no_ca is actually against the idea of authentication (but can be used to establish SSL test pages, etc.)

    -

    Example

    +

    Example

    SSLVerifyClient require -

    -

    SSLVerifyDepth Directive

    Description: - Maximum depth of CA Certificates in Client -Certificate verification
    Syntax: - SSLVerifyDepth number
    Default: - SSLVerifyDepth 1
    Context: - server config, virtual host, directory, .htaccess
    Override: - AuthConfig
    Status: - Extension
    Module: - mod_ssl
    +

    +
    top

    SSLVerifyDepth Directive

    Description: + Maximum depth of CA Certificates in Client +Certificate verification
    Syntax: + SSLVerifyDepth number
    Default: + SSLVerifyDepth 1
    Context: + server config, virtual host, directory, .htaccess
    Override: + AuthConfig
    Status: + Extension
    Module: + mod_ssl

    This directive sets how deeply mod_ssl should verify before deciding that the clients don't have a valid certificate. Notice that this directive can be @@ -1274,8 +1242,8 @@ verifying the client certificate. A depth of 0 means that self-signed client certificates are accepted only, the default depth of 1 means the client certificate can be self-signed or has to be signed by a CA which is directly known to the server (i.e. the CA's certificate is under -SSLCACertificatePath), etc.

    -

    Example

    +SSLCACertificatePath), etc.

    +

    Example

    SSLVerifyDepth 10 -

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    + \ No newline at end of file diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml index cc30672fac..9dd00c0d39 100644 --- a/docs/manual/mod/mod_ssl.xml +++ b/docs/manual/mod/mod_ssl.xml @@ -31,16 +31,11 @@ be made available under different names, too. Look in the Compatibility chapter for details on the compatibility variables.

    - - -
    - - -
    - +
    - - - + + + @@ -75,12 +70,9 @@ compatibility variables.

    +
    Variable Name:Value Type:Description:Variable Name:Value Type:Description:
    HTTPS flag HTTPS is being used.
    SSL_PROTOCOL string The SSL protocol version (SSLv2, SSLv3, TLSv1)
    SSL_SERVER_A_SIG string Algorithm used for the signature of server's certificate
    SSL_SERVER_A_KEY string Algorithm used for the public key of server's certificate
    SSL_SERVER_CERT string PEM-encoded server certificate
    [ where x509 is a component of a X.509 DN: + C,ST,L,O,OU,CN,T,I,G,S,D,UID,Email ]
    -[ where x509 is a component of a X.509 DN: - C,ST,L,O,OU,CN,T,I,G,S,D,UID,Email ] -
    -
    Custom Log Formats @@ -506,13 +498,8 @@ one can either specify all the Ciphers, one at a time, or use aliases to specify the preference and order for the ciphers (see Table 1).

    - - -
    - - -
    - - +
    Tag Description
    + @@ -551,9 +538,6 @@ specify the preference and order for the ciphers (see Table
    Tag Description
    Key Exchange Algorithm:
    kRSA RSA key exchange
    kDHr Diffie-Hellman key exchange with RSA key
    DSS all ciphers using DSS authentication
    NULL all ciphers using no encryption
    -
    -

    Now where this becomes interesting is that these can be put together to specify the order and ciphers you wish to use. To speed this up @@ -593,48 +577,40 @@ href="#table2">Table 2.

    Example SSLCipherSuite RSA:!EXP:!NULL:+HIGH:+MEDIUM:-LOW - - -
    - - -
    - - +
    Cipher-Tag Protocol Key Ex. Auth. Enc. MAC Type
    + - - - - - - - - - - - + + + + + + + + + + + - - + + - - - - - - - + + + + + + +
    Cipher-Tag Protocol Key Ex. Auth. Enc. MAC Type
    RSA Ciphers:
    DES-CBC3-SHA SSLv3 RSA RSA 3DES(168) SHA1  
    DES-CBC3-MD5 SSLv2 RSA RSA 3DES(168) MD5  
    IDEA-CBC-SHA SSLv3 RSA RSA IDEA(128) SHA1  
    RC4-SHA SSLv3 RSA RSA RC4(128) SHA1  
    RC4-MD5 SSLv3 RSA RSA RC4(128) MD5  
    IDEA-CBC-MD5 SSLv2 RSA RSA IDEA(128) MD5  
    RC2-CBC-MD5 SSLv2 RSA RSA RC2(128) MD5  
    RC4-MD5 SSLv2 RSA RSA RC4(128) MD5  
    DES-CBC-SHA SSLv3 RSA RSA DES(56) SHA1  
    RC4-64-MD5 SSLv2 RSA RSA RC4(64) MD5  
    DES-CBC-MD5 SSLv2 RSA RSA DES(56) MD5  
    DES-CBC3-SHA SSLv3 RSA RSA 3DES(168) SHA1
    DES-CBC3-MD5 SSLv2 RSA RSA 3DES(168) MD5
    IDEA-CBC-SHA SSLv3 RSA RSA IDEA(128) SHA1
    RC4-SHA SSLv3 RSA RSA RC4(128) SHA1
    RC4-MD5 SSLv3 RSA RSA RC4(128) MD5
    IDEA-CBC-MD5 SSLv2 RSA RSA IDEA(128) MD5
    RC2-CBC-MD5 SSLv2 RSA RSA RC2(128) MD5
    RC4-MD5 SSLv2 RSA RSA RC4(128) MD5
    DES-CBC-SHA SSLv3 RSA RSA DES(56) SHA1
    RC4-64-MD5 SSLv2 RSA RSA RC4(64) MD5
    DES-CBC-MD5 SSLv2 RSA RSA DES(56) MD5
    EXP-DES-CBC-SHA SSLv3 RSA(512) RSA DES(40) SHA1 export
    EXP-RC2-CBC-MD5 SSLv3 RSA(512) RSA RC2(40) MD5 export
    EXP-RC4-MD5 SSLv3 RSA(512) RSA RC4(40) MD5 export
    EXP-RC2-CBC-MD5 SSLv2 RSA(512) RSA RC2(40) MD5 export
    EXP-RC4-MD5 SSLv2 RSA(512) RSA RC4(40) MD5 export
    NULL-SHA SSLv3 RSA RSA None SHA1  
    NULL-MD5 SSLv3 RSA RSA None MD5  
    NULL-SHA SSLv3 RSA RSA None SHA1
    NULL-MD5 SSLv3 RSA RSA None MD5
    Diffie-Hellman Ciphers:
    ADH-DES-CBC3-SHA SSLv3 DH None 3DES(168) SHA1  
    ADH-DES-CBC-SHA SSLv3 DH None DES(56) SHA1  
    ADH-RC4-MD5 SSLv3 DH None RC4(128) MD5  
    EDH-RSA-DES-CBC3-SHA SSLv3 DH RSA 3DES(168) SHA1  
    EDH-DSS-DES-CBC3-SHA SSLv3 DH DSS 3DES(168) SHA1  
    EDH-RSA-DES-CBC-SHA SSLv3 DH RSA DES(56) SHA1  
    EDH-DSS-DES-CBC-SHA SSLv3 DH DSS DES(56) SHA1  
    ADH-DES-CBC3-SHA SSLv3 DH None 3DES(168) SHA1
    ADH-DES-CBC-SHA SSLv3 DH None DES(56) SHA1
    ADH-RC4-MD5 SSLv3 DH None RC4(128) MD5
    EDH-RSA-DES-CBC3-SHA SSLv3 DH RSA 3DES(168) SHA1
    EDH-DSS-DES-CBC3-SHA SSLv3 DH DSS 3DES(168) SHA1
    EDH-RSA-DES-CBC-SHA SSLv3 DH RSA DES(56) SHA1
    EDH-DSS-DES-CBC-SHA SSLv3 DH DSS DES(56) SHA1
    EXP-EDH-RSA-DES-CBC-SHA SSLv3 DH(512) RSA DES(40) SHA1 export
    EXP-EDH-DSS-DES-CBC-SHA SSLv3 DH(512) DSS DES(40) SHA1 export
    EXP-ADH-DES-CBC-SHA SSLv3 DH(512) None DES(40) SHA1 export
    EXP-ADH-RC4-MD5 SSLv3 DH(512) None RC4(40) MD5 export
    -
    -
    @@ -1100,12 +1076,7 @@ SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)-/ \
    and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
    or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ - - -
    - -
    - -
    +
    Standard CGI/1.0 and Apache variables: 
     HTTP_USER_AGENT        PATH_INFO             AUTH_TYPE
@@ -1163,9 +1134,6 @@ SSL_VERSION_INTERFACE  SSL_CLIENT_S_DN_OU     SSL_SERVER_S_DN_OU
                        SSL_CLIENT_VERIFY
    -
    -
    diff --git a/docs/manual/mod/mod_status.html.en b/docs/manual/mod/mod_status.html.en index d2cae74935..d75a9c990e 100644 --- a/docs/manual/mod/mod_status.html.en +++ b/docs/manual/mod/mod_status.html.en @@ -1,19 +1,21 @@ -mod_status - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_status

    Description: - Provides information on server activity and -performance
    Status: - Base
    Module Identifier: - status_module

    Summary

    + -->mod_status - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_status

    Description: + Provides information on server activity and +performance
    Status: + Base
    Module Identifier: + status_module

    Summary

    -
    +
    Warning: This document has not been updated to take into account changes made in the 2.0 version of the Apache HTTP Server. Some of the information may still be relevant, but please use it with care. -
    +

    The Status module allows a server administrator to find out how well their server is performing. A HTML page is presented @@ -51,30 +53,30 @@ performance

    A compile-time option must be used to display the details marked "(*)" as the instrumentation required for obtaining these statistics does not exist within standard Apache.

    -

    Directives

    Enabling Status Support

    +

    Directives

    Topics

    • Enabling Status Support
    • Automatic Updates
    • Machine Readable Status File
    top

    Enabling Status Support

    To enable status reports only for browsers from the foo.com domain add this code to your httpd.conf configuration file

    -
    - <Location /server-status>
    - SetHandler server-status
    -
    - Order Deny,Allow
    - Deny from all
    - Allow from .foo.com
    +

    + <Location /server-status>
    + SetHandler server-status
    +
    + Order Deny,Allow
    + Deny from all
    + Allow from .foo.com
    </Location> -

    +

    You can now access server statistics by using a Web browser to access the page http://your.server.name/server-status

    -

    Note that mod_status will only work +

    Note that mod_status will only work when you are running Apache in standalone mode and not - inetd mode.

    -

    Automatic Updates

    + inetd mode.

    +
    top

    Automatic Updates

    You can get the status page to update itself automatically if @@ -82,7 +84,7 @@ performance

    http://your.server.name/server-status?refresh=N to refresh the page every N seconds.

    -

    Machine Readable Status File

    +
    top

    Machine Readable Status File

    A machine-readable version of the status file is available by @@ -92,26 +94,26 @@ performance

    /support directory of Apache, log_server_status.

    -
    - It should be noted that if mod_status is +
    + It should be noted that if mod_status is compiled into the server, its handler capability is available in all configuration files, including per-directory files (e.g., .htaccess). This may have security-related ramifications for your site. -
    + -

    ExtendedStatus Directive

    Description: - This directive controls whether the server keeps track of +
    top

    ExtendedStatus Directive

    Description: + This directive controls whether the server keeps track of extended status information for each request. This is only -useful if the status module is enabled on the server.
    Syntax: - ExtendedStatus On|Off
    Default: - ExtendedStatus Off
    Context: - server config
    Status: - Base
    Module: - mod_status
    Compatibility: - ExtendedStatus is only available in Apache 1.3.2 and -later.
    +useful if the status module is enabled on the server.
    Syntax: + ExtendedStatus On|Off
    Default: + ExtendedStatus Off
    Context: + server config
    Status: + Base
    Module: + mod_status
    Compatibility: + ExtendedStatus is only available in Apache 1.3.2 and +later.

    This setting applies to the entire server, and cannot be enabled or disabled on a virtualhost-by-virtualhost basis.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_suexec.html.en b/docs/manual/mod/mod_suexec.html.en index 032472009e..9f8afdb9ae 100644 --- a/docs/manual/mod/mod_suexec.html.en +++ b/docs/manual/mod/mod_suexec.html.en @@ -1,32 +1,34 @@ -mod_suexec - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_suexec

    Description: - Allows CGI scripts to run as a specified user -and Group
    Status: - Extension
    Module Identifier: - suexec_module
    Compatibility: - Available in Apache 2.0 and later

    Summary

    + -->mod_suexec - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_suexec

    Description: + Allows CGI scripts to run as a specified user +and Group
    Status: + Extension
    Module Identifier: + suexec_module
    Compatibility: + Available in Apache 2.0 and later

    Summary

    This module, in combination with the suexec support program allows CGI scripts to run as a specified user and Group.

    -

    Directives

    See also

    SuexecUserGroup Directive

    Description: - User and group permissions for CGI programs
    Syntax: - SuexecUserGroup User Group
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_suexec
    Compatibility: - SuexecUserGroup is only available in 2.0 and -later.
    +
    top

    SuexecUserGroup Directive

    Description: + User and group permissions for CGI programs
    Syntax: + SuexecUserGroup User Group
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_suexec
    Compatibility: + SuexecUserGroup is only available in 2.0 and +later.

    The SuexecUserGroup directive allows you to specify a user and group for CGI programs to run as. Non-CGI requests are still processes with the user specified in the User directive. This directive replaces the Apache 1.3 configuration of using the User and Group directives inside of VirtualHosts.

    -

    Example

    +

    Example

    SuexecUserGroup nobody nogroup -

    +

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_suexec.html.ja.jis b/docs/manual/mod/mod_suexec.html.ja.jis index ab877c2b13..98c36ac497 100644 --- a/docs/manual/mod/mod_suexec.html.ja.jis +++ b/docs/manual/mod/mod_suexec.html.ja.jis @@ -1,31 +1,33 @@ -mod_suexec - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mod_suexec

    $B@bL@(B: - $B;XDj$5$l$?%f!<%6$H%0%k!<%W$G(B CGI $B%9%/%j%W%H$r
    $B%9%F!<%?%9(B: - $B3HD%(B
    $B%b%8%e!<(B$B%k<1JL;R(B: - suexec_module
    $B8_49@-(B: - Apache 2.0 $B0J9_$G;HMQ2DG=(B

    $B35MW(B

    + -->mod_suexec - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mod_suexec

    $B@bL@(B: + $B;XDj$5$l$?%f!<%6$H%0%k!<%W$G(B CGI $B%9%/%j%W%H$r
    $B%9%F!<%?%9(B: + $B3HD%(B
    $B%b%8%e!<%k<1JL;R(B: + suexec_module
    $B8_49@-(B: + Apache 2.0 $B0J9_$G;HMQ2DG=(B

    $B35MW(B

    $B$3$N%b%8%e!<%k$H(B suexec $B%5%]!<%H%W%m%0%i%`(B $B$K$h$j!"(BCGI $B%9%/%j%W%H$,;XDj$5$l$?%f!<%6$H%0%k!<%W$G(B $B -

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    SuexecUserGroup $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - CGI $B%W%m%0%i%`$N%f!<%6%Q!<%_%C%7%g%s!"%0%k!<%W%Q!<%_%C%7%g%s(B
    $B9=J8(B: - SuexecUserGroup User Group
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: - $B3HD%(B
    $B%b%8%e!<%k(B: - mod_suexec
    $B8_49@-(B: - SuexecUserGroup $B$O(B 2.0 $B0J9_$G$N$_;HMQ2DG=!#(B
    +

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    top

    SuexecUserGroup $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + CGI $B%W%m%0%i%`$N%f!<%6%Q!<%_%C%7%g%s!"%0%k!<%W%Q!<%_%C%7%g%s(B
    $B9=J8(B: + SuexecUserGroup User Group
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: + $B3HD%(B
    $B%b%8%e!<%k(B: + mod_suexec
    $B8_49@-(B: + SuexecUserGroup $B$O(B 2.0 $B0J9_$G$N$_;HMQ2DG=!#(B

    SuexecUserGroup $B%G%#%l%/%F%#%V$O(B CGI $B%W%m%0%i%`(B - $B$, -

    $BNc(B

    +

    $BNc(B

    SuexecUserGroup nobody nogroup -

    +

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_unique_id.html.en b/docs/manual/mod/mod_unique_id.html.en index 492dd64ace..ce759df933 100644 --- a/docs/manual/mod/mod_unique_id.html.en +++ b/docs/manual/mod/mod_unique_id.html.en @@ -1,12 +1,14 @@ -mod_unique_id - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_unique_id

    Description: - Provides an environment variable with a unique -identifier for each request
    Status: - Extension
    Module Identifier: - unique_id_module

    Summary

    + -->mod_unique_id - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_unique_id

    Description: + Provides an environment variable with a unique +identifier for each request
    Status: + Extension
    Module Identifier: + unique_id_module

    Summary

    This module provides a magic token for each request which is guaranteed to be unique across "all" requests under very @@ -16,7 +18,7 @@ identifier for each request

    Directives

    This module provides no directives.

    Topics

    • Theory
    top

    Theory

    First a brief recap of how the Apache server works on Unix @@ -169,4 +171,4 @@ identifier for each request

    Apache HTTP Server Version 2.0IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_userdir.html.en b/docs/manual/mod/mod_userdir.html.en index 8e4b0aff1c..ed7d32a139 100644 --- a/docs/manual/mod/mod_userdir.html.en +++ b/docs/manual/mod/mod_userdir.html.en @@ -1,23 +1,25 @@ -mod_userdir - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_userdir

    Description: - User-specific directories
    Status: - Base
    Module Identifier: - userdir_module

    Summary

    + -->mod_userdir - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_userdir

    Description: + User-specific directories
    Status: + Base
    Module Identifier: + userdir_module

    Summary

    This module allows user-specific directories to be accessed using the http://example.com/~user/ syntax.

    -

    Directives

    See also

    Directives

    See also

    UserDir Directive

    Description: - Location of the user-specific directories
    Syntax: - UserDir directory-filename
    Default: - UserDir public_html
    Context: - server config, virtual -host
    Status: - Base
    Module: - mod_userdir
    +tutorial
    top

    UserDir Directive

    Description: + Location of the user-specific directories
    Syntax: + UserDir directory-filename
    Default: + UserDir public_html
    Context: + server config, virtual +host
    Status: + Base
    Module: + mod_userdir

    The UserDir directive sets the real directory in a user's home directory to use when a request for a @@ -74,32 +76,32 @@ http://www.foo.com/*/usr

    		http://www.foo.com/bob/usr/one/two.htmlhttp://www.foo.com/~bob/one/two.html
    -
    +
    Be careful when using this directive; for instance, "UserDir ./" would map "/~root" to "/" - which is probably undesirable. It is strongly recommended that your configuration include a "UserDir - disabled root" declaration. See also the Directory directive and the Security Tips page for + disabled root" declaration. See also the Directory directive and the Security Tips page for more information. -
    +

    Additional examples:

    To allow a few users to have UserDir directories, but not anyone else, use the following:

    -
    -UserDir disabled
    +

    +UserDir disabled
    UserDir enabled user1 user2 user3 -

    +

    To allow most users to have UserDir directories, but deny this to a few, use the following:

    -
    -UserDir enabled
    +

    +UserDir enabled
    UserDir disabled user4 user5 user6 -

    +

    -

    See also

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    See also

    \ No newline at end of file diff --git a/docs/manual/mod/mod_userdir.html.ja.jis b/docs/manual/mod/mod_userdir.html.ja.jis index 6aae2df4ab..de0f220be3 100644 --- a/docs/manual/mod/mod_userdir.html.ja.jis +++ b/docs/manual/mod/mod_userdir.html.ja.jis @@ -1,29 +1,31 @@ -mod_userdir - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mod_userdir

    $B@bL@(B: - $B%f!<%6@lMQ$N%G%#%l%/%H%j$rDs6!(B -
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<(B$B%k<1JL;R(B: - userdir_module

    $B35MW(B

    + -->mod_userdir - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mod_userdir

    $B@bL@(B: + $B%f!<%6@lMQ$N%G%#%l%/%H%j$rDs6!(B +
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k<1JL;R(B: + userdir_module

    $B35MW(B

    $B$3$N%b%8%e!<%k$O!"(B http://example.com/~user/ -$B9=J8$r;H$C$F%f!<%6@lMQ%G%#%l%/%H%j$K%"%/%;%9$G(B$B$-$k$h$&$K$7$^$9!#(B

    -

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    UserDir $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%f!<%6@lMQ%G%#%l%/%H%j$N0LCV(B
    $B9=J8(B: - UserDir directory-filename
    $B%G%U%)%k%H(B: - UserDir public_html
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: - Base
    $B%b%8%e!<%k(B: - mod_userdir
    +$B9=J8$r;H$C$F%f!<%6@lMQ%G%#%l%/%H%j$K%"%/%;%9$G$-$k$h$&$K$7$^$9!#(B

    +
    top

    UserDir $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%f!<%6@lMQ%G%#%l%/%H%j$N0LCV(B
    $B9=J8(B: + UserDir directory-filename
    $B%G%U%)%k%H(B: + UserDir public_html
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: + Base
    $B%b%8%e!<%k(B: + mod_userdir

    UserDir $B%G%#%l%/%F%#%V$O!"(B $B%f!<%6$N%I%-%e%a%s%H$X$N%j%/%(%9%H$rdirectory-filename $B$K$O + directory-filename $B$K$O

    • $B%G%#%l%/%H%jL>$+2<$K<($9$h$&$J%Q%?!<%s!#(B
      • @@ -31,7 +33,7 @@
    • disabled $B%-!<%o!<%I!#(B enabled $B%-!<%o!<%I(B ($B2<5-;2>H(B) $B$GL@<(E*$K(B $B;XDj$5$l$?%f!<%60J30$N(B - $BA4$F$N(B$B%f!<%6L>(B-$B%G(B$B%#%l%/%H%jJQ49$r(B + $BA4$F$N(B$B%f!<%6L>(B-$B%G%#%l%/%H%jJQ49$r(B $B$7$J$$$h$&$K$7$^$9!#(B
    • disabled $B%-!<%o!<%I$H!"%9%Z!<%96h@Z$j$N%f!<%6L>%j%9%H!#(B @@ -74,18 +76,18 @@ http://www.foo.com/*/usr
    		http://www.foo.com/bob/usr/one/two.htmlhttp://www.foo.com/~bob/one/two.html
    -
    +
    $B$3$N%G%#%l%/%F%#%V$r;H$&$H$-$OCm0U$7$F$/$@$5$$(B; "UserDir ./" $B$O(B "/~root" $B$+$i(B "/" $B$X%^%C%W$7$^$9$,!"(B - $B$3$l$OK>$^$7$$F0(B$B:n$G$O$J$$$G$7$g$&!#(B + $B$3$l$OK>$^$7$$F0:n$G$O$J$$$G$7$g$&!#(B "UserDir disabled root" $B@k8@$r(B $B@_Dj$NCf$K4^$a$F$*$/$3$H$r6/$/$*A&$a$7$^$9!#(B - $BDI2C>pJs$K(B Directory + $BDI2C>pJs$K(B Directory $B%G%#%l%/%F%#%V$d(B $B%;%-%e%j%F%#(B Tips $B$N%Z!<%8$b$4Mw2<$5$$!#(B -
    +

    $BDI2C$NNc(B:

    @@ -93,17 +95,17 @@ http://www.foo.com/~*/http://www.foo.com/~bob/one/two.html $B%G%#%l%/%H%j$rMxMQ$7!"$=$l0J30$K$OMxMQ$5$;$?$/$J$$>l9g$O(B $B -
    -UserDir disabled
    +

    +UserDir disabled
    UserDir enabled user1 user2 user3 -

    +

    $BBgItJ,$N%f!<%6$O(B UserDir $B%G%#%l%/%H%j$rMxMQ$9$k$1$l$I!"(B $B>/?t$N?M$OIT5v2D$K$7$?$$>l9g$O!" -

    -UserDir enabled
    +

    +UserDir enabled
    UserDir disabled user4 user5 user6 -

    +

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_usertrack.html.en b/docs/manual/mod/mod_usertrack.html.en index f4e2e4cf19..acbc3b0d1a 100644 --- a/docs/manual/mod/mod_usertrack.html.en +++ b/docs/manual/mod/mod_usertrack.html.en @@ -1,20 +1,22 @@ -mod_usertrack - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_usertrack

    Description: - + -->mod_usertrack - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_usertrack

    Description: + Clickstream logging of user activity on a site -
    Status: - Extension
    Module Identifier: - usertrack_module

    Summary

    +
    Status: + Extension
    Module Identifier: + usertrack_module

    Summary

    Previous releases of Apache have included a module which generates a 'clickstream' log of user activity on a site using cookies. This was called the "cookies" module, mod_cookies. In Apache 1.2 and later this module has been renamed the "user tracking" module, mod_usertrack. This module has been simplified and new directives added.

    -

    Directives

    Logging

    +

    Directives

    Topics

    • Logging
    • 2-digit or 4-digit dates for cookies?
    top

    Logging

    Previously, the cookies module (now the user tracking @@ -25,14 +27,14 @@ now allows multiple log files. The cookie itself is logged by using the text %{cookie}n in the log file format. For example:

    -
    +

    CustomLog logs/clickstream "%{cookie}n %r %t" -

    +

    For backward compatibility the configurable log module - implements the old CookieLog directive, but this - should be upgraded to the above CustomLog directive.

    -

    2-digit or 4-digit dates for cookies?

    + implements the old CookieLog directive, but this + should be upgraded to the above CustomLog directive.

    +
    top

    2-digit or 4-digit dates for cookies?

    (the following is from message @@ -71,13 +73,13 @@ form, but also understands 4-digit years, which can probably reach up until time late in the year "37". -

    CookieDomain Directive

    Description: - The domain to which the tracking cookie applies
    Syntax: - CookieDomain domain
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Extension
    Module: - mod_usertrack
    +
    top

    CookieDomain Directive

    Description: + The domain to which the tracking cookie applies
    Syntax: + CookieDomain domain
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Extension
    Module: + mod_usertrack

    This directive controls the setting of the domain to which the tracking cookie applies. If not present, no domain is @@ -86,13 +88,13 @@ time late in the year "37".

    The domain string must begin with a dot, and must include at least one embedded dot. That is, ".foo.com" is legal, but "foo.bar.com" and ".com" are not.

    -

    CookieExpires Directive

    Description: - Expiry time for the tracking cookie
    Syntax: - CookieExpires expiry-period
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Extension
    Module: - mod_usertrack
    +
    top

    CookieExpires Directive

    Description: + Expiry time for the tracking cookie
    Syntax: + CookieExpires expiry-period
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Extension
    Module: + mod_usertrack

    When used, this directive sets an expiry time on the cookie generated by the usertrack module. The expiry-period can be given either as a number of seconds, or in the format @@ -103,14 +105,14 @@ time late in the year "37".

    If this directive is not used, cookies last only for the current browser session.

    -

    CookieName Directive

    Description: - Name of the tracking cookie
    Syntax: - CookieName token
    Default: - CookieName Apache
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Extension
    Module: - mod_usertrack
    +
    top

    CookieName Directive

    Description: + Name of the tracking cookie
    Syntax: + CookieName token
    Default: + CookieName Apache
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Extension
    Module: + mod_usertrack

    This directive allows you to change the name of the cookie this module uses for its tracking purposes. By default the cookie is named "Apache".

    @@ -118,15 +120,15 @@ time late in the year "37".

    You must specify a valid cookie name; results are unpredictable if you use a name containing unusual characters. Valid characters include A-Z, a-z, 0-9, "_", and "-".

    -

    CookieStyle Directive

    Description: - Format of the cookie header field
    Syntax: - CookieStyle - Netscape|Cookie|Cookie2|RFC2109|RFC2965
    Default: - CookieStyle Netscape
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Extension
    Module: - mod_usertrack
    +
    top

    CookieStyle Directive

    Description: + Format of the cookie header field
    Syntax: + CookieStyle + Netscape|Cookie|Cookie2|RFC2109|RFC2965
    Default: + CookieStyle Netscape
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Extension
    Module: + mod_usertrack

    This directive controls the format of the cookie header field. The three formats allowed are:

    @@ -145,14 +147,14 @@ time late in the year "37".

    Not all clients can understand all of these formats. but you should use the newest one that is generally acceptable to your users' browsers.

    -

    CookieTracking Directive

    Description: - Enables tracking cookie
    Syntax: - CookieTracking on|off
    Default: - CookieTracking off
    Context: - server config, virtual host, directory, .htaccess
    Override: - FileInfo
    Status: - Extension
    Module: - mod_usertrack
    +
    top

    CookieTracking Directive

    Description: + Enables tracking cookie
    Syntax: + CookieTracking on|off
    Default: + CookieTracking off
    Context: + server config, virtual host, directory, .htaccess
    Override: + FileInfo
    Status: + Extension
    Module: + mod_usertrack

    When the user track module is compiled in, and "CookieTracking on" is set, Apache will start sending a user-tracking cookie for all new requests. This directive can @@ -160,4 +162,4 @@ time late in the year "37". per-directory basis. By default, compiling mod_usertrack will not activate cookies.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mod_vhost_alias.html.en b/docs/manual/mod/mod_vhost_alias.html.en index 6bb936c789..b59b83a369 100644 --- a/docs/manual/mod/mod_vhost_alias.html.en +++ b/docs/manual/mod/mod_vhost_alias.html.en @@ -1,12 +1,14 @@ -mod_vhost_alias - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_vhost_alias

    Description: - Provides for dynamically configured mass virtual -hosting
    Status: - Extension
    Module Identifier: - vhost_alias_module

    Summary

    + -->mod_vhost_alias - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mod_vhost_alias

    Description: + Provides for dynamically configured mass virtual +hosting
    Status: + Extension
    Module Identifier: + vhost_alias_module

    Summary

    This module creates dynamically configured virtual hosts, by allowing the IP address and/or the Host: header of @@ -15,8 +17,8 @@ hosting -

    Directives

    See also

    Directory Name Interpolation

    +
    top

    Directory Name Interpolation

    All the directives in this module interpolate a string into @@ -77,16 +79,16 @@ virtual hosting

    Directory Name Interpolation

    If N or M is greater than the number of parts available a single underscore is interpolated.

    -

    Examples

    +
    top

    Examples

    For simple name-based virtual hosts you might use the following directives in your server configuration file:

    -
    - UseCanonicalName Off
    +

    + UseCanonicalName Off
    VirtualDocumentRoot /usr/local/apache/vhosts/%0 -

    +

    A request for http://www.example.com/directory/file.html will be @@ -99,10 +101,10 @@ virtual hosting

    Directory Name Interpolation

    vhosts directory. To do this you might use the following in your configuration file:

    -
    - UseCanonicalName Off
    +

    + UseCanonicalName Off
    VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2 -

    +

    A request for http://www.example.isp.com/directory/file.html @@ -112,18 +114,18 @@ virtual hosting

    Directory Name Interpolation

    A more even spread of files can be achieved by hashing from the end of the name, for example:

    -
    +

    VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.-1/%2.-2/%2.-3/%2 -

    +

    The example request would come from /usr/local/apache/vhosts/isp.com/e/l/p/example/directory/file.html.

    Alternatively you might use:

    -
    +

    VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2.4+ -

    +

    The example request would come from /usr/local/apache/vhosts/isp.com/e/x/a/mple/directory/file.html.

    @@ -131,11 +133,11 @@ virtual hosting

    Directory Name Interpolation

    For IP-based virtual hosting you might use the following in your configuration file:

    -
    - UseCanonicalName DNS
    - VirtualDocumentRootIP /usr/local/apache/vhosts/%1/%2/%3/%4/docs
    +

    + UseCanonicalName DNS
    + VirtualDocumentRootIP /usr/local/apache/vhosts/%1/%2/%3/%4/docs
    VirtualScriptAliasIP /usr/local/apache/vhosts/%1/%2/%3/%4/cgi-bin -

    +

    A request for http://www.example.isp.com/directory/file.html @@ -152,78 +154,78 @@ virtual hosting

    Directory Name Interpolation

    a % directive, you can work around the problem in the following way:

    -
    +

    VirtualDocumentRoot /usr/local/apache/vhosts/%2.0.%3.0 -

    +

    A request for http://www.example.isp.com/directory/file.html will be satisfied by the file /usr/local/apache/vhosts/example.isp/directory/file.html.

    -

    The LogFormat +

    The LogFormat directives %V and %A are useful in conjunction with this module.

    -

    VirtualDocumentRoot Directive

    Description: - Dynamically configure the location of the document root -for a given virtual host
    Syntax: - VirtualDocumentRoot interpolated-directory
    Default: - none
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_vhost_alias
    +
    top

    VirtualDocumentRoot Directive

    Description: + Dynamically configure the location of the document root +for a given virtual host
    Syntax: + VirtualDocumentRoot interpolated-directory
    Default: + none
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_vhost_alias

    The VirtualDocumentRoot directive allows you to determine where Apache will find your documents based on the value of the server name. The result of expanding interpolated-directory is used as the root of the - document tree in a similar manner to the DocumentRoot directive's argument. + document tree in a similar manner to the DocumentRoot directive's argument. If interpolated-directory is none then VirtaulDocumentRoot is turned off. This directive cannot be used in the same context as VirtualDocumentRootIP.

    -

    VirtualDocumentRootIP Directive

    Description: - Dynamically configure the location of the document root -for a given virtual host
    Syntax: - VirtualDocumentRootIP interpolated-directory
    Default: - none
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_vhost_alias
    +
    top

    VirtualDocumentRootIP Directive

    Description: + Dynamically configure the location of the document root +for a given virtual host
    Syntax: + VirtualDocumentRootIP interpolated-directory
    Default: + none
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_vhost_alias

    The VirtualDocumentRootIP directive is like the VirtualDocumentRoot directive, except that it uses the IP address of the server end of the connection instead of the server name.

    -

    VirtualScriptAlias Directive

    Description: - Dynamically configure the location of the CGI directory for -a given virtual host
    Syntax: - VirtualScriptAlias interpolated-directory
    Default: - none
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_vhost_alias
    +
    top

    VirtualScriptAlias Directive

    Description: + Dynamically configure the location of the CGI directory for +a given virtual host
    Syntax: + VirtualScriptAlias interpolated-directory
    Default: + none
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_vhost_alias

    The VirtualScriptAlias directive allows you to determine where Apache will find CGI scripts in a similar manner to VirtualDocumentRoot does for other documents. It matches requests for URIs starting - /cgi-bin/, much like ScriptAlias + /cgi-bin/, much like ScriptAlias /cgi-bin/ would.

    -

    VirtualScriptAliasIP Directive

    Description: - Dynamically configure the location of the cgi directory for -a given virtual host
    Syntax: - VirtualScriptAliasIP interpolated-directory
    Default: - none
    Context: - server config, virtual host
    Status: - Extension
    Module: - mod_vhost_alias
    +
    top

    VirtualScriptAliasIP Directive

    Description: + Dynamically configure the location of the cgi directory for +a given virtual host
    Syntax: + VirtualScriptAliasIP interpolated-directory
    Default: + none
    Context: + server config, virtual host
    Status: + Extension
    Module: + mod_vhost_alias

    The VirtualScriptAliasIP directive is like the VirtualScriptAlias directive, except that it uses the IP address of the server end of the connection instead of the server name.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mpm_common.html.en b/docs/manual/mod/mpm_common.html.en index 18db1e2d90..902bf18159 100644 --- a/docs/manual/mod/mpm_common.html.en +++ b/docs/manual/mod/mpm_common.html.en @@ -1,34 +1,36 @@ -mpm_common - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mpm_common

    Description: - A collection of directives that are implemented by -more than one multi-processing module (MPM)
    Status: - MPM

    Directives

    CoreDumpDirectory Directive

    Description: - Directory where Apache attempts to -switch before dumping core
    Syntax: - CoreDumpDirectory directory
    Default: - See usage for the default setting
    Context: - server config
    Status: - MPM
    Module: - worker, perchild, prefork, mpm_winnt
    + -->mpm_common - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mpm_common

    Description: + A collection of directives that are implemented by +more than one multi-processing module (MPM)
    Status: + MPM
    top

    CoreDumpDirectory Directive

    Description: + Directory where Apache attempts to +switch before dumping core
    Syntax: + CoreDumpDirectory directory
    Default: + See usage for the default setting
    Context: + server config
    Status: + MPM
    Module: + worker, perchild, prefork, mpm_winnt

    This controls the directory to which Apache attempts to switch before dumping core. The default is in the - ServerRoot directory, however + ServerRoot directory, however since this should not be writable by the user the server runs as, core dumps won't normally get written. If you want a core dump for debugging, you can use this directive to place it in a different location.

    -

    Group Directive

    Description: - Group under which the server will answer -requests
    Syntax: - Group unix-group
    Default: - Group #-1
    Context: - server config, virtual host
    Status: - MPM
    Module: - worker, perchild, prefork
    +
    top

    Group Directive

    Description: + Group under which the server will answer +requests
    Syntax: + Group unix-group
    Default: + Group #-1
    Context: + server config, virtual host
    Status: + MPM
    Module: + worker, perchild, prefork

    The Group directive sets the group under which the server will answer requests. In order to use this directive, the stand-alone server must be run initially as root. @@ -53,16 +55,16 @@ requestsSpecial note: Use of this directive in <VirtualHost> is no longer supported. To implement the suEXEC wrapper with Apache 2.0, use the - SuexecUserGroup - directive. SECURITY: See User for a discussion of the + SuexecUserGroup + directive. SECURITY: See User for a discussion of the security considerations.

    -

    Listen Directive

    Description: - IP addresses and ports that the server -listens to
    Syntax: - Listen [IP-address:]portnumber
    Context: - server config
    Status: - MPM
    Module: - worker, perchild, prefork, mpm_winnt
    +
    top

    Listen Directive

    Description: + IP addresses and ports that the server +listens to
    Syntax: + Listen [IP-address:]portnumber
    Context: + server config
    Status: + MPM
    Module: + worker, perchild, prefork, mpm_winnt

    The Listen directive instructs Apache to listen to only specific IP addresses or ports; by default it responds to requests on all IP interfaces. The Listen directive is @@ -83,29 +85,29 @@ listens toFor example, to make the server accept connections on both port 80 and port 8000, use:

    -
    - Listen 80
    +

    + Listen 80
    Listen 8000 -

    +

    To make the server accept connections on two specified interfaces and port numbers, use

    -
    - Listen 192.170.2.1:80
    +

    + Listen 192.170.2.1:80
    Listen 192.170.2.5:8000 -

    +

    IPv6 addresses must be surrounded in square brackets, as in the following example:

    -
    +

    Listen [fe80::a00:20ff:fea7:ccea]:80 -

    -

    See also

    ListenBackLog Directive

    Description: - Maximum length of the queue of pending connections
    Syntax: - ListenBacklog backlog
    Default: - ListenBacklog 511
    Context: - server config
    Status: - MPM
    Module: - worker, perchild, prefork, mpm_winnt
    +

    +

    See also

    top

    ListenBackLog Directive

    Description: + Maximum length of the queue of pending connections
    Syntax: + ListenBacklog backlog
    Default: + ListenBacklog 511
    Context: + server config
    Status: + MPM
    Module: + worker, perchild, prefork, mpm_winnt

    The maximum length of the queue of pending connections. Generally no tuning is needed or desired, however on some systems it is desirable to increase this when under a TCP SYN @@ -117,13 +119,13 @@ listens to -

    LockFile Directive

    Description: - Location of the accept serialization lock file
    Syntax: - LockFile filename
    Default: - LockFile logs/accept.lock
    Context: - server config
    Status: - MPM
    Module: - worker, perchild, prefork
    +
    top

    LockFile Directive

    Description: + Location of the accept serialization lock file
    Syntax: + LockFile filename
    Default: + LockFile logs/accept.lock
    Context: + server config
    Status: + MPM
    Module: + worker, perchild, prefork

    The LockFile directive sets the path to the lockfile used when Apache is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or USE_FLOCK_SERIALIZED_ACCEPT. This @@ -139,43 +141,43 @@ listens to -

    MaxClients Directive

    Description: - Maximum number of child processes that will be created -to serve requests
    Syntax: - MaxClients number
    Context: - server config
    Status: - MPM
    Module: - worker, prefork
    +
    top

    MaxClients Directive

    Description: + Maximum number of child processes that will be created +to serve requests
    Syntax: + MaxClients number
    Context: + server config
    Status: + MPM
    Module: + worker, prefork

    The MaxClients directive sets the limit on the number of simultaneous requests that will be served. Any connection attempts over the MaxClients limit will normally be queued, up to a number based on the - ListenBacklog + ListenBacklog directive. Once a child process is freed at the end of a different request, the connection will then be serviced.

    -

    For non-threaded servers (i.e., prefork), +

    For non-threaded servers (i.e., prefork), MaxClients translates into the maximum number of child processes that will be launched to serve requests. The default value is 256; to increase it, you must also raise - ServerLimit.

    + ServerLimit.

    -

    For threaded servers (i.e., worker), +

    For threaded servers (i.e., worker), MaxClients restricts the total number of threads that will be available to serve clients. The default value is 16 multiplied by the value of - ThreadsPerChild. + ThreadsPerChild. To increase MaxClients to a value that requires more than 16 processes, you must also - raise ServerLimit.

    -

    MaxRequestsPerChild Directive

    Description: - Limit on the number of requests that an individual child server -will handle during its life
    Syntax: - MaxRequestsPerChild number
    Default: - MaxRequestsPerChild 10000
    Context: - server config
    Status: - MPM
    Module: - worker, perchild, prefork, mpm_winnt
    + raise ServerLimit.

    +
    top

    MaxRequestsPerChild Directive

    Description: + Limit on the number of requests that an individual child server +will handle during its life
    Syntax: + MaxRequestsPerChild number
    Default: + MaxRequestsPerChild 10000
    Context: + server config
    Status: + MPM
    Module: + worker, perchild, prefork, mpm_winnt

    The MaxRequestsPerChild directive sets the limit on the number of requests that an individual child server process will handle. After @@ -198,115 +200,115 @@ will handle during its lifeMaxSpareThreads Directive
    Description: - Maximum number of idle threads
    Syntax: - MaxSpareThreads number
    Context: - server config
    Status: - MPM
    Module: - mpm_netware, perchild, worker
    +

    top

    MaxSpareThreads Directive

    Description: + Maximum number of idle threads
    Syntax: + MaxSpareThreads number
    Context: + server config
    Status: + MPM
    Module: + mpm_netware, perchild, worker

    Maximum number of idle threads. Different MPMs deal with this directive differently.

    -

    For perchild the default is +

    For perchild the default is MaxSpareThreads 10. This MPM monitors the number of idle threads on a per-child basis. If there are too many idle threads in that child, the server will begin to kill threads within that child.

    -

    For worker the default is +

    For worker the default is MaxSpareThreads 500. This MPM deals with idle threads on a server-wide basis. If there are too many idle threads in the server then child processes are killed until the number of idle threads is less than this number.

    -

    For mpm_netware the default is +

    For mpm_netware the default is MaxSpareThreads 100. Since this MPM runs a single-process, the spare thread count is also server-wide.

    -

    See also

    MaxThreadsPerChild Directive

    Description: - Maximum number of threads per child process
    Syntax: - MaxThreadsPerChild number
    Default: - MaxThreadsPerChild 64
    Context: - server config
    Status: - MPM
    Module: - worker, perchild
    +

    See also

    top

    MaxThreadsPerChild Directive

    Description: + Maximum number of threads per child process
    Syntax: + MaxThreadsPerChild number
    Default: + MaxThreadsPerChild 64
    Context: + server config
    Status: + MPM
    Module: + worker, perchild

    Maximum number of threads per child. For MPMs with a variable number of threads per child, this directive sets the maximum number of threads that will be created in each child process. To increase this value beyond its default, it is necessary to change the value of the compile-time define HARD_THREAD_LIMIT and recompile the server.

    -

    MinSpareThreads Directive

    Description: - Minimum number of idle threads available to handle request -spikes
    Syntax: - MinSpareServers number
    Context: - server config
    Status: - MPM
    Module: - mpm_netware, perchild, worker
    +
    top

    MinSpareThreads Directive

    Description: + Minimum number of idle threads available to handle request +spikes
    Syntax: + MinSpareServers number
    Context: + server config
    Status: + MPM
    Module: + mpm_netware, perchild, worker

    Minimum number of idle threads to handle request spikes. Different MPMs deal with this directive differently.

    -

    perchild uses a default of +

    perchild uses a default of MinSpareThreads 5 and monitors the number of idle threads on a per-child basis. If there aren't enough idle threads in that child, the server will begin to create new threads within that child.

    -

    worker uses a default of MinSpareThreads +

    worker uses a default of MinSpareThreads 250 and deals with idle threads on a server-wide basis. If there aren't enough idle threads in the server then child processes are created until the number of idle threads is greater than number.

    -

    mpm_netware uses a default of +

    mpm_netware uses a default of MinSpareThreads 10 and, since it is a single-process MPM, tracks this on a server-wide bases.

    -

    See also

    NumServers Directive

    Description: - Total number of children alive at the same time
    Syntax: - NumServers number
    Default: - NumServers 2
    Context: - server config
    Status: - MPM
    Module: - perchild
    +

    See also

    top

    NumServers Directive

    Description: + Total number of children alive at the same time
    Syntax: + NumServers number
    Default: + NumServers 2
    Context: + server config
    Status: + MPM
    Module: + perchild

    Number of children alive at the same time. MPMs that use this directive do not dynamically create new child processes so this number should be large enough to handle the requests for the entire site.

    -

    PidFile Directive

    Description: - File where the server records the process ID -of the daemon
    Syntax: - PidFile filename
    Default: - PidFile logs/httpd.pid
    Context: - server config
    Status: - MPM
    Module: - worker, perchild, prefork, mpm_winnt
    +
    top

    PidFile Directive

    Description: + File where the server records the process ID +of the daemon
    Syntax: + PidFile filename
    Default: + PidFile logs/httpd.pid
    Context: + server config
    Status: + MPM
    Module: + worker, perchild, prefork, mpm_winnt

    The PidFile directive sets the file to which the server records the process id of the daemon. If the filename does not begin with a slash (/) then it is assumed to be - relative to the ServerRoot.

    + relative to the ServerRoot.

    -

    Example

    +

    Example

    PidFile /var/run/apache.pid -

    +

    It is often useful to be able to send the server a signal, - so that it closes and then reopens its ErrorLog and TransferLog, and + so that it closes and then reopens its ErrorLog and TransferLog, and re-reads its configuration files. This is done by sending a SIGHUP (kill -1) signal to the process id listed in the PidFile.

    The PidFile is subject to the same warnings about log file placement and security.

    -

    ScoreBoardFile Directive

    Description: - Location of the file used to store coordination data for -the child processes
    Syntax: - ScoreBoardFile file-path
    Default: - ScoreBoardFile logs/apache_status
    Context: - server config
    Status: - MPM
    Module: - worker, perchild, prefork
    +
    top

    ScoreBoardFile Directive

    Description: + Location of the file used to store coordination data for +the child processes
    Syntax: + ScoreBoardFile file-path
    Default: + ScoreBoardFile logs/apache_status
    Context: + server config
    Status: + MPM
    Module: + worker, perchild, prefork

    Apache uses a scoreboard to communicate between its parent and child processes. Some architectures require a file to facilitate this communication. If the file is left unspecified, Apache first @@ -315,9 +317,9 @@ the child processes

    Example

    +

    Example

    ScoreBoardFile /var/run/apache_status -

    +

    File-based shared memory is useful for third-party applications that require direct access to the scoreboard.

    @@ -326,113 +328,113 @@ the child processes    security.

    -

    See also

    SendBufferSize Directive

    Description: - TCP buffer size
    Syntax: - SendBufferSize bytes
    Context: - server config
    Status: - MPM
    Module: - worker, perchild, prefork, mpm_winnt
    +

    See also

    top

    SendBufferSize Directive

    Description: + TCP buffer size
    Syntax: + SendBufferSize bytes
    Context: + server config
    Status: + MPM
    Module: + worker, perchild, prefork, mpm_winnt

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

    -

    ServerLimit Directive

    Description: - Upper limit on configurable number of processes
    Syntax: - ServerLimit number
    Default: - ServerLimit 256 (prefork), ServerLimit 16 (worker)
    Context: - server config
    Status: - MPM
    Module: - worker, prefork
    -

    For the prefork MPM, this directive sets the - maximum configured value for MaxClients for the lifetime of the +

    top

    ServerLimit Directive

    Description: + Upper limit on configurable number of processes
    Syntax: + ServerLimit number
    Default: + ServerLimit 256 (prefork), ServerLimit 16 (worker)
    Context: + server config
    Status: + MPM
    Module: + worker, prefork
    +

    For the prefork MPM, this directive sets the + maximum configured value for MaxClients for the lifetime of the Apache process. For the worker MPM, this directive in combination - with ThreadLimit sets - the maximum configured value for MaxClients for the lifetime of the + with ThreadLimit sets + the maximum configured value for MaxClients for the lifetime of the Apache process. Any attempts to change this directive during a - restart will be ignored, but MaxClients can be modified during + restart will be ignored, but MaxClients can be modified during a restart.

    Special care must be taken when using this directive. If ServerLimit is set to a value much higher than necessary, extra, unused shared memory will be allocated. If - both ServerLimit and MaxClients are set to values + both ServerLimit and MaxClients are set to values higher than the system can handle, Apache may not start or the system may become unstable.

    -

    With the prefork MPM, use this directive only - if you need to set MaxClients higher than 256. +

    With the prefork MPM, use this directive only + if you need to set MaxClients higher than 256. Do not set the value of this directive any higher than what you - might want to set MaxClients to.

    + might want to set MaxClients to.

    -

    With the worker MPM, use this directive only - if your MaxClients and - ThreadsPerChild +

    With the worker MPM, use this directive only + if your MaxClients and + ThreadsPerChild settings require more than 16 server processes. Do not set the value of this directive any higher than the number of server - processes required by what you may want for MaxClients and ThreadsPerChild.

    -

    StartServers Directive

    Description: - Number of child server processes created at startup
    Syntax: - StartServers number
    Default: - StartServers 5
    Context: - server config
    Status: - MPM
    Module: - worker
    + processes required by what you may want for MaxClients and ThreadsPerChild.

    +
    top

    StartServers Directive

    Description: + Number of child server processes created at startup
    Syntax: + StartServers number
    Default: + StartServers 5
    Context: + server config
    Status: + MPM
    Module: + worker

    The StartServers directive sets the number of child server processes created on startup. As the number of processes is dynamically controlled depending on the load, there is usually little reason to adjust this parameter.

    -

    See also

    StartThreads Directive

    Description: - Nubmer of threads created on startup
    Syntax: - StartThreads number
    Context: - server config
    Status: - MPM
    Module: - mpm_netware, perchild
    +

    See also

    top

    StartThreads Directive

    Description: + Nubmer of threads created on startup
    Syntax: + StartThreads number
    Context: + server config
    Status: + MPM
    Module: + mpm_netware, perchild

    Number of threads created on startup. As the number of threads is dynamically controlled depending on the load, there is usually little reason to adjust this parameter.

    -

    For perchild the default is StartThreads +

    For perchild the default is StartThreads 5 and this directive tracks the number of threads per process at startup.

    -

    For mpm_netware the default is +

    For mpm_netware the default is StartThreads 50 and, since there is only a single process, this is the total number of threads created at startup to serve requests.

    -

    ThreadLimit Directive

    Description: - Sets the upper limit on the configurable number of threads -per child process
    Syntax: - ThreadLimit number
    Context: - server config
    Status: - MPM
    Module: - mpm_winnt, worker
    -

    This directive sets the maximum configured value for ThreadsPerChild for the lifetime +

    top

    ThreadLimit Directive

    Description: + Sets the upper limit on the configurable number of threads +per child process
    Syntax: + ThreadLimit number
    Context: + server config
    Status: + MPM
    Module: + mpm_winnt, worker
    +

    This directive sets the maximum configured value for ThreadsPerChild for the lifetime of the Apache process. Any attempts to change this directive - during a restart will be ignored, but ThreadsPerChild can be modified + during a restart will be ignored, but ThreadsPerChild can be modified during a restart up to the value of this directive.

    Special care must be taken when using this directive. If ThreadLimit is set to a value much higher - than ThreadsPerChild, + than ThreadsPerChild, extra unused shared memory will be allocated. If both - ThreadLimit and ThreadsPerChild are set to values + ThreadLimit and ThreadsPerChild are set to values higher than the system can handle, Apache may not start or the system may become unstable. Do not set the value of this directive - any higher than your greatest predicted setting of ThreadsPerChild for the + any higher than your greatest predicted setting of ThreadsPerChild for the current run of Apache.

    The default value for ThreadLimit is - 64 when used with worker and 1920 when used - with mpm_winnt.

    - -

    ThreadsPerChild Directive

    Description: - Number of threads created by each child process
    Syntax: - ThreadsPerChild number
    Context: - server config
    Status: - MPM
    Module: - worker, mpm_winnt
    + 64 when used with worker and 1920 when used + with mpm_winnt.

    + +
    top

    ThreadsPerChild Directive

    Description: + Number of threads created by each child process
    Syntax: + ThreadsPerChild number
    Context: + server config
    Status: + MPM
    Module: + worker, mpm_winnt

    This directive sets the number of threads created by each child process. The child creates these threads at startup and never creates more. If using an MPM like mpmt_winnt, where @@ -443,17 +445,17 @@ per child processworker and 64 when used with - mpm_winnt.

    - -

    User Directive

    Description: - The userid under which the server will answer -requests
    Syntax: - User unix-userid
    Default: - User #-1
    Context: - server config, virtual host
    Status: - MPM
    Module: - worker, perchild, prefork
    + worker and 64 when used with + mpm_winnt.

    + +
    top

    User Directive

    Description: + The userid under which the server will answer +requests
    Syntax: + User unix-userid
    Default: + User #-1
    Context: + server config, virtual host
    Status: + MPM
    Module: + worker, perchild, prefork

    The User directive sets the userid as which the server will answer requests. In order to use this directive, the standalone server must be run initially as @@ -484,12 +486,12 @@ requests -

    Special note: Use of this directive in <VirtualHost> is no longer supported. To +

    Special note: Use of this directive in <VirtualHost> is no longer supported. To configure your server for suexec use - SuexecUserGroup.

    + SuexecUserGroup.

    -

    Security

    Don't set User -(or Group) to +

    Security

    Don't set User +(or Group) to root unless you know exactly what you are doing, and what -the dangers are.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +the dangers are.

    + \ No newline at end of file diff --git a/docs/manual/mod/mpm_common.html.ja.jis b/docs/manual/mod/mpm_common.html.ja.jis index 8a0eaf3c2f..21ac129fb4 100644 --- a/docs/manual/mod/mpm_common.html.ja.jis +++ b/docs/manual/mod/mpm_common.html.ja.jis @@ -1,32 +1,34 @@ -mpm_common - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mpm_common

    $B@bL@(B: - $BFs$D0J>e$N%^%k%A%W%m%;%C%7%s%0%b%8%e(B$B!<%k(B (MPM) -$B$G
    $B%9%F!<%?%9(B: - MPM

    $B%G%#%l%/%F%#%V(B

    CoreDumpDirectory $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - Apache $B$,(B$B%3%"%@%s%W$9$kA0$K0\F0$r;n$_$k%G%#%l%/%H%j(B -
    $B9=J8(B: - CoreDumpDirectory directory
    $B%G%U%)%k%H(B: - $B%G%U%)%k%H$N@_Dj$O@bL@J8$rFI$s$G$/$@$5$$(B
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork, mpm_winnt
    + -->mpm_common - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mpm_common

    $B@bL@(B: + $BFs$D0J>e$N%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM) +$B$G
    $B%9%F!<%?%9(B: + MPM
    top

    CoreDumpDirectory $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + Apache $B$,%3%"%@%s%W$9$kA0$K0\F0$r;n$_$k%G%#%l%/%H%j(B +
    $B9=J8(B: + CoreDumpDirectory directory
    $B%G%U%)%k%H(B: + $B%G%U%)%k%H$N@_Dj$O@bL@J8$rFI$s$G$/$@$5$$(B
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork, mpm_winnt

    Apache $B$,%3%"%@%s%W$9$kA0$K0\F0$r;n$_$k%G%#%l%/%H%j$r@)8f$7$^$9!#(B - $B%G%U%)%k%HCM$O(B ServerRoot + $B%G%U%)%k%HCM$O(B ServerRoot $B%G%#%l%/%H%j$G$9$,!"$3$N%G%#%l%/%H%j$O%5!<%P$No$O%3%"%@%s%W$O=q$-9~$^$l$^$;$s!#(B - $B%G%P%C%0$N$?$a$K%3%"%@%s%W$,I,MW$G$"$l$P(B$B!"(B + $B%G%P%C%0$N$?$a$K%3%"%@%s%W$,I,MW$G$"$l$P!"(B $B$3$N%G%#%l%/%F%#%V$r;H$C$FB>$N0LCV$K%3%"%@%s%W$r=q$-=P$9$h$&$K$G$-$^$9!#(B

    -

    Group $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%j%/%(%9%H$K1~Ez$9$k:]$K=jB0$9$k%0%k!<%W(B
    $B9=J8(B: - Group unix-group
    $B%G%U%)%k%H(B: - Group #-1
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork
    +
    top

    Group $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%j%/%(%9%H$K1~Ez$9$k:]$K=jB0$9$k%0%k!<%W(B
    $B9=J8(B: + Group unix-group
    $B%G%U%)%k%H(B: + Group #-1
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork

    Group $B%G%#%l%/%F%#%V$G!"(B $B%j%/%(%9%H$K1~Ez$9$k:]$K=jB0$7$F$*$/%0%k!<%W$r@_Dj$7$^$9!#(B $B$3$N%G%#%l%/%F%#%V$r;HMQ$9$k$?$a$K$O!"%9%?%s%I%"%m%s7?$N(B @@ -51,19 +53,19 @@ $B5/F0$r9T$C$?%f!<%6$N=jB0$9$k%0%k!<%W$H$7$F

    $BFC5-;v9`(B: $B$3$N%G%#%l%/%F%#%V$r(B <VirtualHost> - $B$G;HMQ$9$k$3$H$O%5%]!<%H$5$l$J$/$J$j(B$B$^$7$?!#(BApache 2.0 $B$G(B + $B$G;HMQ$9$k$3$H$O%5%]!<%H$5$l$J$/$J$j$^$7$?!#(BApache 2.0 $B$G(B suEXEC $B%i%C%Q!<(B$B$rl9g$O!"(B - SuexecUserGroup + SuexecUserGroup $B$r;HMQ$7$F$/$@$5$$!#(B $B%;%-%e%j%F%#(B: $B%;%-%e%j%F%#>e$NCm0UE@$K4X$7$F$O!"(B - User + User $B$r$4Mw2<$5$$!#(B

    -

    Listen $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%5!<%P$,(B listen $B$9$k(BIP $B%"%I%l%9$H%]!<%HHV9f(B
    $B9=J8(B: - Listen [IP-address:]portnumber
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork, mpm_winnt
    +
    top

    Listen $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%5!<%P$,(B listen $B$9$k(BIP $B%"%I%l%9$H%]!<%HHV9f(B
    $B9=J8(B: + Listen [IP-address:]portnumber
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork, mpm_winnt

    Listen $B%G%#%l%/%F%#%V$O(B Apache $B$,FCDj$N(B IP $B%"%I%l%9$d%]!<%HHV9f$@$1$r(B listen $B$9$k$h$&$K;XDj$7$^$9!#(B $B%G%U%)%k%H$G$OA4$F$N(B IP $B%$%s%?!<%U%'!<%9$N%j%/%(%9%H$K1~Ez$7$^$9!#(B @@ -71,7 +73,7 @@ $B$b$7@_Dj%U%!%$%k$K$J$1$l$P!"%5!<%P$O5/F0$K<:GT$7$^$9!#(B $B$3$l$O0JA0$N%P!<%8%g%s$N(B Apache $B$+$iJQ99$N$"$C$?ItJ,$G$9!#(B

    -

    Listen $B%G%#%l%/%F%#(B$B%V$G$O!"FCDj$N%]!<%H$"$k$$$O(B +

    Listen $B%G%#%l%/%F%#%V$G$O!"FCDj$N%]!<%H$"$k$$$O(B $B%"%I%l%9$H%]!<%H$NAH$_9g$o$;$+$iF~$C$F$/$k%j%/%(%9%H$KBP$7$F(B $B1~Ez$9$k$h$&$K;XDj$7$^$9!#(B $B$b$7%]!<%HHV9f$@$1$,;XDj$5$l$?>l9g$O!"%5!<%P$OA4%$%s%?!<%U%'!<%9$N(B @@ -87,29 +89,29 @@

    $BNc$($P!"%5!<%P$,(B 80 $BHV%]!<%H$H(B 8000 $BHV%]!<%H$NN>J}$N(B $B%3%M%/%7%g%s$rl9g$O!" -

    - Listen 80
    +

    + Listen 80
    Listen 8000 -

    +

    $BFs$D$NFCDj$N%$%s%?!<%U%'!<%9$H%]!<%HHV9f$+$i$N%3%M%/%7%g%s$r(B $B -

    - Listen 192.170.2.1:80
    +

    + Listen 192.170.2.1:80
    Listen 192.170.2.5:8000 -

    +

    IPv6 $B%"%I%l%9$O3Q3g8L$G0O$^$J$1$l$P$J$j$^$;$s!#(B $BNc$($P -

    +

    Listen [fe80::a00:20ff:fea7:ccea]:80 -

    -

    $B;2>H(B

    ListenBackLog $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $BJ]N1>uBV$N%3%M%/%7%g%s$N%-%e!<$N:GBgD9(B
    $B9=J8(B: - ListenBacklog backlog
    $B%G%U%)%k%H(B: - ListenBacklog 511
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork, mpm_winnt
    +

    +

    $B;2>H(B

    top

    ListenBackLog $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $BJ]N1>uBV$N%3%M%/%7%g%s$N%-%e!<$N:GBgD9(B
    $B9=J8(B: + ListenBacklog backlog
    $B%G%U%)%k%H(B: + ListenBacklog 511
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork, mpm_winnt

    $BJ]N1>uBV$N%3%M%/%7%g%s$N%-%e!<$N:GBgD9$G$9!#(B $B0lHLE*$K$OD4@0$9$kI,MW$O$"$j$^$;$s$7!"D4@0$OK>$^$7$/$"$j$^$;$s!#(B $B$7$+$7!"(BTCP SYN $B%U%i%C%I%"%?%C%/$N>u672<$K$*$+$l$k>l9g$K!"(B @@ -122,13 +124,13 @@ $B%P%C%/%m%0$H$7$F;XDj$5$l$F$$$kCM$A$g$&$I$^$G;H$C$F$$$k$o$1$G$O$J$/!"(B $B@_Dj$5$l$F$$$kCM$K4p$E$$$F(B ($BDL>o$O@_DjCM$h$j$bBg$-$JCM$r(B) $B;H$C$F$$$k$3$H$KCm0U$7$F$/$@$5$$!#(B

    -

    LockFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $BNs2=$9$k$?$a$N%m%C%/%U%!%$%k$N0LCV(B
    $B9=J8(B: - LockFile filename
    $B%G%U%)%k%H(B: - LockFile logs/accept.lock
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork
    +
    top

    LockFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $BNs2=$9$k$?$a$N%m%C%/%U%!%$%k$N0LCV(B
    $B9=J8(B: + LockFile filename
    $B%G%U%)%k%H(B: + LockFile logs/accept.lock
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork

    USE_FCNTL_SERIALIZED_ACCEPT $B$^$?$O(B USE_FLOCK_SERIALIZED_ACCEPT $B$N$$$:$l$+$r;H$C$F(B Apache $B$r%3%s%Q%$%k$7$?:]$K;HMQ$9$k$3$H$K$J$k!"(B $B%m%C%/%U%!%$%k$N%Q%9$r(B LockFile @@ -145,45 +147,45 @@ $BCV$+$J$$J}$,$h$$$G$9!#$J$<$J$i!"%5!<%P$,5/F0;~$K:n@.$9$k(B $B%m%C%/%U%!%$%k$N:n@.<+BN$rK832$9$k$3$H$K$h$C$F!"(B $BC/$G$b%5!<%S%95qH]%"%?%C%/$r0z$-5/$3$9$3$H$,$G$-$k$+$i$G$9!#(B

    -

    MaxClients $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%j%/%(%9%H$K1~Ez$9$k$?$a$K:n@.$5$l$k(B -$B;R%W%m%;%9$N:GBg8D?t(B
    $B9=J8(B: - MaxClients number
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, prefork
    +
    top

    MaxClients $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%j%/%(%9%H$K1~Ez$9$k$?$a$K:n@.$5$l$k(B +$B;R%W%m%;%9$N:GBg8D?t(B
    $B9=J8(B: + MaxClients number
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, prefork

    MaxClients $B%G%#%l%/%F%#%V$O!"(B $B1~Ez$9$k$3$H$N$G$-$kF1;~%j%/%(%9%H?t$r@_Dj$7$^$9!#(B MaxClients $B@)8B?t$r1[$($k%3%M%/%7%g%s$ODL>o!"(B - ListenBacklog + ListenBacklog $B%G%#%l%/%F%#%V$G@_Dj$7$??t$^$G%-%e!<$KF~$j$^$9!#(B $BB>$N%j%/%(%9%H$N:G8e$^$GC#$7$F;R%W%m%;%9$,6u$/$H!"(B $B -

    $B%9%l%C%I$rMQ$$$J$$%5!<%P(B ($B$9$J$o$A(B prefork) +

    $B%9%l%C%I$rMQ$$$J$$%5!<%P(B ($B$9$J$o$A(B prefork) $B$G$O!"(BMaxClients - $B$O!"%j%/%(%9%H$K(B$B1~Ez$9$k$?$a$K5/F0$5$l$k(B + $B$O!"%j%/%(%9%H$K1~Ez$9$k$?$a$K5/F0$5$l$k(B $B;R%W%m%;%9$N:GBg?t$H$J$j$^$9!#(B $B%G%U%)%k%HCM$O(B 256 $B$G!"$3$l$rA}2C$5$;$?$$>l9g$O!"(B - ServerLimit + ServerLimit $B$NCM$bA}2C$5$;$kI,MW$,$"$j$^$9!#(B

    -

    $B%9%l%C%I$rMQ$$$k%5!<%P(B ($B$9$J$o$A(B worker) +

    $B%9%l%C%I$rMQ$$$k%5!<%P(B ($B$9$J$o$A(B worker) $B$G$O!"(BMaxClients $B$O!"%/%i%$%"%s%H$K1~Ez$G$-$k%9%l%C%I$NAm?t$r@)8B$7$^$9!#(B $B%G%U%)%k%HCM$O(B - ThreadsPerChild + ThreadsPerChild $B$r(B 16 $BG\$7$?CM$K$J$j$^$9!#(BMaxClients $B$r(B 16 $B%W%m%;%90J>eI,MW$JCM$^$GA}2C$5$;$?$$>l9g$O!"(B - ServerLimit + ServerLimit $B$bA}2C$5$;$kI,MW$,$"$j$^$9!#(B

    -

    MaxRequestsPerChild $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B8D!9$N;R%5!<%P$,2TF/Cf$K07$&%j%/%(%9%H?t$N>e8B(B
    $B9=J8(B: - MaxRequestsPerChild number
    $B%G%U%)%k%H(B: - MaxRequestsPerChild 10000
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork, mpm_winnt
    +
    top

    MaxRequestsPerChild $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B8D!9$N;R%5!<%P$,2TF/Cf$K07$&%j%/%(%9%H?t$N>e8B(B
    $B9=J8(B: + MaxRequestsPerChild number
    $B%G%U%)%k%H(B: + MaxRequestsPerChild 10000
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork, mpm_winnt

    MaxRequestsPerChild $B%G%#%l%/%F%#%V$O!"(B $B8D!9$N;R%5!<%P%W%m%;%9$,07$&$3$H$N$G$-$k%j%/%(%9%H$N@)8B?t$r(B $B@_Dj$7$^$9!#(BMaxRequestsPerChild @@ -206,105 +208,105 @@ $B0l$DL\$N%j%/%(%9%H$@$1$,$3$N@)8B$K3:Ev$7$^$9!#(B $B$B%3%M%/%7%g%s(B$B?t$r(B $B@)8B$9$k$h$&$K5sF0$,JQ2=$7$^$9!#(B

    -

    MaxSpareThreads $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%"%$%I%k%9%l%C%I$N:GBg?t(B
    $B9=J8(B: - MaxSpareThreads number
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - mpm_netware, perchild, worker
    +
    top

    MaxSpareThreads $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%"%$%I%k%9%l%C%I$N:GBg?t(B
    $B9=J8(B: + MaxSpareThreads number
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + mpm_netware, perchild, worker

    $B%"%$%I%k$J%9%l%C%I$N:GBg?t$G$9!#0[$J$k(B MPM $B$G$O$=$l$>$l!"(B $B$3$N%G%#%l%/%F%#%V$O0[$J$k -

    perchild $B$G$O!"(B +

    perchild $B$G$O!"(B $B%G%U%)%k%H$O(B MaxSpareThreads 10 $B$G$9!#(B $B$3$N(B MPM $B$O%"%$%I%k%9%l%C%I?t$r!"$=$l$>$l$N;R%W%m%;%9$4$H$K4F;k$7$^$9!#(B $B;R%W%m%;%9$K%"%$%I%k%9%l%C%I$,B?$9$.$k>l9g$O!"(B $B%5!<%P$O$=$N;R%W%m%;%9$K4^$^$l$k%9%l%C%I$r=*N;$7;O$a$^$9!#(B

    -

    worker $B$G$O!"(B +

    worker $B$G$O!"(B $B%G%U%)%k%H$O(B MaxSpareThreads 500 $B$G$9!#(B $B$3$N(B MPM $B$O%"%$%I%k%9%l%C%I?t$r%5!<%PA4BN$G4F;k$7$^$9!#(B $B%5!<%P$G%"%$%I%k%9%l%C%I?t$,B?$9$.$k>l9g$O!"(B $B$3$N?t;z$h$j$b>/$J$$?t$K$J$k$^$G;R%W%m%;%9$r=*N;$7$^$9!#(B

    -

    mpm_netware $B$G$O!"(B +

    mpm_netware $B$G$O!"(B $B%G%U%)%k%H$O(B MaxSpareThreads 100 $B$G$9!#(B $B$3$N(B MPM $B$O%7%s%0%k%W%m%;%9$G -

    $B;2>H(B

    MaxThreadsPerChild $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B;R%W%m%;%9Kh$N%9%l%C%I?t$N:GBg?t(B
    $B9=J8(B: - MaxThreadsPerChild number
    $B%G%U%)%k%H(B: - MaxThreadsPerChild 64
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild
    +

    $B;2>H(B

    top

    MaxThreadsPerChild $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B;R%W%m%;%9Kh$N%9%l%C%I?t$N:GBg?t(B
    $B9=J8(B: + MaxThreadsPerChild number
    $B%G%U%)%k%H(B: + MaxThreadsPerChild 64
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild

    $B;R%W%m%;%9Kh$K4^$^$l$k%9%l%C%I?t$N:GBgCM$G$9!#(B $B;R%W%m%;%9Kh$K%9%l%C%I?tJQ2=$9$k(B MPM $B$G$O!"(B $B$3$N%G%#%l%/%F%#%V$O!";R%W%m%;%9Fb$K@8@.$5$l$k%9%l%C%I?t$N(B $B:GBgCM$r@_Dj$7$^$9!#%G%U%)%k%HCM$h$j$bBg$-$$CM$K$9$k$N$G$"$l$P!"(B $B%3%s%Q%$%k;~$KDj5A$5$l$?(B HARD_THREAD_LIMIT $B$rJQ99$7$F!"%5!<%P$r:F%3%s%Q%$%k$9$kI,MW$,$"$j$^$9!#(B

    -

    MinSpareThreads $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%j%/%(%9%H$K1~Ez$9$k$3$H$N$G$-$k(B -$B%"%$%I%k%9%l%C%I?t$N:G>.?t(B
    $B9=J8(B: - MinSpareServers number
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - mpm_netware, perchild, worker
    +
    top

    MinSpareThreads $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%j%/%(%9%H$K1~Ez$9$k$3$H$N$G$-$k(B +$B%"%$%I%k%9%l%C%I?t$N:G>.?t(B
    $B9=J8(B: + MinSpareServers number
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + mpm_netware, perchild, worker

    $B%j%/%(%9%H$K1~Ez$9$k%9%l%C%I?t$N:G>.CM$G$9!#(B $B0[$J$k(B MPM $B$G$O$=$l$>$l!"(B - $B$3$N(B$B%G%#%l%/%F%#%V$O0[$J$k + $B$3$N%G%#%l%/%F%#%V$O0[$J$k -

    perchild $B$G$O!"(B +

    perchild $B$G$O!"(B $B%G%U%)%k%H$O(B MinSpareThreads 5 $B$G!"(B $B%"%$%I%k%9%l%C%I?t$r;R%W%m%;%9Kh$K4F;k$7$^$9!#(B $B$b$7;R%W%m%;%9$K==J,$J?t$N%9%l%C%I$,$J$1$l$P!"(B $B%5!<%P$O$=$N;R%W%m%;%9$K?7$7$$%9%l%C%I$r:n$j;O$a$^$9!#(B

    -

    worker $B$G$O!"(B +

    worker $B$G$O!"(B $B%G%U%)%k%H$O(B MinSpareThreads 250 $B$G!"(B $B%"%$%I%k%9%l%C%I?t$r%5!<%PA4BN$G4F;k$7$^$9!#(B $B$b$7%5!<%P$K==J,$J?t$N%"%$%I%k%9%l%C%I$,$J$1$l$P!"(B $B%"%$%I%k%9%l%C%I?t$,$3$N?t$h$j$bBg$-$/$J$k$^$G(B $B?7$7$$;R%W%m%;%9$,@8@.$5$l$^$9!#(B

    -

    mpm_netware $B$G$O!"(B +

    mpm_netware $B$G$O!"(B $B%G%U%)%k%H$O(B MinSpareThreads 10 $B$G!"(B $B%7%s%0%k%W%m%;%9(B MPM $B$G$9$N$G!"%5!<%PA4BN$G4IM}$5$l$^$9!#(B

    -

    $B;2>H(B

    NumServers $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $BF1;~$K5/F0$7$F$$$k;R%W%m%;%9$NAm?t(B
    $B9=J8(B: - NumServers number
    $B%G%U%)%k%H(B: - NumServers 2
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - perchild
    +

    $B;2>H(B

    top

    NumServers $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $BF1;~$K5/F0$7$F$$$k;R%W%m%;%9$NAm?t(B
    $B9=J8(B: + NumServers number
    $B%G%U%)%k%H(B: + NumServers 2
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + perchild

    $BF1;~$K5/F0$7$F$$$k;R%W%m%;%9$N?t$G$9!#(B $B$3$N%G%#%l%/%F%#%V$r;HMQ$9$k(B MPM $B$OF0E*$K?7$7$$;R%W%m%;%9$r(B $B@8@.$9$k$3$H$O9T$o$J$$$N$G!"%5%$%HA4BN$KMh$k%j%/%(%9%HA4$F$r(B $B==J,07$($kDxEY$KBg$-$J?t$K@_Dj$7$F$*$/I,MW$,$"$j$^$9!#(B

    -

    PidFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%G!<%b%s$N%W%m%;%9(B ID -$B$r%5!<%P$,5-O?$9$k$?$a$N%U%!%$%k(B
    $B9=J8(B: - PidFile filename
    $B%G%U%)%k%H(B: - PidFile logs/httpd.pid
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork, mpm_winnt
    +
    top

    PidFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%G!<%b%s$N%W%m%;%9(B ID +$B$r%5!<%P$,5-O?$9$k$?$a$N%U%!%$%k(B
    $B9=J8(B: + PidFile filename
    $B%G%U%)%k%H(B: + PidFile logs/httpd.pid
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork, mpm_winnt

    PidFile $B%G%#%l%/%F%#%V$G!"(B $B%G!<%b%s$N%W%m%;%9(B ID $B$r%5!<%P$,5-O?$9$k%U%!%$%k$r@_Dj$7$^$9!#(B $B$b$7%U%!%$%kL>$,%9%i%C%7%e(B (/) $B$G;O$^$i$J$$>l9g$O!"(B - ServerRoot + ServerRoot $B$+$i$NAjBPE*$J$b$N$H$7$F07$o$l$^$9!#(B

    -

    $BNc(B

    +

    $BNc(B

    PidFile /var/run/apache.pid -

    +

    -

    $B%5!<%P$,(B ErrorLog +

    $B%5!<%P$,(B ErrorLog $B$d(B TransferLog $B$rJD$8$F3+$-D>$7$?$j!"@_Dj%U%!%$%k$r(B - $B:FFI9~$7$?$j$5$;$k$?$a$K!"%5!<%P$K%7%0%J%k(B$B$rAw$k$3$H$,$G$-$k$H(B + $B:FFI9~$7$?$j$5$;$k$?$a$K!"%5!<%P$K%7%0%J%k$rAw$k$3$H$,$G$-$k$H(B $BJXMx$J$3$H$,$"$j$^$9!#(B $B$3$l$O(B SIGHUP (kill -1) $B%7%0%J%k$r(B PidFile $B$K=q$+$l$F$$$k%W%m%;%9(B ID $B$KAw$k$3$H$G$G$-$^$9!#(B

    @@ -312,14 +314,14 @@

    PidFile $B$K$O!"%m%0%U%!%$%k$N@_CV0LCV$d(B $B%;%-%e%j%F%#(B $B$HA4$/F1$8Cm0UE@$,$"$j$^$9!#(B

    -

    ScoreBoardFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B;R%W%m%;%9$HO"7H$9$k$?$a$N%G!<%?$rJ]B8$9$k(B -$B%U%!%$%k$N0LCV(B
    $B9=J8(B: - ScoreBoardFile file-path
    $B%G%U%)%k%H(B: - ScoreBoardFile logs/apache_status
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork
    +
    top

    ScoreBoardFile $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B;R%W%m%;%9$HO"7H$9$k$?$a$N%G!<%?$rJ]B8$9$k(B +$B%U%!%$%k$N0LCV(B
    $B9=J8(B: + ScoreBoardFile file-path
    $B%G%U%)%k%H(B: + ScoreBoardFile logs/apache_status
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork

    Apache $B$O?F%W%m%;%9$H;R%W%m%;%94V$NDL?.$K%9%3%"%\!<%I$rMQ$$$^$9!#(B $B$3$NDL?.5!G=$K%U%!%$%k$rI,MW$H$9$k%"!<%-%F%/%A%c$b$"$j$^$9!#(B $B%U%!%$%k$,;XDj$5$l$F$$$J$1$l$P!"(BApache $B$O$^$:%a%b%j>e(B @@ -328,9 +330,9 @@ $B$3$N%G%#%l%/%F%#%V$r;XDj$9$k$H!"(BApache $B$OI,$:%G%#%9%/$K%U%!%$%k$r@8@.$7$^$9!#(B

    -

    $BNc(B

    +

    $BNc(B

    ScoreBoardFile /var/run/apache_status -

    +

    $B%U%!%$%k%Y!<%9$N6&M-%a%b%j$O!"%5!<%I%Q!<%F%#!<@=$N%"%W%j%1!<%7%g%s$G(B $B%9%3%"%\!<%I$KD>@\%"%/%;%9$9$kI,MW$,$"$k>l9g$KLr$KN)$A$^$9!#(B

    @@ -340,148 +342,148 @@ $B$7$+$7!"%m%0%U%!%$%k$N@_CV0LCV$d(B $B%;%-%e%j%F%#(B $B$HF1MM$NCm0UE@$,$"$k$N$G!"Cm0U$7$F$/$@$5$$!#(B

    -

    $B;2>H(B

    SendBufferSize $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - TCP $B%P%C%U%!%5%$%:(B
    $B9=J8(B: - SendBufferSize bytes
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork, mpm_winnt
    +

    $B;2>H(B

    top

    SendBufferSize $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + TCP $B%P%C%U%!%5%$%:(B
    $B9=J8(B: + SendBufferSize bytes
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork, mpm_winnt

    $B%5!<%P$O(B TCP $B%P%C%U%!%5%$%:$r;XDj$5$l$?%P%$%H?t$K@_Dj$7$^$9!#(B $B9bB.$G9b%l%$%F%s%7$J4D6-$G(B ($BNc(B 100ms $BDxEY!"BgN&2#CG9bB.DL?.O)$J$I(B) $B8E$$0lHLE*$J(B OS $B$N%G%U%)%k%HCM$rA}$d$9$N$KHs>o$KJXMx$G$9!#(B

    -

    ServerLimit $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B@_Dj2DG=$J%5!<%P%W%m%;%9?t$N>e8B(B
    $B9=J8(B: - ServerLimit number
    $B%G%U%)%k%H(B: - ServerLimit 256 (prefork), ServerLimit 16 (worker)
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, prefork
    -

    prefork MPM $B$N>l9g$O!"$3$N%G%#%l%/%F%#%V$O(B +

    top

    ServerLimit $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B@_Dj2DG=$J%5!<%P%W%m%;%9?t$N>e8B(B
    $B9=J8(B: + ServerLimit number
    $B%G%U%)%k%H(B: + ServerLimit 256 (prefork), ServerLimit 16 (worker)
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, prefork
    +

    prefork MPM $B$N>l9g$O!"$3$N%G%#%l%/%F%#%V$O(B Apache $B%W%m%;%92TF/Cf$K$*$1$k(B - MaxClients + MaxClients $B$K@_Dj2DG=$J>e8BCM$r@_Dj$9$k$3$H$K$J$j$^$9(B ($BLuCm(B: prefork $B$N>l9g$OF1;~%/%i%$%"%s%H?t(B = $B%5!<%P%W%m%;%9?t$J$N$G(B) $B!#(B - worker MPM $B$N>l9g$K$O!"$3$N%G%#%l%/%F%#%V$O(B - ThreadLimit + worker MPM $B$N>l9g$K$O!"$3$N%G%#%l%/%F%#%V$O(B + ThreadLimit $B%G%#%l%/%F%#%V$HAH$_9g$o$;$F!"(B Apache $B%W%m%;%92TF/Cf$K$*$1$k(B - MaxClients + MaxClients $B$K@_Dj2DG=$J>e8BCM$r@_Dj$9$k$3$H$K$J$j$^$9!#(B $B:F5/F0Cf$K$3$N%G%#%l%/%F%#%V$rJQ99$7$F$bL5;k$5$l$^$9$,!"(B - MaxClients + MaxClients $B$O:F5/F0Cf$K=$@5$9$k$3$H$,$G$-$^$9!#(B

    $B$3$N%G%#%l%/%F%#%V$r;HMQ$9$k:]$OFC$KCm0U$7$F$/$@$5$$!#(B ServerLimit $B$,I,MW0J>e$KBg$-(B$B$JCM$K(B $B@_Dj$5$l$?>l9g$O!"M>7W$JL$;HMQ6&M-%a%b%j$,3d$jEv$F$i$l$^$9!#(B ServerLimit $B$H(B - MaxClients + MaxClients $B$,%7%9%F%`$N07$($kHO0O$r1[$($?@_DjCM$K$J$C$F$$$k$H!"(B Apache $B$O5/F0$7$J$$$+!"5/F0$7$F$bIT0BDj$K$J$k$G$7$g$&!#(B

    -

    prefork MPM $B$G$O!"(B - MaxClients +

    prefork MPM $B$G$O!"(B + MaxClients $B$r(B 256 $B$h$j$bBg$-$JCM$K@_Dj$9$kI,MW$,$"$k;~$K$@$1;HMQ$7$F$/$@$5$$!#(B - $B4uK>$N(B MaxClients + $B4uK>$N(B MaxClients $B?t$H$/$i$Y$F!"I,MW0J>e$KBg$-$JCM$r;XDj$9$k$3$H$OHr$1$F$/$@$5$$!#(B

    -

    worker MPM $B$G$O!"(B - MaxClients $B$H(B - ThreadsPerChild +

    worker MPM $B$G$O!"(B + MaxClients $B$H(B + ThreadsPerChild $B$N@_Dj$G(B 16 $B%5!<%P%W%m%;%90J>eI,MW$K$J$k>l9g$K$N$_;HMQ$7$F$/$@$5$$!#(B $B4uK>$N(B - MaxClients $B$H(B - ThreadsPerChild + MaxClients $B$H(B + ThreadsPerChild $B$H$/$i$Y$F!"I,MW$H$J$k%5!<%P%W%m%;%9?t0J>e$KBg$-$JCM$r(B $B@_Dj$9$k$3$H$OHr$1$F$/$@$5$$!#(B

    -

    StartServers $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B5/F0;~$K@8@.$5$l$k;R%5!<%P%W%m%;%9$N?t(B
    $B9=J8(B: - StartServers number
    $B%G%U%)%k%H(B: - StartServers 5
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker
    +
    top

    StartServers $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B5/F0;~$K@8@.$5$l$k;R%5!<%P%W%m%;%9$N?t(B
    $B9=J8(B: + StartServers number
    $B%G%U%)%k%H(B: + StartServers 5
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker

    StartServers $B%G%#%l%/%F%#%V$O!"(B $B5/F0;~$K@8@.$5$l$k;R%5!<%P%W%m%;%9$N?t$r@_Dj$7$^$9!#(B $B%W%m%;%9?t$OIi2Y$K1~$8$FF0E*$K@)8f$5$l$^$9$N$G!"(B $BDL>o$O$3$NCM$rD4@0$9$kM}M3$O$"$^$j$J$$$G$7$g$&!#(B

    -

    $B;2>H(B

    StartThreads $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B5/F0;~$K@8@.$5$l$k%9%l%C%I$N?t(B
    $B9=J8(B: - StartThreads number
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - mpm_netware, perchild
    +

    $B;2>H(B

    top

    StartThreads $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B5/F0;~$K@8@.$5$l$k%9%l%C%I$N?t(B
    $B9=J8(B: + StartThreads number
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + mpm_netware, perchild

    $B5/F0;~$K@8@.$5$l$k%9%l%C%I$N?t$G$9!#(B $B%9%l%C%I?t$OIi2Y$K1~$8$FF0E*$K@)8f$5$l$^$9$N$G!"(B $BDL>o$O$3$NCM$rD4@0$9$kM}M3$O$"$^$j$J$$$G$7$g$&!#(B

    -

    perchild $B$G$N%G%U%)%k%H$O(B +

    perchild $B$G$N%G%U%)%k%H$O(B StartThreads 5 $B$G!"$3$N%G%#%l%/%F%#%V$O5/F0;~$K(B $B%W%m%;%9Kh$N%9%l%C%I?t$rDI@W$7$^$9!#(B

    -

    mpm_netware $B$G$N%G%U%)%k%H$O(B +

    mpm_netware $B$G$N%G%U%)%k%H$O(B StartThreads 50 $B$G!"(B $B$3$N>l9g%W%m%;%9$O0l$D$7$+$J$$$N$G!"(B $B5/F0;~$K%j%/%(%9%H$K1~Ez$9$k%9%l%C%I$NAm?t$H$J$j$^$9!#(B

    -

    ThreadLimit $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B@_Dj2DG=$J;R%W%m%;%9Kh$N%9%l%C%I?t$N>e8B$r(B -$B@_Dj$7$^$9(B
    $B9=J8(B: - ThreadLimit number
    $B%G%U%)%k%H(B: - ThreadLimit 64
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker
    +
    top

    ThreadLimit $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B@_Dj2DG=$J;R%W%m%;%9Kh$N%9%l%C%I?t$N>e8B$r(B +$B@_Dj$7$^$9(B
    $B9=J8(B: + ThreadLimit number
    $B%G%U%)%k%H(B: + ThreadLimit 64
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker

    $B$3$N%G%#%l%/%F%#%V$O(B Apache $B%W%m%;%92TF/Cf$K$*$1$k(B - ThreadsPerChild + ThreadsPerChild $B$K@_Dj2DG=$J>e8BCM$r@_Dj$7$^$9!#:F5/F0;~$K$3$N%G%#%l%/%F%#%V$NCM$r(B $BJQ99$7$F$bL5;k$5$l$^$9$,!"(B - ThreadsPerChild + ThreadsPerChild $B$O:F5/F0Cf$K!"$3$N%G%#%l%/%F%#%V$G;XDj$5$l$?>e8BCM$^$G(B $BJQ99$9$k$3$H$,$G$-$^$9!#(B

    $B$3$N%G%#%l%/%F%#%V$r;HMQ$9$k:]$OFC$KCm0U$7$F$/$@$5$$!#(B ThreadLimit $B$,(B - ThreadsPerChild + ThreadsPerChild $B$h$j$b$:$C$HBg$-$JCM$K@_Dj$5$l$?>l9g$O!"(B $BM>7W$JL$;HMQ6&M-%a%b%j$,3d$jEv$F$i$l$F$7$^$$$^$9!#(B ThreadLimit $B$,(B - ThreadsPerChild + ThreadsPerChild $B$NN>J}$,%7%9%F%`$N07$($kHO0O$rD6$($F$$$k>l9g$O!"(B Apache $B$O5/F0$7$J$$$+!"5/F0$7$?$H$7$F$bIT0BDj$K$J$k$G$7$g$&!#(B

    $B$3$N%G%#%l%/%F%#%V$O(B - ThreadsPerChild + ThreadsPerChild $B$r(B 64 $B$h$j$bBg$-$JCM$K@_Dj$9$kI,MW$,$"$k>l9g$K$N$_;HMQ$7$F$/$@$5$$!#(B $B$3$N%G%#%l%/%F%#%V$NCM$O!"4uK>$N(B - ThreadsPerChild + ThreadsPerChild $B$h$j$bBg$-$JCM$K@_Dj$7$J$$$G$/$@$5$$!#(B

    -

    ThreadsPerChild $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B;R%W%m%;%9$=$l$>$l$K@8@.$5$l$k%9%l%C%I?t(B
    $B9=J8(B: - ThreadsPerChild number
    $B%G%U%)%k%H(B: - ThreadsPerChild 50
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, mpm_winnt
    +
    top

    ThreadsPerChild $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B;R%W%m%;%9$=$l$>$l$K@8@.$5$l$k%9%l%C%I?t(B
    $B9=J8(B: + ThreadsPerChild number
    $B%G%U%)%k%H(B: + ThreadsPerChild 50
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, mpm_winnt

    $B$3$N%G%#%l%/%F%#%V$O!"$=$l$>$l$N;R%W%m%;%9$G@8@.$5$l$k(B $B%9%l%C%I?t$r@_Dj$7$^$9!#(B $B;R%W%m%;%9$O3+;O;~$K$3$l$i$N%9%l%C%I$r@8@.$7$F!"(B - $B$=$N8e$O@8@.$7$^$;$s!#(Bmpm_winnt $B$N$h$&$J!"(B + $B$=$N8e$O@8@.$7$^$;$s!#(Bmpm_winnt $B$N$h$&$J!"(B $B;R%W%m%;%9$,0l$D$7$+$J$$$h$&$J(B MPM $B$rMxMQ$7$F$$$k$N$G$"$l$P!"(B $B$3$NCM$O%5!<%P$NIi2YA4BN$r==J,worker $B$N$h$&$J!"(B + $BBg$-$/$J$1$l$P$J$j$^$;$s!#(Bworker $B$N$h$&$J!"(B $B;R%W%m%;%9$,J#?t$"$k$h$&$J(B MPM $B$rMxMQ$7$F$$$k$N$G$"$l$P!"(B $B%5!<%P$NDL>oIi2Y$r==J,07$($kDxEY$K!"(B $B%9%l%C%IAm?t$,B?$/$J$1$l$P$J$j$^$;$s!#(B

    -

    User $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%j%/%(%9%H$K1~Ez$9$k:]$KMQ$$$k%f!<%6(B ID
    $B9=J8(B: - User unix-userid
    $B%G%U%)%k%H(B: - User #-1
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - worker, perchild, prefork
    +
    top

    User $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%j%/%(%9%H$K1~Ez$9$k:]$KMQ$$$k%f!<%6(B ID
    $B9=J8(B: + User unix-userid
    $B%G%U%)%k%H(B: + User #-1
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B, $B%P!<%A%c%k%[%9%H(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + worker, perchild, prefork

    User $B%G%#%l%/%F%#%V$O(B $B%5!<%P$,%j%/%(%9%H$K1~Ez$9$k:]$KMQ$$$k%f!<%6(B ID $B$r@_Dj$7$^$9!#(B $B$3$N%G%#%l%/%F%#%V$r;HMQ$9$k$?$a$K$O!"%9%?%s%I%"%m%s7?$N(B @@ -516,16 +518,16 @@ $B8"8B$Go$G$9!#(B

    $BFC5-;v9`(B: $B$3$N%G%#%l%/%F%#%V$r(B - <VirtualHost> + <VirtualHost> $B$G;HMQ$9$k$3$H$O%5%]!<%H$5$l$J$/$J$j$^$7$?!#(B suexec $B8~$1$K%5!<%P$r@_Dj$9$k$N$G$"$l$P!"(B - SuexecUserGroup + SuexecUserGroup $B$r;HMQ$7$F$/$@$5$$!#(B

    -

    $B%;%-%e%j%F%#(B

    +

    $B%;%-%e%j%F%#(B

    $B<+J,$,2?$r$d$C$F$$$k$N$+@53N$KGD0.$7$F$$$J$$!"(B $B$=$7$F$=$N4m81@-$rGD0.$7$F$$$J$$$N$G$"$l$P!"(B User -($B$d(B Group) -$B$r(B root $B$K@_Dj$7$J$$$G$/$@$5$$!#(B

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file +($B$d(B Group) +$B$r(B root $B$K@_Dj$7$J$$$G$/$@$5$$!#(B

    + \ No newline at end of file diff --git a/docs/manual/mod/mpm_netware.html.en b/docs/manual/mod/mpm_netware.html.en index 9a87a375a2..10b91f8c20 100644 --- a/docs/manual/mod/mpm_netware.html.en +++ b/docs/manual/mod/mpm_netware.html.en @@ -1,12 +1,14 @@ -mpm_netware - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mpm_netware

    Description: - Multi-Processing Module implementing an exclusively threaded web - server optimized for Novell NetWare
    Status: - MPM
    Module Identifier: - mpm_netware_module

    Summary

    + -->mpm_netware - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mpm_netware

    Description: + Multi-Processing Module implementing an exclusively threaded web + server optimized for Novell NetWare
    Status: + MPM
    Module Identifier: + mpm_netware_module

    Summary

    This Multi-Processing Module (MPM) implements an exclusively threaded web server that has been optimized for Novell NetWare.

    @@ -34,29 +36,29 @@

    MaxRequestsPerChild controls how frequently the server recycles processes by killing old ones and launching new - ones.  On the NetWare OS it is highly recommended that this directive - remain set to 0.  This allows worker threads to continue servicing + ones.  On the NetWare OS it is highly recommended that this directive + remain set to 0.  This allows worker threads to continue servicing requests indefinitely.

    See also: Setting which addresses and ports Apache uses.

    -

    Directives

    MaxThreads Directive

    Description: -
    Syntax: - MaxThreads number
    Default: - MaxThreads 250
    Context: - server config
    Status: - MPM
    Module: - mpm_netware
    +
    top

    MaxThreads Directive

    Description: +
    Syntax: + MaxThreads number
    Default: + MaxThreads 250
    Context: + server config
    Status: + MPM
    Module: + mpm_netware

    The MaxThreads directive sets the desired maximum number worker threads allowable.

    -

    ThreadStackSize Directive

    Description: -
    Syntax: - ThreadStackSize number
    Default: - ThreadStackSize 65536
    Context: - server config
    Status: - MPM
    Module: - mpm_netware
    +
    top

    ThreadStackSize Directive

    Description: +
    Syntax: + ThreadStackSize number
    Default: + ThreadStackSize 65536
    Context: + server config
    Status: + MPM
    Module: + mpm_netware

    This directive tells the server what stack size to use for each of the running threads. If you ever get a stack overflow you will need to bump this number to a higher setting.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mpm_winnt.html.en b/docs/manual/mod/mpm_winnt.html.en index 4c5769d069..37ea5a2595 100644 --- a/docs/manual/mod/mpm_winnt.html.en +++ b/docs/manual/mod/mpm_winnt.html.en @@ -1,14 +1,16 @@ -mpm_winnt - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mpm_winnt

    Description: - This Multi-Processing Module is optimized for Windows - NT.
    Status: - MPM
    Module Identifier: - mpm_winnt_module

    Summary

    + -->mpm_winnt - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module mpm_winnt

    Description: + This Multi-Processing Module is optimized for Windows + NT.
    Status: + MPM
    Module Identifier: + mpm_winnt_module

    Summary

    This Multi-Processing Module (MPM) is the default for the Windows NT operating systems. It uses a single control process which launches a single child process which in turn creates threads to handle requests

    -

    Directives

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/mpm_winnt.html.ja.jis b/docs/manual/mod/mpm_winnt.html.ja.jis index a571910f19..3b61dbd8f5 100644 --- a/docs/manual/mod/mpm_winnt.html.ja.jis +++ b/docs/manual/mod/mpm_winnt.html.ja.jis @@ -1,15 +1,17 @@ -mpm_winnt - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B mpm_winnt

    $B@bL@(B: - Windows NT -$B8~$1$K:GE,2=$5$l$?(B$B%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<(B$B%k<1JL;R(B: - mpm_winnt_module

    $B35MW(B

    -

    $B$3$N%^%k%A%W%m%;%C(B$B%7%s%0%b%8%e!<%k(B (MPM) + -->mpm_winnt - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B mpm_winnt

    $B@bL@(B: + Windows NT +$B8~$1$K:GE,2=$5$l$?%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k<1JL;R(B: + mpm_winnt_module

    $B35MW(B

    +

    $B$3$N%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM) $B$O(B Windows NT $B$G$N%G%U%)%k%H$K$J$j$^$9!#(B $B0l$D$N@)8fMQ%W%m%;%9$rMQ$$!"$3$l$,0l$D$N;R%W%m%;%9$r5/F0$7!"(B $B$=$7$F;R%W%m%;%9$,%j%/%(%9%H$r -

    $B%G%#%l%/%F%#%V(B

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/perchild.html.en b/docs/manual/mod/perchild.html.en index 86cca9f16b..3ef8cceee4 100644 --- a/docs/manual/mod/perchild.html.en +++ b/docs/manual/mod/perchild.html.en @@ -1,17 +1,19 @@ -perchild - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module perchild

    Description: - Multi-Processing Module allowing for daemon processes + -->perchild - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module perchild

    Description: + Multi-Processing Module allowing for daemon processes serving requests to be assigned a variety of different - userids
    Status: - MPM
    Module Identifier: - mpm_perchild_module

    Summary

    -
    + userids
    Status: + MPM
    Module Identifier: + mpm_perchild_module

    Summary

    +
    This MPM does not currently work on most platforms. Work is ongoing to make it functional. -
    +

    This Multi-Processing Module (MPM) implements a hybrid multi-process, multi-threaded web server. A fixed number of @@ -20,9 +22,9 @@ make it functional. threads in each process.

    A single control process launches the number of child processes - indicated by the NumServers directive at server + indicated by the NumServers directive at server startup. Each child process creates threads as specified in the - StartThreads directive. + StartThreads directive. The individual threads then listen for connections and serve them when they arrive.

    @@ -32,27 +34,27 @@ make it functional. threads to be created. For each child process, Apache assesses the number of idle threads and creates or destroys threads to keep this number within the boundaries specified by - MinSpareThreads - and MaxSpareThreads. + MinSpareThreads + and MaxSpareThreads. Since this process is very self-regulating, it is rarely necessary to modify these directives from their default values. The maximum number of clients that may be served simultaneously is determined by multiplying the number of server processes - that will be created (NumServers) by the maximum + that will be created (NumServers) by the maximum number of threads created in each process - (MaxThreadsPerChild).

    + (MaxThreadsPerChild).

    While the parent process is usually started as root under Unix in order to bind to port 80, the child processes and threads are launched by Apache as a less-privileged user. The - User and Group directives are used to + User and Group directives are used to set the privileges of the Apache child processes. The child processes must be able to read all the content that will be served, but should have as few privileges beyond that as possible. In addition, unless suexec is used, these directives also set the privileges which will be inherited by CGI scripts.

    -

    MaxRequestsPerChild +

    MaxRequestsPerChild controls how frequently the server recycles processes by killing old ones and launching new ones.

    @@ -65,25 +67,25 @@ make it functional. userids. These processes can then be associated with specific virtual hosts.

    -

    Directives

    AssignUserId Directive

    Description: -
    Syntax: - AssignUserID user_id group_id
    Context: - virtual host
    Status: - MPM
    Module: - perchild
    +
    top

    AssignUserId Directive

    Description: +
    Syntax: + AssignUserID user_id group_id
    Context: + virtual host
    Status: + MPM
    Module: + perchild

    Tie a virtual host to a specific child process. Requests addressed to the virtual host where this directive appears will be served by the process running with the specified user and group id.

    -

    ChildPerUserId Directive

    Description: -
    Syntax: - ChildPerUserID user_id -group_id child_id
    Context: - server config
    Status: - MPM
    Module: - perchild
    +
    top

    ChildPerUserId Directive

    Description: +
    Syntax: + ChildPerUserID user_id +group_id child_id
    Context: + server config
    Status: + MPM
    Module: + perchild

    Specify a user id and group id for a specific child process. The number of -children is set by the NumServers -directive. For example, the default value for NumServers is 5 and that means +children is set by the NumServers +directive. For example, the default value for NumServers is 5 and that means children ids 1,2,3,4 and 5 are available for assigment. If a child does not -have an associated ChildPerUserID, it inherits the User and Group settings from the main server

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +have an associated ChildPerUserID, it inherits the User and Group settings from the main server

    +
    \ No newline at end of file diff --git a/docs/manual/mod/prefork.html.en b/docs/manual/mod/prefork.html.en index c65b4ffbe3..c9a728dcb6 100644 --- a/docs/manual/mod/prefork.html.en +++ b/docs/manual/mod/prefork.html.en @@ -1,11 +1,13 @@ -prefork - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module prefork

    Description: - Implements a non-threaded, pre-forking web server
    Status: - MPM
    Module Identifier: - mpm_prefork_module

    Summary

    + -->prefork - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module prefork

    Description: + Implements a non-threaded, pre-forking web server
    Status: + MPM
    Module Identifier: + mpm_prefork_module

    Summary

    This Multi-Processing Module (MPM) implements a non-threaded, pre-forking web server that handles requests in a manner similar to Apache 1.3. It is appropriate for sites that need to avoid @@ -15,13 +17,13 @@

    This MPM is very self-regulating, so it is rarely necessary to adjust its configuration directives. Most important is that - MaxClients be big enough to + MaxClients be big enough to handle as many simultaneous requests as you expect to receive, but small enough to assure that there is enough physical RAM for all processes.

    -

    Directives

    See also

    How it Works

    +
    top

    How it Works

    A single control process is responsible for launching child processes which listen for connections and serve them when they arrive. Apache always tries to maintain several spare @@ -30,38 +32,38 @@ child processes to be forked before their requests can be served.

    -

    The StartServers, - MinSpareServers, - MaxSpareServers, and - MaxClients regulate how +

    The StartServers, + MinSpareServers, + MaxSpareServers, and + MaxClients regulate how the parent process creates children to serve requests. In general, Apache is very self-regulating, so most sites do not need to adjust these directives from their default values. Sites which need to serve more than 256 simultaneous requests may need to - increase MaxClients, - while sites with limited memory may need to decrease MaxClients to keep the server from + increase MaxClients, + while sites with limited memory may need to decrease MaxClients to keep the server from thrashing (swapping memory to disk and back). More information about tuning process creation is provided in the performance hints documentation.

    While the parent process is usually started as root under Unix in order to bind to port 80, the child processes are launched by - Apache as a less-privileged user. The User and Group directives are used to set + Apache as a less-privileged user. The User and Group directives are used to set the privileges of the Apache child processes. The child processes must be able to read all the content that will be served, but should have as few privileges beyond that as possible.

    -

    MaxRequestsPerChild +

    MaxRequestsPerChild controls how frequently the server recycles processes by killing old ones and launching new ones.

    -

    AcceptMutex Directive

    Description: - Method that Apache uses to serialize multiple children -accepting requests on network sockets
    Syntax: - AcceptMutex default|method
    Default: - AcceptMutex default
    Context: - server config
    Status: - MPM
    Module: - prefork
    +
    top

    AcceptMutex Directive

    Description: + Method that Apache uses to serialize multiple children +accepting requests on network sockets
    Syntax: + AcceptMutex default|method
    Default: + AcceptMutex default
    Context: + server config
    Status: + MPM
    Module: + prefork

    The AcceptMutex directives sets the method that Apache uses to serialize multiple children accepting requests on network sockets. Prior to Apache 2.0, the method was @@ -81,12 +83,12 @@ accepting requests on network socketsLockFile directive. + file defined by the LockFile directive.

    fcntl
    uses the fnctl(2) system call to lock the - file defined by the LockFile directive.
    + file defined by the LockFile directive.
    sysvsem
    @@ -97,13 +99,13 @@ accepting requests on network socketsMaxSpareServers Directive
    Description: - Maximum number of idle child server processes
    Syntax: - MaxSpareServers number
    Default: - MaxSpareServers 10
    Context: - server config
    Status: - MPM
    Module: - prefork
    +
    top

    MaxSpareServers Directive

    Description: + Maximum number of idle child server processes
    Syntax: + MaxSpareServers number
    Default: + MaxSpareServers 10
    Context: + server config
    Status: + MPM
    Module: + prefork

    The MaxSpareServers directive sets the desired maximum number of idle child server processes. An idle process is one which is not handling a request. If there are @@ -113,13 +115,13 @@ accepting requests on network socketsMinSpareServers

  • StartServers

    • MinSpareServers Directive

    Description: - Minimum number of idle child server processes
    Syntax: - MinSpareServers number
    Default: - MinSpareServers 5
    Context: - server config
    Status: - MPM
    Module: - prefork
    +

    See also

    top

    MinSpareServers Directive

    Description: + Minimum number of idle child server processes
    Syntax: + MinSpareServers number
    Default: + MinSpareServers 5
    Context: + server config
    Status: + MPM
    Module: + prefork

    The MinSpareServers directive sets the desired minimum number of idle child server processes. An idle process is one which is not handling a request. If there are @@ -129,4 +131,4 @@ accepting requests on network socketsMaxSpareServers

  • StartServers

    • Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file +

    See also

    \ No newline at end of file diff --git a/docs/manual/mod/prefork.html.ja.jis b/docs/manual/mod/prefork.html.ja.jis index e7cc6926ea..f030a2ce33 100644 --- a/docs/manual/mod/prefork.html.ja.jis +++ b/docs/manual/mod/prefork.html.ja.jis @@ -1,30 +1,32 @@ -prefork - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B prefork

    $B@bL@(B: - $B%9%l%C%I$r;H$o$:!"@h9T$7$F(B fork $B$r9T$J(B$B$&%&%'%V%5!<%P$r
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<(B$B%k<1JL;R(B: - mpm_prefork_module

    $B35MW(B

    -

    $B$3$N%^%k%A%W%m%;%C%7%s%0%b(B$B%8%e!<%k(B (MPM) $B$O!"(B + -->prefork - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B prefork

    $B@bL@(B: + $B%9%l%C%I$r;H$o$:!"@h9T$7$F(B fork $B$r9T$J$&%&%'%V%5!<%P$r
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k<1JL;R(B: + mpm_prefork_module

    $B35MW(B

    +

    $B$3$N%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM) $B$O!"(B Unix $B>e$G$N(B Apache 1.3 $B$N%G%U%)%k%H$N5sF0$HHs>o$K$h$/;w$?J}K!$G(B $B%j%/%(%9%H$r=hM}$9$k!"%9%l%C%I$r;H$o$:!"@h9T$7$F(B fork $B$r9T$J$&(B $B%&%'%V%5!<%P$r$N%j%/%(%9%H$K1F6A$7$J$$$h$&$K!"(B $B8D!9$N%j%/%(%9%H$rC1N%$9$k$N$K$b!":GE,$J(B MPM $B$G$9!#(B

    $B$3$N(B MPM $B$OHs>o$K<+N'E*$J$N$G!"$3$N(B MPM $B$N@_Dj%G%#%l%/%F%#%V$r(B $BD4@0$9$kI,MW$O$[$H$s$I$J$$$G$7$g$&!#$b$C$H$b=EMW$J$3$H$O!"(B - MaxClients + MaxClients $B$,!"M=A[$5$l$kF1;~%j%/%(%9%H?t$r==J,07$($k$0$i$$$OBg$-$$$1$l$I$b!"(B - $BA4%W%m%;%9$K==J,$JJ*M}%a%b%j$,3N.$5$$CM$K$9$k!"(B + $BA4%W%m%;%9$K==J,$JJ*M}%a%b%j$,3N.$5$$CM$K$9$k!"(B $B$H$$$&$3$H$G$9!#(B

    -

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    $BF0:nJ}K!(B

    +
    top

    $BF0:nJ}K!(B

    $B0l$D$N%3%s%H%m!<%k%W%m%;%9$,!"(B $B%3%M%/%7%g%s$KBP$7$F(B listen $B$7$F!"$7$+$k$Y$-;~$K1~Ez$9$k(B $B;R%W%m%;%9$r5/F0$7$^$9!#(BApache $B$O>o$K4v$D$+$N(B$B%9%Z%"(B @@ -36,19 +38,19 @@

    $B?F%W%m%;%9$,%j%/%(%9%H$K1~Ez$9$k$N;R%W%m%;%9$r(B $B$I$N$h$&$K@8@.$9$k$+$O!"(B - StartServers, - MinSpareServers, - MaxSpareServers, - MaxClients + StartServers, + MinSpareServers, + MaxSpareServers, + MaxClients $B$GD4@0$7$^$9!#0lHLE*$K!"(BApache $B$OHs>o$K<+N'E*$J$N$G!"(B $BBgDq$N%5%$%H$G$O$3$l$i$N%G%#%l%/%F%#%V$r%G%U%)%k%HCM$+$iD4@0$9$k(B $BI,MW$O$J$$$G$7$g$&!#(B $BF1;~$K(B 256 $B$rD6$($k%j%/%(%9%H$K1~Ez$7$J$$$H$$$1$J$$%5%$%H$G$O!"(B - MaxClients + MaxClients $B$rA}$d$9I,MW$,$"$k$G$7$g$&!#(B $B0lJ}!"%a%b%j$N8B$i$l$F$$$k%5%$%H$G$O!"%9%i%C%7%s%0(B ($B%a%b%j$H%G%#%9%/4V$G2?EY$b%9%o%C%W(B) $B$,5/$3$k$N$rKI$0$?$a$K(B - MaxClients + MaxClients $B$r8:$i$9I,MW$,$"$k$G$7$g$&!#%W%m%;%9@8@.$N%A%e!<%K%s%0$K4X$9$k(B $B>\$7$$>pJs$O!"(B$B@-G=$K4X$9$k%R%s%H(B $B$K$"$j$^$9!#(B

    @@ -56,25 +58,25 @@

    $BDL>o(B Unix $B$G$O?F%W%m%;%9$O(B 80 $BHV%]!<%H$K%P%$%s%I$9$k$?$a$K(B root $B$G5/F0$5$l$^$9$,!";R%W%m%;%9$d%9%l%C%I$O(B $B$b$C$HDc$$8"8B$N%f!<%6$G(B Apache $B$K$h$C$F5/F0$5$l$^$9!#(B - User $B$H(B - Group + User $B$H(B + Group $B%G%#%l%/%F%#%V$O(B Apache $B$N;R%W%m%;%9$N8"8B$r@_Dj$9$k$N$KMQ$$$i$l$^$9!#(B $B;R%W%m%;%9$O%/%i%$%"%s%H$KAw$k%3%s%F%s%DA4$F$rFI$a$J$$$H$$$1$^$;$s$,!"(B $B2DG=$J8B$jI,MW:G>.8B$N8"8B$N$_$r;}$C$F$$$k$h$&$K$9$k$Y$-$G$9!#(B

    -

    MaxRequestsPerChild - $B$O!"8E$$%W%m%;%9$rDd;_$7$F?7$7$$%W%m%;%9(B$B$r5/F0$9$k$3$H$K$h$C$F!"(B +

    MaxRequestsPerChild + $B$O!"8E$$%W%m%;%9$rDd;_$7$F?7$7$$%W%m%;%9$r5/F0$9$k$3$H$K$h$C$F!"(B $B$I$NDxEY$NIQEY$G%5!<%P$,%W%m%;%9$r%j%5%$%/%k$9$k$+$r@)8f$7$^$9!#(B

    -

    AcceptMutex $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $BJ#?t$N;R%W%m%;%9$,%M%C%H%o!<%/%=%1%C%H$G%j%/%(%9%H$r(B +
    top

    AcceptMutex $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $BJ#?t$N;R%W%m%;%9$,%M%C%H%o!<%/%=%1%C%H$G%j%/%(%9%H$r(B accept $B$7$h$&$H$7$F$$$k$H$-$K!"(BApache $B$,$=$l$i$N;R%W%m%;%9$rD>Ns2=$9$k$?$a$K(B -$B;H$&J}K!(B
    $B9=J8(B: - AcceptMutex default|method
    $B%G%U%)%k%H(B: - AcceptMutex default
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - prefork
    +$B;H$&J}K!(B
    $B9=J8(B: + AcceptMutex default|method
    $B%G%U%)%k%H(B: + AcceptMutex default
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + prefork

    AcceptMutex $B%G%#%l%/%F%#%V$O!"(B $B%M%C%H%o!<%/%=%1%C%H$N%j%/%(%9%H$r(B accept $B$7$h$&$H$7$F$$$kJ#?t$N;R%W%m%;%9$r(B Apache $B$,D>Ns2=$9$k$?$a$K;H$&J}K!$r@_Dj$7$^$9!#(B @@ -95,13 +97,13 @@ accept $B$7$h$&$H$7$F$$$k$H$-$K!"(BApache $B$,$=$l$i$N;R%W%m%;%9$rD>Ns2=$9$k$

    flock
    -
    LockFile +
    LockFile $B%G%#%l%/%F%#%V$GDj5A$7$?%U%!%$%k$N%m%C%/$K!"(B flock(2) $B%7%9%F%`%3!<%k$r;H$$$^$9!#(B
    fcntl
    -
    LockFile +
    LockFile $B%G%#%l%/%F%#%V$GDj5A$7$?%U%!%$%k$N%m%C%/$K!"(B fnctl(2) $B%7%9%F%`%3!<%k$r;H$$$^$9!#(B
    @@ -114,13 +116,13 @@ accept $B$7$h$&$H$7$F$$$k$H$-$K!"(BApache $B$,$=$l$i$N;R%W%m%;%9$rD>Ns2=$9$k$
    POSIX Threads (PThreads) $B5,3J$G=hM}$r;H$$$^$9!#(B
    -

    MaxSpareServers $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%"%$%I%k$J;R%5!<%P%W%m%;%9$N:GBg8D?t(B
    $B9=J8(B: - MaxSpareServers number
    $B%G%U%)%k%H(B: - MaxSpareServers 10
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - prefork
    +
    top

    MaxSpareServers $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%"%$%I%k$J;R%5!<%P%W%m%;%9$N:GBg8D?t(B
    $B9=J8(B: + MaxSpareServers number
    $B%G%U%)%k%H(B: + MaxSpareServers 10
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + prefork

    MaxSpareServers $B%G%#%l%/%F%#%V$O!"(B $B%"%$%I%k$J(B$B;R%5!<%P%W%m%;%9$N4uK>:GBg8D?t$r@_Dj$7$^$9!#(B $B%"%$%I%k%W%m%;%9$H$O!"%j%/%(%9%H$r07$C$F$$$J$$%W%m%;%9$G$9!#(B @@ -129,13 +131,13 @@ accept $B$7$h$&$H$7$F$$$k$H$-$K!"(BApache $B$,$=$l$i$N;R%W%m%;%9$rD>Ns2=$9$k$

    $BHs>o$K:.$s$G$$$k%5%$%H$G$N$_!"$3$N%Q%i%a!<%?$r%A%e!<%K%s%0$9$k$Y$-$G$9!#(B $B$3$N%Q%i%a!<%?$rBg$-$/$9$k$H$$$&$3$H$O!"BgDq$N>l9g$O0-$$H/A[$G$9!#(B

    -

    $B;2>H(B

    MinSpareServers $B%G%#%l%/%F%#%V(B

    $B@bL@(B: - $B%"%$%I%k$J;R%5!<%P%W%m%;%9$N:G>.8D?t(B
    $B9=J8(B: - MinSpareServers number
    $B%G%U%)%k%H(B: - MinSpareServers 5
    $B%3%s%F%-%9%H(B: - $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<%k(B: - prefork
    +

    $B;2>H(B

    top

    MinSpareServers $B%G%#%l%/%F%#%V(B

    $B@bL@(B: + $B%"%$%I%k$J;R%5!<%P%W%m%;%9$N:G>.8D?t(B
    $B9=J8(B: + MinSpareServers number
    $B%G%U%)%k%H(B: + MinSpareServers 5
    $B%3%s%F%-%9%H(B: + $B%5!<%P@_Dj%U%!%$%k(B
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k(B: + prefork

    MaxSpareServers $B%G%#%l%/%F%#%V$O!"(B $B%"%$%I%k$J(B$B;R%5!<%P%W%m%;%9$N4uK>:G>.8D?t$r@_Dj$7$^$9!#(B $B%"%$%I%k%W%m%;%9$H$O!"%j%/%(%9%H$r07$C$F$$$J$$%W%m%;%9$G$9!#(B @@ -144,4 +146,4 @@ accept $B$7$h$&$H$7$F$$$k$H$-$K!"(BApache $B$,$=$l$i$N;R%W%m%;%9$rD>Ns2=$9$k$

    $BHs>o$K:.$s$G$$$k%5%$%H$G$N$_!"$3$N%Q%i%a!<%?$r%A%e!<%K%s%0$9$k$Y$-$G$9!#(B $B$3$N%Q%i%a!<%?$rBg$-$/$9$k$H$$$&$3$H$O!"BgDq$N>l9g$O0-$$H/A[$G$9!#(B

    -

    $B;2>H(B

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file +

    $B;2>H(B

    \ No newline at end of file diff --git a/docs/manual/mod/worker.html.en b/docs/manual/mod/worker.html.en index c3203a28c4..c323ff4936 100644 --- a/docs/manual/mod/worker.html.en +++ b/docs/manual/mod/worker.html.en @@ -1,12 +1,14 @@ -worker - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module worker

    Description: - Multi-Processing Module implementing a hybrid - multi-threaded multi-process web server
    Status: - MPM
    Module Identifier: - mpm_worker_module

    Summary

    + -->worker - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache Module worker

    Description: + Multi-Processing Module implementing a hybrid + multi-threaded multi-process web server
    Status: + MPM
    Module Identifier: + mpm_worker_module

    Summary

    This Multi-Processing Module (MPM) implements a hybrid multi-process multi-threaded server. By using threads to serve requests, it is able to serve a large number of requests with @@ -15,21 +17,21 @@ keeping multiple processes available, each with many threads.

    The most important directives used to control this MPM are - ThreadsPerChild, which + ThreadsPerChild, which controls the number of threads deployed by each child process and - MaxClients, which + MaxClients, which controls the maximum total number of threads that may be launched.

    -

    Directives

    See also

    How it Works

    +
    top

    How it Works

    Each process has a fixed number of threads. The server adjusts to handle load by increasing or decreasing the number of processes.

    A single control process is responsible for launching child processes. Each child process creates a fixed number of threads as - specified in the ThreadsPerChild directive. The + specified in the ThreadsPerChild directive. The individual threads then listen for connections and serve them when they arrive.

    @@ -38,34 +40,34 @@ requests. In this way, clients do not need to wait for a new threads or processes to be created before their requests can be served. The number of processes that will initially launched is - set by the StartServers + set by the StartServers directive. Then during operation, Apache assesses the total number of idle threads in all processes, and forks or kills processes to - keep this number within the boundaries specified by MinSpareThreads and MaxSpareThreads. Since this + keep this number within the boundaries specified by MinSpareThreads and MaxSpareThreads. Since this process is very self-regulating, it is rarely necessary to modify these directives from their default values. The maximum number of clients that may be served simultaneously (i.e., the maximum total number of threads in all processes) is determined by the - MaxClients directive, + MaxClients directive, while the maximum number of processes that can be launched is set - by the ServerLimit - directive. ServerLimit - multiplied by ThreadsPerChild must be greater - than or equal to MaxClients

    + by the ServerLimit + directive. ServerLimit + multiplied by ThreadsPerChild must be greater + than or equal to MaxClients

    A typical configuration of the process-thread controls in - the worker MPM could look as follows:

    + the worker MPM could look as follows:

    -
    StartServers         2
+
    StartServers         2
 MaxClients         150
 MinSpareThreads     25
 MaxSpareThreads     75
 ThreadsPerChild     25
-ServerLimit         16
    +ServerLimit 16

    While the parent process is usually started as root under Unix in order to bind to port 80, the child processes and threads are - launched by Apache as a less-privileged user. The User and Group directives are used to set + launched by Apache as a less-privileged user. The User and Group directives are used to set the privileges of the Apache child processes. The child processes must be able to read all the content that will be served, but should have as few privileges beyond that as possible. In @@ -73,7 +75,7 @@ ServerLimit 16

    these directives also set the privileges which will be inherited by CGI scripts.

    -

    MaxRequestsPerChild +

    MaxRequestsPerChild controls how frequently the server recycles processes by killing old ones and launching new ones.

    -

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file + \ No newline at end of file diff --git a/docs/manual/mod/worker.html.ja.jis b/docs/manual/mod/worker.html.ja.jis index d997fe665d..9acbc2e4f5 100644 --- a/docs/manual/mod/worker.html.ja.jis +++ b/docs/manual/mod/worker.html.ja.jis @@ -1,36 +1,38 @@ -worker - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache $B%b%8%e!<%k(B worker

    $B@bL@(B: - $B%^%k%A%9%l%C%I$H%^%k%A%W%m%;%9$N%O%$%V%j%C%I7?(B -$B%&%'%V%5!<%P$r
    $B%9%F!<%?%9(B: - MPM
    $B%b%8%e!<(B$B%k<1JL;R(B: - mpm_worker_module

    $B35MW(B

    + -->worker - Apache HTTP Server

    Modules | Directives | FAQ | Glossary | Sitemap

    Apache HTTP Server Version 2.0

    <-

    Apache $B%b%8%e!<%k(B worker

    $B@bL@(B: + $B%^%k%A%9%l%C%I$H%^%k%A%W%m%;%9$N%O%$%V%j%C%I7?(B +$B%&%'%V%5!<%P$r
    $B%9%F!<%?%9(B: + MPM
    $B%b%8%e!<%k<1JL;R(B: + mpm_worker_module

    $B35MW(B

    $B$3$N%^%k%A%W%m%;%C%7%s%0%b%8%e!<%k(B (MPM) - $B$O!"%^(B$B%k%A%9%l%C%I$H%^%k%A%W%m%;%9$N%O%$%V%j%C%I7?%5!<%P$r(B + $B$O!"%^%k%A%9%l%C%I$H%^%k%A%W%m%;%9$N%O%$%V%j%C%I7?%5!<%P$r(B $B/$J$$%7%9%F%`;q8;$G!"(B $BB?$/$N%j%/%(%9%H$K1~Ez$9$k$3$H$,$G$-$^$9!#(B - $B$5$i$K!"B?$/$N%9%l%C(B$B%I$r;}$C$?J#?t$N%W%m%;%9$r0];}$9$k$3$H$G!"(B + $B$5$i$K!"B?$/$N%9%l%C%I$r;}$C$?J#?t$N%W%m%;%9$r0];}$9$k$3$H$G!"(B $B%W%m%;%9%Y!<%9$N%5!<%P$N;}$D0BDj@-$rJ];}$7$F$$$^$9!#(B

    $B$3$N(B MPM $B$r@)8f$9$k$N$K;H$o$l$k:G$b=EMW$J%G%#%l%/%F%#%V$O!"(B - ThreadsPerChild $B$H(B - MaxClients $B$G$9!#(B - ThreadsPerChild $B$O(B + ThreadsPerChild $B$H(B + MaxClients $B$G$9!#(B + ThreadsPerChild $B$O(B $B3F;R%W%m%;%9$GMQ0U$5$l$k%9%l%C%I?t$r@)8f$7$F!"(B - MaxClients $B$O(B + MaxClients $B$O(B $B5/F0$5$l$k%9%l%C%I$NAm?t$N:GBgCM$r@)8B$7$^$9!#(B

    -

    $B%G%#%l%/%F%#%V(B

    $B;2>H(B

    $BF0(B$B:nJ}K!(B

    +
    top

    $BF0:nJ}K!(B

    $B%W%m%;%9$O7h$^$C$??t$N%9%l%C%I$r;}$A$^$9!#(B $BIi2Y$X$NE,1~$O%W%m%;%9$N?t$rA}8:$K$h$jBP1~$7$^$9!#(B

    $B0l$D$N@)8fMQ%W%m%;%9$,;R%W%m%;%9$r5/F0$7$^$9!#(B $B;R%W%m%;%9$O(B - ThreadsPerChild + ThreadsPerChild $B%G%#%l%/%F%#%V$G;XDj$5$l$?0lDj?t$N%9%l%C%I$r:n$j$^$9!#(B $B$=$l$+$i!"8D!9$N%9%l%C%I$,%3%M%/%7%g%s$KBP$7$F(B listen $B$7$F!"$7$+$k$Y$-;~$KF0:n$7$^$9!#(B

    @@ -42,42 +44,42 @@ $B?7$7$$%9%l%C%I$d%W%m%;%9$,@8@.$5$l$k$N$r(B $BBT$?$J$/$F$b$h$$$h$&$K$J$C$F$$$^$9!#(B $B5/F0=i4|;~$N%W%m%;%9Am?t$O!"(B - StartServers + StartServers $B%G%#%l%/%F%#%V$G@_Dj$5$l$^$9!#$=$N8e$N2TF/Cf$K!"(B Apache $B$OA4%W%m%;%9$N%"%$%I%k%9%l%C%I$N9g7W?t$r8+@Q$b$C$F!"(B - MinSpareThreads $B$H(B - MaxSpareThreads + MinSpareThreads $B$H(B + MaxSpareThreads $B$G;XDj$5$l$?HO0O$NCf$K$3$N?t$,<}$^$k$h$&$K(B fork $B$7$?$j(B kill $B$7$?$j$7$^$9!#$3$NA`:n$OHs>o$K<+N'E*$J$N$G!"(B $B$3$l$i$N%G%#%l%/%F%#%V$r%G%U%)%k%HCM$+$iJQ99$9$kI,MW$O(B $B$a$C$?$K$J$$$G$7$g$&!#(B $BF1;~$K1~Ez$9$k$3$H$N$G$-$k%/%i%$%"%s%H?t$N:GBg?t(B ($B$D$^$jA4%W%m%;%9Cf$NAm%9%l%C%I?t$N:GBgCM(B) $B$O(B - MaxClients + MaxClients $B%G%#%l%/%F%#%V$G7hDj$5$l$F$$$F!"(B $B0lJ}$G5/F0$9$k$3$H$N$G$-$k%W%m%;%9?t$N:GBgCM$O(B - ServerLimit + ServerLimit $B%G%#%l%/%F%#%V$G@_Dj$5$l$F$$$^$9!#(B - ServerLimit $B$H(B - ThreadsPerChild $B$H$N@Q$O!"(B - MaxClients + ServerLimit $B$H(B + ThreadsPerChild $B$H$N@Q$O!"(B + MaxClients $B$HEy$7$$$+$=$l$h$jBg$-$$I,MW$,$"$j$^$9!#(B

    -

    worker MPM $B$NE57?E*$J%W%m%;%9!&%9%l%C%I@)8f$N(B +

    worker MPM $B$NE57?E*$J%W%m%;%9!&%9%l%C%I@)8f$N(B $B@_Dj$G$O!" -

    StartServers         2
+
    StartServers         2
 MaxClients         150
 MinSpareThreads     25
 MaxSpareThreads     75
 ThreadsPerChild     25
-ServerLimit         16
    +ServerLimit 16

    $BDL>o(B Unix $B$G$O?F%W%m%;%9$O(B 80 $BHV%]!<%H$K%P%$%s%I$9$k$?$a$K(B root $B$G5/F0$5$l$^$9$,!";R%W%m%;%9$d%9%l%C%I$O(B $B$b$C$HDc$$8"8B$N%f!<%6$G(B Apache $B$K$h$C$F5/F0$5$l$^$9!#(B - User $B$H(B - Group $B%G%#%l%/%F%#%V$O(B + User $B$H(B + Group $B%G%#%l%/%F%#%V$O(B Apache $B$N;R%W%m%;%9$N8"8B$r@_Dj$9$k$N$KMQ$$$i$l$^$9!#(B $B;R%W%m%;%9$O%/%i%$%"%s%H$KAw$k%3%s%F%s%DA4$F$rFI$a$J$$$H$$$1$^$;$s$,!"(B $B2DG=$J8B$jI,MW:G>.8B$N8"8B$N$_$r;}$C$F$$$k$h$&$K$9$k$Y$-$G$9!#(B @@ -85,7 +87,7 @@ ServerLimit 16

    $B$,;HMQ$5$l$F$$$J$$8B$j!"$3$l$i$N%G%#%l%/%F%#%V$O(B CGI $B%9%/%j%W%H$G7Q>5$5$l$k8"8B$b@_Dj$7$^$9!#(B

    -

    MaxRequestsPerChild +

    MaxRequestsPerChild $B$O!"8E$$%W%m%;%9$rDd;_$7$F?7$7$$%W%m%;%9$r5/F0$9$k$3$H$K$h$C$F!"(B $B$I$NDxEY$NIQEY$G%5!<%P$,%W%m%;%9$r%j%5%$%/%k$9$k$+$r@)8f$7$^$9!#(B

    -

    Apache HTTP Server Version 2.0

    $B:w(B$B0z(B$B%[(B$B!<(B$B%`(B \ No newline at end of file + \ No newline at end of file -- 2.50.1