From 371ae890fb929c902c4fb54e96d6228b6a2006f7 Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Fri, 8 Mar 2002 17:19:23 +0000 Subject: [PATCH] Update the html tranformations. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93793 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html | 59 +++--- docs/manual/mod/mod_autoindex.html | 80 ++++---- docs/manual/mod/mod_charset_lite.html | 8 +- docs/manual/mod/mod_example.html | 134 ++++--------- docs/manual/mod/mod_ext_filter.html | 157 +++++---------- docs/manual/mod/mod_file_cache.html | 248 +++++++++--------------- docs/manual/mod/mod_headers.html | 261 +++++++++---------------- docs/manual/mod/mod_imap.html | 265 +++++++++----------------- docs/manual/mod/mod_speling.html | 15 +- docs/manual/mod/mod_status.html | 20 +- docs/manual/mod/mod_suexec.html | 4 +- docs/manual/mod/mod_unique_id.html | 4 +- docs/manual/mod/mod_userdir.html | 4 +- docs/manual/mod/mod_vhost_alias.html | 13 +- 14 files changed, 442 insertions(+), 830 deletions(-) diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index 421a2c8798..a0589ee581 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -184,7 +184,7 @@ authenticationAuthentication, Authorization, and - Access Control

AuthType Directive

Description: Selects the type of user authentication
Syntax:AuthType Basic|Digest
Context:directory, .htaccess
Status:Core
Module:core
+ Access Control

AuthType Directive

Description: Selects the 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. @@ -234,8 +234,8 @@ server cannot determine a type in any other way DefaultType image/gif - would be appropriate for a directory which contained many gif - images with filenames missing the .gif extension. +

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 provides the default mime-type. All other mime-type definitions, @@ -267,8 +267,8 @@ named file-system directory and sub-directories <Directory ~ "^/www/.*/[0-9]{3}"> - would match directories in /www/ that consisted of three - numbers. +

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

If multiple (non-regular expression) directory sections match the directory (or its parents) containing a document, @@ -315,7 +315,7 @@ named file-system directory and sub-directories -

-
INode
+
+
INode
The file's i-node number will be included in the calculation
-
MTime
+
MTime
The date and time the file was last modified will be included
-
Size
+
Size
The number of bytes in the file will be included
-
All
+
All
All available fields will be used (equivalent to 'FileETag INode MTime Size')
-
None
+
None
If a document is file-based, no ETag field will be included in the response
@@ -987,16 +987,16 @@ matching URLs
- Level + Level - Description + Description - Example + Example @@ -1480,16 +1480,16 @@ is accessed by an incompatible browserServerName of the serving virtual host, - and the EMail setting additionally creates a + and the EMail setting additionally creates a "mailto:" reference to the ServerAdmin of the referenced document.


ServerTokens Directive

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

This directive controls whether Server response +

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 information about compiled-in modules.

@@ -1497,23 +1497,23 @@ is accessed by an incompatible browserA fully qualified domain name for the IP address of the virtual host. - Example: + -
<VirtualHost 10.1.2.3>
+

Example

+ <VirtualHost 10.1.2.3>
ServerAdmin webmaster@host.foo.com
DocumentRoot /www/docs/host.foo.com
ServerName host.foo.com
diff --git a/docs/manual/mod/mod_autoindex.html b/docs/manual/mod/mod_autoindex.html index 071ef64803..79bc5ff9f7 100644 --- a/docs/manual/mod/mod_autoindex.html +++ b/docs/manual/mod/mod_autoindex.html @@ -39,7 +39,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX same header repeatedly toggles between ascending and descending order. These column header links are suppressed with IndexOptions directive's - SuppressColumnSorting option.

+ SuppressColumnSorting option.

Note that when the display is sorted by "Size", it's the actual size of the files that's used, not the @@ -60,41 +60,41 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX resource.

    -
  • C=N sorts the directory by file name
  • +
  • C=N sorts the directory by file name
  • -
  • C=M sorts the directory by last-modified +
  • C=M sorts the directory by last-modified date, then file name
  • -
  • C=S sorts the directory by size, then file +
  • C=S sorts the directory by size, then file name
  • -
  • C=D sorts the directory by description, then +
  • C=D sorts the directory by description, then file name
     
  • -
  • O=A sorts the listing in Ascending +
  • O=A sorts the listing in Ascending Order
  • -
  • O=D sorts the listing in Descending +
  • O=D sorts the listing in Descending Order
     
  • -
  • F=0 formats the listing as a simple list +
  • F=0 formats the listing as a simple list (not FancyIndexed)
  • -
  • F=1 formats the listing as a FancyIndexed +
  • F=1 formats the listing as a FancyIndexed list
  • -
  • F=2 formats the listing as an HTMLTable +
  • F=2 formats the listing as an HTMLTable FancyIndexed list
     
  • -
  • V=0 disables version sorting
  • +
  • V=0 disables version sorting
  • -
  • V=1 enables version sorting
    +
  • V=1 enables version sorting
     
  • -
  • P=pattern lists only files matching +
  • P=pattern lists only files matching the given pattern
@@ -324,7 +324,7 @@ indexing
Synt of

-
DescriptionWidth=[n +
DescriptionWidth=[n | *] (Apache 1.3.10 or 2.0.23 and later)
The DescriptionWidth keyword allows you to @@ -341,19 +341,19 @@ indexing
Synt width necessary to accommodate the longest description string. -
See the section on AddDescription for dangers - inherent in truncating descriptions.
+
See the section on AddDescription for dangers + inherent in truncating descriptions.
-
FancyIndexing
+
FancyIndexing
This turns on fancy indexing of directories.
-
FoldersFirst (Apache - 1.3.10 or 2.0.23 and later)
+
FoldersFirst (Apache + 1.3.10 or 2.0.23 and later)
If this option is enabled, subdirectory listings will - always appear first, followed by normal files in the + always appear first, followed by normal files in the directory. The listing is basically broken into two components, the files and the subdirectories, and each is sorted separately and then displayed subdirectories-first. @@ -361,12 +361,12 @@ indexing
Synt FoldersFirst is enabled, subdirectory Zed will be listed before subdirectory Beta, which will be listed before normal files - Gamma and Alpha. This option + Gamma and Alpha. This option only has an effect if FancyIndexing - is also enabled. + is also enabled. -
HTMLTable (Experimental, - Apache 2.0.23 and later)
+
HTMLTable (Experimental, + Apache 2.0.23 and later)
This experimental option with FancyIndexing constructs a @@ -376,13 +376,13 @@ indexing
Synt left-to-right and right-to-left reading order, as can happen on WinNT or other utf-8 enabled platforms. -
IconsAreLinks
+
IconsAreLinks
This makes the icons part of the anchor for the filename, for fancy indexing.
-
IconHeight[=pixels] +
IconHeight[=pixels] (Apache 1.3 and later)
@@ -395,7 +395,7 @@ indexing
Synt the standard height of the icons supplied with the Apache software. -
IconWidth[=pixels] (Apache +
IconWidth[=pixels] (Apache 1.3 and later)
@@ -408,14 +408,14 @@ indexing
Synt the standard width of the icons supplied with the Apache software. -
IgnoreClient
+
IgnoreClient
This option causes mod_autoindex to ignore all query variables from the client, including sort order (implies SuppressColumnSorting.)
-
NameWidth=[n | *] +
NameWidth=[n | *] (Apache 1.3.2 and later)
The NameWidth keyword allows you to specify the width of @@ -430,7 +430,7 @@ indexing
Synt
NameWidth=* grows the column to the necessary width.
-
ScanHTMLTitles
+
ScanHTMLTitles
This enables the extraction of the title from HTML documents @@ -439,7 +439,7 @@ indexing
Synt httpd will read the document for the value of the TITLE tag. This is CPU and disk intensive. -
SuppressColumnSorting +
SuppressColumnSorting (Apache 1.3 and later)
@@ -452,7 +452,7 @@ indexing
Synt string. That behavior is now controlled by IndexOptions IgnoreClient in Apache 2.0.23. -
SuppressDescription
+
SuppressDescription
This will suppress the file description in fancy indexing @@ -464,7 +464,7 @@ indexing
Synt index option to limit the size of the description column. -
SuppressHTMLPreamble +
SuppressHTMLPreamble (Apache 1.3 and later)
@@ -478,7 +478,7 @@ indexing
Synt HTML instructions in this case. If there is no header file, the preamble is generated as usual. -
SuppressIcon (Apache +
SuppressIcon (Apache 2.0.23 and later)
@@ -488,13 +488,13 @@ indexing
Synt by the final specification prohibits IMG and HR tags from the PRE block (used to format FancyIndexed listings.) -
SuppressLastModified
+
SuppressLastModified
This will suppress the display of the last modification date, in fancy indexing listings.
-
SuppressRules +
SuppressRules (Apache 2.0.23 and later)
@@ -504,13 +504,13 @@ indexing
Synt by the final specification prohibits IMG and HR tags from the PRE block (used to format FancyIndexed listings.) -
SuppressSize
+
SuppressSize
This will suppress the file size in fancy indexing listings.
-
TrackModified (Apache +
TrackModified (Apache 1.3.15 or 2.0.23 and later)
@@ -528,7 +528,7 @@ indexing
Synt Last-Modified header on all Unix platforms. If this is a concern, leave this option disabled. -
VersionSort (Apache 2.0a3 +
VersionSort (Apache 2.0a3 and later)
@@ -558,7 +558,7 @@ foo-1.04
-

Incremental IndexOptions

+ Incremental IndexOptions
diff --git a/docs/manual/mod/mod_charset_lite.html b/docs/manual/mod/mod_charset_lite.html index c0e203ec12..a816db9106 100644 --- a/docs/manual/mod/mod_charset_lite.html +++ b/docs/manual/mod/mod_charset_lite.html @@ -66,8 +66,8 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX as a valid character set name by the character set support in APR. Generally, this means that it must be supported by iconv.

- Example: -
+ +

Example

<Directory "/export/home/trawick/apacheinst/htdocs/convert">
CharsetSourceEnc UTF-16BE
CharsetDefault ISO8859-1
@@ -110,8 +110,8 @@ NoImplicitAdd
- Example: -
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

+ +
variable FOOBAR.

example

<Directory "/export/home/trawick/apacheinst/htdocs/convert">
CharsetSourceEnc UTF-16BE
CharsetDefault ISO8859-1
diff --git a/docs/manual/mod/mod_example.html b/docs/manual/mod/mod_example.html index 96ca75f6ad..fab7e678f8 100644 --- a/docs/manual/mod/mod_example.html +++ b/docs/manual/mod/mod_example.html @@ -1,45 +1,14 @@ - - - - - - - Apache module mod_example - - - - - - -
- Warning: This document has not been updated +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

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

Module mod_example

- -

This module illustrates many of the aspects of the Apache 1.2 API and, when - used, demonstrates the manner in which module callbacks are - triggered by the server.

- -

Status: Extension
- Source File: - mod_example.c
- Module Identifier: - example_module
- Compatibility: Available in - Apache 1.2 and later.

- -

Summary

+

The files in the src/modules/example directory under the Apache distribution directory tree are provided as an @@ -56,17 +25,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

Compiling the example module

To include the example module in your server, follow the steps below:

@@ -76,90 +35,61 @@ 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.
  • -
  • Make the server (run "make" in the +
  • Make the server (run "make" in the src directory).
  • To add another module of your own:

      -
    1. mkdir src/modules/mymodule
    2. +
    3. mkdir src/modules/mymodule
    4. -
    5. cp src/modules/example/* - src/modules/mymodule
    6. +
    7. cp src/modules/example/* + src/modules/mymodule
    8. Modify the files in the new directory.
    9. Follow steps [1] through [3] above, with appropriate changes.
    - -

    Using the mod_example Module

    +

    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
    +    the following in your srm.conf file:

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

    -
    +    

    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

    - -

    Syntax: Example
    - Default: None
    - Context: server config, virtual - host, directory, .htaccess
    - Override: Options
    - Status: Extension
    - Module: mod_example
    - Compatibility: - Example is only available in Apache 1.2 and - later.

    - -

    The Example directive just sets a demonstration +


    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 example content-handler applies, you will get a display of the routines within the module and how and in what order they were called to service the document request. The effect of this - directive one can observe under the point "Example - directive declared here: YES/NO".

    - - - - + directive one can observe under the point "Example + directive declared here: YES/NO".

    +

    Apache HTTP Server Version 2.0

    IndexHome
    \ No newline at end of file diff --git a/docs/manual/mod/mod_ext_filter.html b/docs/manual/mod/mod_ext_filter.html index 4bc76ab588..2f8daede6e 100644 --- a/docs/manual/mod/mod_ext_filter.html +++ b/docs/manual/mod/mod_ext_filter.html @@ -1,43 +1,18 @@ - - - - - - - Apache module mod_ext_filter - - - - - - -

    Module mod_ext_filter

    - -

    This module provides the ability to pass the response body +mod_ext_filter - Apache HTTP Server

    [APACHE DOCUMENTATION]

    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
    - Source File: - mod_ext_filter.c
    - 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 @@ -59,18 +34,10 @@

    Even when the performance characteristics are not suitable for production use, mod_ext_filter can be used as a prototype environment for filters.

    +

    Directives

    Examples

    -

    Directives

    - - - -

    Examples

    - -

    Generating HTML from some other type of response

    +

    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 
    @@ -92,10 +59,12 @@
         ExtFilterOptions DebugLevel=1
     
         </Directory>
    - 
     
    +
    + -

    Implementing a content encoding filter

    +

    Implementing a content encoding filter

    +
       # mod_ext_filter directive to define the external filter
       ExtFilterDefine gzip mode=output cmd=/bin/gzip
    @@ -109,14 +78,16 @@
       Header set Content-Encoding gzip
     
       </Location>
    - 
     
    +
    -

    Note: this gzip example is just for the purposes of - illustration. Please refer to - mod_deflate for a practical implementation.

    +

    Note: this gzip example is just for the purposes of illustration. + Please refer to mod_deflate for a practical + implementation.

    -

    Slowing down the server

    + +

    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
    @@ -130,28 +101,12 @@
       SetOutputFilter slowdown slowdown slowdown
     
       </Location>
    - 
     
    -
    - -

    ExtFilterDefine

    - -

    Syntax: ExtFilterDefine - filtername parameters
    - Default: None
    - Context: server
    - Override: none
    - Status: Experimental
    - Module: mod_ext_filter

    - -

    The ExtFilterDefine directive defines the +

    + + +

    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.

    @@ -170,7 +125,7 @@
    cmd=cmdline
    -
    The cmd= keyword allows you to specify the +
    The cmd= keyword allows you to specify the external command to run. If there are arguments after the program name, the command line should be surrounded in quotation marks.
    @@ -199,33 +154,15 @@
    PreservesContentLength
    -
    The PreservesContentLength keyword specifies +
    The PreservesContentLength keyword specifies that the filter preserves the content length. This is not the default, as most filters change the content length. In the event that the filter doesn't modify the length, this keyword should be specified.
    -
    - -

    ExtFilterOptions

    - -

    Syntax: ExtFilterOptions - option [option] ...
    - Default: DebugLevel=0 - NoLogStderr
    - Context: directory
    - Override: none
    - Status: Experimental
    - Module: mod_ext_filter

    - -

    The ExtFilterOptions directive specifies +


    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

    @@ -233,11 +170,11 @@
    DebugLevel=n
    - The DebugLevel keyword allows you to specify + The DebugLevel keyword allows you to specify the level of debug messages generated by mod_ext_filter. By default, no debug messages are generated. This is equivalent to - DebugLevel=0. With higher numbers, more debug + DebugLevel=0. With higher numbers, more debug messages are generated, and server performance will be degraded. The actual meanings of the numeric values are described with the definitions of the DBGLVL_ constants @@ -250,24 +187,18 @@
    LogStderr | NoLogStderr
    -
    The LogStderr keyword specifies that +
    The LogStderr keyword specifies that messages written to standard error by the external filter program will be saved in the Apache error log. - NoLogStderr disables this feature.
    + NoLogStderr disables this feature. -
    -
    - 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. -

    -

    - - +

    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 diff --git a/docs/manual/mod/mod_file_cache.html b/docs/manual/mod/mod_file_cache.html index e684f7ed71..724f33a6c4 100644 --- a/docs/manual/mod/mod_file_cache.html +++ b/docs/manual/mod/mod_file_cache.html @@ -1,23 +1,14 @@ - - - - - - - Apache module mod_file_cache - - - - - - -

    Module mod_file_cache

    - -

    This module should be used with care. You can easily +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

    + +
    +This module should be used with care. You can easily create a broken site using mod_file_cache, so read this - document carefully.

    + document carefully. +

    Caching frequently requested files that change very infrequently is a technique for reducing server load. @@ -30,18 +21,6 @@ (specifically, the file I/O) for serving the file when the server is started rather than during each request.

    -

    mod_file_cache is not compiled into the server - by default. To use mod_file_cache you have to - enable the following line in the server build - Configuration file:

    -
    -    AddModule  modules/experimental/mod_file_cache.o
    - 
    -
    -
    -
    - -

    Notice: You cannot use this for speeding up CGI programs or other files which are served by special content handlers. It can only be used for regular files which are usually served by @@ -49,39 +28,35 @@

    This module is an extension of and borrows heavily from the mod_mmap_static module in Apache 1.3.

    - -

    Summary

    - -

    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 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 server will start but the file will - not be cached. On platforms that support both directives, you - should experiment with both to see which works best for - you.

    - -

    MmapFile Directive

    - -

    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 - system-specific limits on the size and number of files that can - be mmap()d, experimentation is probably the easiest way to find +

    Directives

    Using mod_file_cache

    + +

    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 + 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 + server will start but the file will not be cached. On platforms + that support both directives, you should experiment with both to + see which works best for you.

    + +

    MmapFile Directive

    + +

    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 + system-specific limits on the size and number of files that can be + mmap()d, experimentation is probably the easiest way to find out.

    This mmap()ing is done once at server start or restart, only. So whenever one of the mapped files changes on the - filesystem you have to restart the server (see the Stopping and Restarting + filesystem you have to restart the server (see the Stopping and Restarting documentation). To reiterate that point: if the files are modified in place without restarting the server you may end up serving requests that are completely bogus. You @@ -92,15 +67,16 @@ an extra stat() every time which is a waste and against the intent of I/O reduction.

    -

    CacheFile Directive

    -

    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 retrieves the - handle from the cache and passes it to the sendfile() (or - TransmitFile() on Windows), socket API.

    +

    CacheFile Directive

    + +

    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 + retrieves the handle from the cache and passes it to the + sendfile() (or TransmitFile() on Windows), socket API.

    Insert more details about sendfile API...

    @@ -115,109 +91,57 @@ copy in place. Most tools such as rdist and mv do this.

    -

    Directives

    - - -
    - -

    MMapFile

    - -

    Syntax: MMapFile - filename [filename] ...
    - Default: None
    - Context: server-config
    - Override: Not - applicable
    - Status: Experimental
    - Module: mod_file_cache
    - Compatibility: Only in Apache - 1.3 (via mod_mmap_statis) or later.

    - -

    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 - shutdown. When the files have changed on the filesystem at - least a HUP or USR1 signal should be send to the server to - re-mmap them.

    -

    Be careful with the filename arguments: They have +

    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 + this command: +
    + 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
    +

    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 + time. Handles to cached files are automatically closed on a server + shutdown. When the files have changed on the filesystem, the + server should be restarted to to re-cache them.

    + +

    Be careful with the file-path arguments: They have to literally match the filesystem path Apache's URL-to-filename translation handlers create. We cannot compare inodes or other stuff to match paths through symbolic links etc. because that again would cost extra stat() system calls which is not acceptable. This module may or may not work - with filenames rewritten by mod_alias or - mod_rewrite.

    - Example: -
    -  MMapFile /usr/local/apache/htdocs/index.html
    - 
    -
    -
    - -

    CacheFile

    - -

    Syntax: CacheFile - filename [filename] ...
    - Default: None
    - Context: server-config
    - Override: Not - applicable
    - Status: Experimental
    - Module: mod_file_cache
    - Compatibility: Only available - in Apache 2.0 or later.

    - -

    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 time. Handles to - cached files are automatically closed on a server shutdown. - When the files have changed on the filesystem, the server - should be restarted to to re-cache them.

    - -

    Be careful with the filename arguments: They have + with filenames rewritten by mod_alias or + mod_rewrite.

    + +

    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
    +

    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 + shutdown. When the files have changed on the filesystem at + least a HUP or USR1 signal should be send to the server to + re-mmap them.

    + +

    Be careful with the file-path arguments: They have to literally match the filesystem path Apache's URL-to-filename translation handlers create. We cannot compare inodes or other stuff to match paths through symbolic links etc. because that again would cost extra stat() system calls which is not acceptable. This module may or may not work - with filenames rewritten by mod_alias or - mod_rewrite.

    - Example: -
    -  CacheFile /usr/local/apache/htdocs/index.html
    - 
    -
    - -

    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 - this command:

    -
    -  find /www/htdocs -type f -print \
    -  | sed -e 's/.*/mmapfile &/' > /www/conf/mmap.conf
    - 
    -
    - - - + with filenames rewritten by mod_alias or + mod_rewrite.

    +

    Example

    + MMapFile /usr/local/apache/htdocs/index.html +
    +

    Apache HTTP Server Version 2.0

    IndexHome
    \ No newline at end of file diff --git a/docs/manual/mod/mod_headers.html b/docs/manual/mod/mod_headers.html index fd67a3adcd..f391384bcf 100644 --- a/docs/manual/mod/mod_headers.html +++ b/docs/manual/mod/mod_headers.html @@ -1,49 +1,13 @@ - - - - - - - Apache module mod_headers - - - - - - -

    Module mod_headers

    - -

    This module provides for the customization of HTTP request - and response headers.

    - -

    Status: Extension
    - Source File: - mod_headers.c
    - Module Identifier: - headers_module
    - Compatibility: Available in - Apache 1.2 and later. RequestHeader appeared in Apache 2.0.

    - -

    Summary

    - This module provides directives to control and modify HTTP +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

    +

    This module provides directives to control and modify HTTP request and response headers. Headers can be merged, replaced - or removed. - -

    Directives

    - - - -

    Order of Processing

    + or removed.

    +

    Directives

    Order of Processing

    The directives provided by mod_header can occur almost anywhere within the server configuration. They are valid in the @@ -68,158 +32,69 @@

    Order is important. These two headers have a different effect if reversed:

    -
    - RequestHeader append MirrorID "mirror 12"
    - RequestHeader unset MirrorID
    -
    +
    +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".

    - -

    Examples

    +

    Example

    1. Copy all request headers that begin with "TS" to the - response headers:
    2. + response headers: -
    3. -
      +
      Header echo ^TS* - - +
    4. Add a header, MyHeader, to the response including a timestamp for when the request was received and how long it took to begin serving the request. This header can be used by the client to intuit load on the server or in isolating - bottlenecks between the client and the server.
    5. + bottlenecks between the client and the server. -
    6. -
      +
      Header add MyHeader "%D %t" - - results in this header being added to the response: -
      +
      + results in this header being added to the response: +
      MyHeader: D=3775428 t=991424704447256 - +
    7. -
    8. Say hello to Joe
    9. +
    10. Say hello to Joe -
    11. -
      +
      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. - +
    12. Conditionally send MyHeader on the response if and only if header "MyRequestHeader" is present on the request. This is useful for constructing headers in response to some client stimulus. Note that this example requires the services of the - mod_setenvif module.
    13. + mod_setenvif module. -
    14. -
      -   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 - +
    -
    - -

    RequestHeader directive

    - Syntax: RequestHeader - set|append|add header value
    - Syntax: RequestHeader unset - header
    - Context: server config, virtual - host, access.conf, .htaccess
    - Override: FileInfo
    - Status: Extension
    - Module: mod_header - -

    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 - performs is determined by the first argument. This can be one - of the following values:

    - -
      -
    • set
      - The request header is set, replacing any previous header - with this name
    • - -
    • 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
      - 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
      - The request header of this name is removed, if it exists. If - there are multiple headers of the same name, all will be - removed.
    • -
    - -

    This argument is followed by a header name, which can - include the final colon, but it is not required. Case is - ignored. For add, append and - set a value is given as the third argument. If - this value contains spaces, it should be surrounded by double - quotes. For unset, no value should be given.

    - -

    The RequestHeader directive is processed 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.

    -
    - -

    Header directive

    - Syntax: Header set|append|add - header value - [env=[!]environment-variable]
    - Syntax: Header unset - header
    - Syntax: Header echo - header
    - Context: server config, virtual - host, access.conf, .htaccess
    - Override: FileInfo
    - Status: Extension
    - Module: mod_header - +

    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 @@ -227,31 +102,31 @@ 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.
    • @@ -283,14 +158,13 @@ duration of the request. The value is preceded by "D=".
    -

    When the Header directive is used with the +

    When the Header directive is used with the add, append, or set argument, a fourth argument may be used to specify conditions - under which the action will be taken. If the environment variable specified in the + under which the action will be taken. If the environment variable specified in the env=... argument exists (or if the environment variable does not exist and env=!... is specified) - then the action specified by the Header directive + then the action specified by the Header directive will take effect. Otherwise, the directive will have no effect on the request.

    @@ -298,7 +172,48 @@ variable FOOBAR.
    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 + performs is determined by the first argument. This can be one + of the following values:

    + +
      +
    • set
      + The request header is set, replacing any previous header + with this name
    • + +
    • 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
      + 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
      + The request header of this name is removed, if it exists. If + there are multiple headers of the same name, all will be + removed.
    • +
    + +

    This argument is followed by a header name, which can + include the final colon, but it is not required. Case is + ignored. For add, append and + set a value is given as the third argument. If + this value contains spaces, it should be surrounded by double + quotes. For unset, no value should be given.

    +

    The RequestHeader directive is processed + 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 diff --git a/docs/manual/mod/mod_imap.html b/docs/manual/mod/mod_imap.html index a3f1dc2cd2..f84d7b9759 100644 --- a/docs/manual/mod/mod_imap.html +++ b/docs/manual/mod/mod_imap.html @@ -1,71 +1,31 @@ - - - - - - - Apache module mod_imap - - - - - - -

    Module mod_imap

    - -

    This module provides for server-side imagemap - processing.

    - -

    Status: Base
    - Source File: mod_imap.c
    - Module Identifier: - imap_module
    - Compatibility: Available in - Apache 1.1 and later.

    - -

    Summary

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

    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) + handler imap-file (using either + 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 -
    - Note that the following is still supported: +
    AddHandler imap-file map
    -
    - AddType application/x-httpd-imap map -
    - However, we are trying to phase out "magic MIME types" so we - are deprecating this method. +

    Note that the following is still supported:

    -

    Directives

    +
    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

    -

    New Features

    - The imagemap module adds some new features that were not - possible with previously distributed imagemap programs. +

    The imagemap module adds some new features that were not + possible with previously distributed imagemap programs.

    • URL references relative to the Referer: information.
    • @@ -79,29 +39,29 @@
    • Configurable generation of imagemap menus.
    +

    Imagemap File

    -

    Imagemap File

    - The lines in the imagemap files can have one of several - formats: +

    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 ... "Menu text"
    -
    - The directive is one of base, +
    + 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 absolute or relative URL, or one of the special values listed below. The coordinates are x,y pairs separated by whitespace. The quoted text is used as the text of the link if a imagemap menu is generated. Lines beginning with '#' are - comments. + comments.

    -

    Imagemap File Directives

    - There are six directives allowed in the imagemap file. The +

    Imagemap File Directives

    +

    There are six directives allowed in the imagemap file. The directives can come in any order, but are processed in the - order they are found in the imagemap file. + order they are found in the imagemap file.

    base Directive
    @@ -112,7 +72,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. @@ -154,8 +114,10 @@ valid coordinates are given.
    -

    Values

    - The values for each of the directives can any of the following: + +

    Values

    + +

    The values for each of the directives can any of the following:

    @@ -163,7 +125,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.
    @@ -197,12 +159,13 @@ default.
    -

    Coordinates

    + +

    Coordinates

    0,0 200,200
    -
    A coordinate consists of an x and a y +
    A coordinate consists of an x and a y value separated by a comma. The coordinates are separated from each other by whitespace. To accommodate the way Lynx handles imagemaps, should a user select the coordinate @@ -210,7 +173,9 @@ selected.
    -

    Quoted Text

    + + +

    Quoted Text

    "Menu Text"
    @@ -218,64 +183,64 @@
    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

    +

    Example Mapfile

    -
    - #Comments are printed in a 'formatted' or - 'semiformatted' menu.
    - #And can contain html tags. <hr>
    - base referer
    +
    + #Comments are printed in a 'formatted' or + '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?"
    -
    - - -

    Referencing your mapfile

    - -
    - <A HREF="/maps/imagemap1.map">
    - <IMG ISMAP SRC="/images/imagemap1.gif">
    - </A>
    -
    -
    - -

    ImapMenu - directive

    - Syntax: ImapMenu - none|formatted|semiformatted|unformatted
    - Context: server config, virtual - host, directory, .htaccess
    - Override: Indexes
    - Module: mod_imap
    - Compatibility: ImapMenu is only - available in Apache 1.1 and later. - -

    The ImapMenu directive determines the action taken if an - imagemap file is called without valid coordinates.

    + 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

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

    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
    +

    The ImapDefault directive sets the default + default used in the imagemap files. Its value is + overridden by a default directive within the + imagemap file. If not present, the default action + is nocontent, which means that a 204 No + Content is sent to the client. In this case, the client + should continue to display the original page.

    +

    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.

    none
    @@ -308,56 +273,4 @@ of your menus, but requires you to treat your map files as HTML instead of plaintext.
    -
    - -

    ImapDefault - directive

    - Syntax: ImapDefault - error|nocontent|map|referer|URL
    - Context: server config, virtual - host, directory, .htaccess
    - Override: Indexes
    - Module: mod_imap
    - Compatibility: ImapDefault is - only available in Apache 1.1 and later. - -

    The ImapDefault directive sets the default - default used in the imagemap files. Its value is - overridden by a default directive within the - imagemap file. If not present, the default action - is nocontent, which means that a 204 No - Content is sent to the client. In this case, the client - should continue to display the original page.

    -
    - -

    ImapBase - directive

    - Syntax: ImapBase - map|referer|URL
    - Context: server config, virtual - host, directory, .htaccess
    - Override: Indexes
    - Module: mod_imap
    - Compatibility: ImapBase is only - available in Apache 1.1 and later. - -

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

    - - - +

    Apache HTTP Server Version 2.0

    IndexHome
    \ No newline at end of file diff --git a/docs/manual/mod/mod_speling.html b/docs/manual/mod/mod_speling.html index 6c1a8984bc..4e8f550064 100644 --- a/docs/manual/mod/mod_speling.html +++ b/docs/manual/mod/mod_speling.html @@ -2,10 +2,9 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --->mod_speling - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_speling

    Description:This module attempts to correct misspellings of URLs that -users might have entered, by ignoring capitalization and by -allowing up to one misspelling.
    Status:Extension
    Module Identifier:speling_module
    Compatibility:Available in Apache 1.3 and later. Available as -an External module in Apache 1.1 and later.

    Summary

    +-->mod_speling - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_speling

    Description:Attempts to correct mistaken URLs that +users might have entered by ignoring capitalization and by +allowing up to one misspelling
    Status:Extension
    Module Identifier:speling_module

    Summary

    Requests to documents sometimes cannot be served by the core apache server because the request was misspelled or @@ -34,8 +33,8 @@ an External module in Apache 1.1 and later.

    -

    Directives


    CheckSpelling Directive

    Description: This directive enables or disables the spelling -module.
    Syntax:CheckSpelling on|off
    Default:CheckSpelling Off
    Context:server config, virtual host, directory, .htaccess
    Override:Options
    Status:Extension
    Module:mod_speling
    Compatibility:CheckSpelling was available as a separately available +

    Directives


    CheckSpelling Directive

    Description: Enables the spelling +module
    Syntax:CheckSpelling on|off
    Default:CheckSpelling Off
    Context:server config, virtual host, directory, .htaccess
    Override:Options
    Status:Extension
    Module:mod_speling
    Compatibility:CheckSpelling was available as a separately available module for Apache 1.1, but was limited to miscapitalizations. As of Apache 1.3, it is part of the Apache distribution. Prior to Apache 1.3.2, the CheckSpelling directive was only available in the @@ -59,8 +58,8 @@ of Apache 1.3, it is part of the Apache distribution. Prior to Apache directory names.
  • spelling corrections apply strictly to existing files, so - a request for the <Location /status> may + a request for the <Location /status> may get incorrectly treated as the negotiated file - "/stats.html".
  • + "/stats.html".

    Apache HTTP Server Version 2.0

    IndexHome \ No newline at end of file diff --git a/docs/manual/mod/mod_status.html b/docs/manual/mod/mod_status.html index 6551ff8f36..630e8049aa 100644 --- a/docs/manual/mod/mod_status.html +++ b/docs/manual/mod/mod_status.html @@ -2,8 +2,8 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --->mod_status - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_status

    Description:This module provides information on server activity and -performance.
    Status:Base
    Module Identifier:status_module
    Compatibility:Available in Apache 1.1 and later

    Summary

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

    Warning: This document has not been updated @@ -45,15 +45,15 @@ performance.
    The current hosts and requests being processed (*) - A compile-time option must be used to display the details +

    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. + these statistics does not exist within standard Apache.

    Directives

    Enabling Status Support

    - To enable status reports only for browsers from the foo.com +

    To enable status reports only for browsers from the foo.com domain add this code to your httpd.conf - configuration file + configuration file

    <Location /server-status>
    SetHandler server-status
    @@ -74,20 +74,20 @@ performance.
    Automatic Updates - You can get the status page to update itself automatically if +

    You can get the status page to update itself automatically if you have a browser that supports "refresh". Access the page http://your.server.name/server-status?refresh=N to - refresh the page every N seconds. + refresh the page every N seconds.

    Machine Readable Status File

    - A machine-readable version of the status file is available by +

    A machine-readable version of the status file is available by accessing the page http://your.server.name/server-status?auto. This is useful when automatically run, see the Perl program in the /support directory of Apache, - log_server_status. + log_server_status.

    It should be noted that if mod_status is diff --git a/docs/manual/mod/mod_suexec.html b/docs/manual/mod/mod_suexec.html index 9fdd2e2335..e92aa194df 100644 --- a/docs/manual/mod/mod_suexec.html +++ b/docs/manual/mod/mod_suexec.html @@ -2,8 +2,8 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --->mod_suexec - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_suexec

    Description:This module 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
    [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

    This module allows CGI scripts to run as a specified user and Group.

    Directives


    SuexecUserGroup Directive

    Description:
    Syntax:SuexecUserGroup User Group
    Default:None
    Context:server config, virtual host
    Status:Extension
    Module:mod_suexec
    Compatibility:SuexecUserGroup is only available in 2.0 and diff --git a/docs/manual/mod/mod_unique_id.html b/docs/manual/mod/mod_unique_id.html index 02191fee7b..a040c54d6a 100644 --- a/docs/manual/mod/mod_unique_id.html +++ b/docs/manual/mod/mod_unique_id.html @@ -2,8 +2,8 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --->mod_unique_id - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_unique_id

    Description:This module provides an environment variable with a unique -identifier for each request.
    Status:Extension
    Module Identifier:unique_id_module
    Compatibility:Available in Apache 1.3 and later.

    Summary

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

    This module provides a magic token for each request which is guaranteed to be unique across "all" requests under very diff --git a/docs/manual/mod/mod_userdir.html b/docs/manual/mod/mod_userdir.html index fb51735aef..fd0879bb94 100644 --- a/docs/manual/mod/mod_userdir.html +++ b/docs/manual/mod/mod_userdir.html @@ -2,8 +2,8 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --->mod_userdir - Apache HTTP Server

    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_userdir

    Description:This module provides for user-specific -directories.
    Status:Base
    Module Identifier:userdir_module

    Summary

    +-->mod_userdir - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_userdir

    Description:Provides for user-specific +directories
    Status:Base
    Module Identifier:userdir_module

    Summary

    Directives


    UserDir Directive

    Description: Sets the directory from which to serve files when requests for a particular user are received, denoted by requests containing ~username, such as diff --git a/docs/manual/mod/mod_vhost_alias.html b/docs/manual/mod/mod_vhost_alias.html index 4071e06f74..dcdb473420 100644 --- a/docs/manual/mod/mod_vhost_alias.html +++ b/docs/manual/mod/mod_vhost_alias.html @@ -2,8 +2,8 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --->mod_vhost_alias - Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_vhost_alias

    Description:This module provides support for dynamically configured mass virtual -hosting.
    Status:Extension
    Module Identifier:vhost_alias_module
    Compatibility:Available in Apache 1.3.7 and later.

    Summary

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

    This module creates dynamically configured virtual hosts, by allowing the IP address and/or the Host: header of @@ -11,9 +11,8 @@ hosting.

    - See also: UseCanonicalName. -

    Directives

    Directory Name Interpolation

    +

    See also

    Directives

    Directory Name Interpolation

    All the directives in this module interpolate a string into @@ -162,7 +161,7 @@ hosting.

    %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
    Override:
    Status:Extension
    Module:mod_vhost_alias
    Compatibility:VirtualDocumentRoot is only available in 1.3.7 and +for a given virtual host
    Syntax:VirtualDocumentRoot interpolated-directory
    Default:none
    Context:server config, virtual host
    Override:
    Status:Extension
    Module:mod_vhost_alias
    Compatibility:VirtualDocumentRoot is only available in 1.3.7 and later.

    The VirtualDocumentRoot directive allows you to @@ -184,7 +183,7 @@ and later.

    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
    Override:
    Status:Extension
    Module:mod_vhost_alias
    Compatibility:VirtualScriptAlias is only available in 1.3.7 +a given virtual host
    Syntax:VirtualScriptAlias interpolated-directory
    Default:none
    Context:server config, virtual host
    Override:
    Status:Extension
    Module:mod_vhost_alias
    Compatibility:VirtualScriptAlias is only available in 1.3.7 and later.

    The VirtualScriptAlias directive allows you to @@ -195,7 +194,7 @@ and later.

    /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
    Override:
    Status:Extension
    Module:mod_vhost_alias
    Compatibility:VirtualScriptAliasIP is only available in 1.3.7 +a given virtual host
    Syntax:VirtualScriptAliasIP interpolated-directory
    Default:none
    Context:server config, virtual host
    Override:
    Status:Extension
    Module:mod_vhost_alias
    Compatibility:VirtualScriptAliasIP is only available in 1.3.7 and later.

    The VirtualScriptAliasIP directive is like the -- 2.40.0