From: Joshua Slive Date: Mon, 27 May 2002 00:44:32 +0000 (+0000) Subject: Update transformations. X-Git-Tag: 2.0.37~250 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=41c6a81e329a506ff6f2933b2851ca82414febf4;p=apache Update transformations. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95298 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_include.html.en b/docs/manual/mod/mod_include.html.en index 68928048bc..a1578492cb 100644 --- a/docs/manual/mod/mod_include.html.en +++ b/docs/manual/mod/mod_include.html.en @@ -29,7 +29,7 @@

The following directive must be given for the directories containing the shtml files (typically in a <Directory> section, but this directive is - also valid .htaccess files if AllowOverride + also valid in .htaccess files if AllowOverride Options is set):

@@ -413,11 +413,11 @@
<!--#if expr="\"$DOCUMENT_URI\" = \"/foo/file.html\"" -->
- in foo
+   in foo
<!--#elif expr="\"$DOCUMENT_URI\" = \"/bar/file.html\"" -->
- in bar
+   in bar
<!--#else -->
- in neither
+   in neither
<!--#endif -->

Flow Control Elements

@@ -523,14 +523,13 @@ default. You can use the AcceptPathInfo directive to configure the server to accept requests with PATH_INFO.

-

SSIEndTag Directive

Description: Changes the string that mod_include looks for to end an -include command.
Syntax:SSIEndTag tag
Default:SSIEndTag "-->"
Context:server config, virtual host
Override:FileInfo
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.30 and later. +

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 a include command.

+ to mark the end of an include element.

-

See also

  • SSIStartTag

SSIErrorMsg Directive

Description: Changes the error message displayed when there is an error
Syntax:SSIErrorMsg message
Default:SSIErrorMsg -"[an error occurred while processing this directive]"
Context:server config, virtual host, directory, .htaccess
Override:
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.30 and later.
+

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.

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 @@ -540,31 +539,31 @@ include command.

SSIStartTag Directive
Description:
Syntax:Changes the string that mod_include looks for to start an -include element
Default:SSIStartTag "<!--"
Context:server config, virtual host
Override:
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.30 and later.
+

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.

-

You may want to use this option if have 2 servers parsing the +

You may want to use this option if you have 2 servers parsing the output of a file each processing different commands (possibly at different times).

-

See also

  • SSIEndTag

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:
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.30 and later.
+

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.

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.

This directive has the same effect as the <!--#config timefmt=formatstring --> element.

-

SSIUndefinedEcho Directive

Description: Changes the string that mod_include displays when -a variable isn't set.
Syntax:SSIUndefinedEcho tag
Default:SSIUndefinedEcho "<!-- undef -->"
Context:server config, virtual host
Override:FileInfo
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.34 and later. +

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


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
Compatibility:
+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 diff --git a/docs/manual/mod/mod_setenvif.html.en b/docs/manual/mod/mod_setenvif.html.en index 2759b874cc..4337889606 100644 --- a/docs/manual/mod/mod_setenvif.html.en +++ b/docs/manual/mod/mod_setenvif.html.en @@ -3,7 +3,7 @@ This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->mod_setenvif- Apache HTTP Server

[APACHE DOCUMENTATION]

Apache HTTP Server Version 2.0

Apache Module mod_setenvif

Description:Allows the setting of environment variables based -on characteristics of the request
Status:Base
Module Identifier:setenvif_module
Compatibility:Available in Apache 1.3 and later

Summary

+on characteristics of the request
Status:Base
Module Identifier:setenvif_module

Summary

The mod_setenvif module allows you to set environment variables according to whether different aspects of @@ -21,57 +21,27 @@ on characteristics of the request

BrowserMatch
  • BrowserMatchNoCase
  • SetEnvIf
  • SetEnvIfNoCase
  • See also


    BrowserMatch Directive

    Description: Sets environment variables conditional on HTTP User-Agent -
    Syntax:BrowserMatch regex env-variable[=value] -[env-variable[=value]] ...
    Context:server config, virtual host, directory, .htaccess
    Override:FileInfo
    Status:Base
    Module:mod_setenvif
    Compatibility:Apache 1.2 and - above (in Apache 1.2 this directive was found in the - now-obsolete mod_browser module)
    -

    The BrowserMatch directive defines - environment variables based on the User-Agent HTTP - request header field. The first argument should be a POSIX.2 - extended regular expression (similar to an - egrep-style regex). The rest of the arguments give - the names of variables to set, and optionally values to which they - should be set. These take the form of

    - -
      -
    1. varname, or
    2. - -
    3. !varname, or
    4. - -
    5. varname=value
    6. -
    - -

    In the first form, the value will be set to "1". The second - will remove the given variable if already defined, and the - third will set the variable to the value given by - value. If a User-Agent - string matches more than one entry, they will be merged. - Entries are processed in the order in which they appear, and - later entries can override earlier ones.

    +
    Syntax:BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...
    Context:server config, virtual host, directory, .htaccess
    Override:FileInfo
    Status:Base
    Module:mod_setenvif
    +

    The BrowserMatch is a special cases of the + SetEnvIf directive that + sets environment variables conditional on the + User-Agent HTTP request header. The following two + lines have the same effect:

    +
    + BrowserMatchNoCase Robot is_a_robot
    + SetEnvIfNoCase User-Agent Robot is_a_robot
    +
    -

    For example:

    +

    Some additional examples:

    BrowserMatch ^Mozilla forms jpeg=yes browser=netscape
    BrowserMatch "^Mozilla/[2-3]" tables agif frames javascript
    BrowserMatch MSIE !javascript
    - -

    Note that the regular expression string is - case-sensitive. For case-INsensitive matching, - see the BrowserMatchNoCase - directive.

    - -

    The BrowserMatch and - BrowserMatchNoCase directives are special cases of - the SetEnvIf and SetEnvIfNoCase - directives. The following two lines have the same effect:

    -
    - BrowserMatchNoCase Robot is_a_robot
    - SetEnvIfNoCase User-Agent Robot is_a_robot
    -

    BrowserMatchNoCase Directive

    Description: Sets environment variables conditional on User-Agent without -respect to case
    Syntax:BrowserMatchNoCase regex env-variable[=value] - [env-variable[=value]] ...
    Context:server config, virtual host, directory, .htaccess
    Override:FileInfo
    Status:Base
    Module:mod_setenvif
    Compatibility:Apache 1.2 and +respect to case
    Syntax:BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...
    Context:server config, virtual host, directory, .htaccess
    Override:FileInfo
    Status:Base
    Module:mod_setenvif
    Compatibility:Apache 1.2 and above (in Apache 1.2 this directive was found in the now-obsolete mod_browser module)
    @@ -94,16 +64,21 @@ respect to caseSetEnvIf Directive
    Description: Sets environment variables based on attributes of the request
    Syntax:SetEnvIf attribute - regex env-variable[=value] - [env-variable[=value]] ...
    Context:server config, virtual host, directory, .htaccess
    Override:FileInfo
    Status:Base
    Module:mod_setenvif
    Compatibility:Apache 1.3 and - above; the Request_Protocol keyword and environment-variable - matching are only available with 1.3.7 and later
    -

    The SetEnvIf directive defines environment - variables based on attributes of the request. These attributes - can be the values of various HTTP request header fields (see RFC2616 - for more information about these), or of other aspects of the - request, including the following:

    - + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...Context:server config, virtual host, directory, .htaccessOverride:FileInfoStatus:BaseModule:mod_setenvif +

    The SetEnvIf directive defines + environment variables based on attributes of the request. The + attribute specified in the first argument can be one of three + things:

    + +
      +
    1. An HTTP request header field (see RFC2616 + for more information about these); for example: Host, + User-Agent, Referer, and + Accept-Language. A regular expression may be + used to specify a set of request headers.
    2. + +
    3. One of the following aspects of the request: +
    4. + +
    5. The name of an environment variable in the list of those +associated with the request. This allows +SetEnvIf directives to test against the result +of prior matches. Only those environment variables defined by earlier +SetEnvIf[NoCase] directives are available for testing in +this manner. 'Earlier' means that they were defined at a broader scope +(such as server-wide) or previously in the current directive's scope. +Environment variables will be considered only if there was no match +among request characteristics and a regular expression was not +used for the attribute.
    6. +
    + +

    The second argument (regex) is a Perl compatible regular expression. +This is similar to a POSIX.2 egrep-style regular expression. +If the regex matches against the attribute, +then the remainder of the arguments are evaluated.

    + +

    The rest of the arguments give the names of variables to set, and +optionally values to which they should be set. These take the form +of

    -

    Some of the more commonly used request header field names - include Host, User-Agent, and - Referer.

    - -

    If the attribute name doesn't match any of the - special keywords, nor any of the request's header field names, - it is tested as the name of an environment variable in the list - of those associated with the request. This allows - SetEnvIf directives to test against the result of - prior matches.

    - -
    - Only those environment variables defined by earlier - SetEnvIf[NoCase] directives are available for - testing in this manner. 'Earlier' means that they were - defined at a broader scope (such as server-wide) or - previously in the current directive's scope. -
    - -

    attribute may be a regular expression when used to - match a request header. If attribute is a regular - expression and it doesn't match any of the request's header - names, then attribute is not tested against the - request's environment variable list.

    +
      +
    1. varname, or
    2. + +
    3. !varname, or
    4. + +
    5. varname=value
    6. +
    + +

    In the first form, the value will be set to "1". The second + will remove the given variable if already defined, and the + third will set the variable to the literal value given by + value.

    Example:

    @@ -175,8 +161,9 @@ respect to case

    SetEnvIfNoCase Directive

    Description: Sets environment variables based on attributes of the request -without respect to case
    Syntax:SetEnvIfNoCase attribute regex env-variable[=value] - [env-variable[=value]] ...
    Context:server config, virtual host, directory, .htaccess
    Override:FileInfo
    Status:Base
    Module:mod_setenvif
    Compatibility:Apache 1.3 and above
    +without respect to case
    Syntax:SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...
    Context:server config, virtual host, directory, .htaccess
    Override:FileInfo
    Status:Base
    Module:mod_setenvif
    Compatibility:Apache 1.3 and above

    The SetEnvIfNoCase is semantically identical to the SetEnvIf directive, diff --git a/docs/manual/mod/mod_so.html.en b/docs/manual/mod/mod_so.html.en index 92b67c5aa9..aa0dbba650 100644 --- a/docs/manual/mod/mod_so.html.en +++ b/docs/manual/mod/mod_so.html.en @@ -2,10 +2,8 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - -->mod_so- Apache HTTP Server

    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_so

    Description: - This module provides for loading of executable code and - modules into the server at start-up or restart time. -
    Status:Base (Windows>; Optional (Unix)
    Module Identifier:so_module
    Compatibility:Available in Apache 1.3 and later.

    Summary

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

    Apache HTTP Server Version 2.0

    Apache Module mod_so

    Description:Loading of executable code and +modules into the server at start-up or restart time
    Status:Base (Windows); Optional (Unix)
    Module Identifier:so_module

    Summary

    On selected operating systems this module can be used to load modules into Apache at runtime via the Dynamic Shared Object (DSO) mechanism, @@ -14,14 +12,8 @@

    On Unix, the loaded code typically comes from shared object files (usually with .so extension), on Windows this may either the .so or .dll - extension. This module is only available in Apache 1.3 and - up.

    - -

    In previous releases, the functionality of this module was - provided for Unix by mod_dld, and for Windows by mod_dll. On - Windows, mod_dll was used in beta release 1.3b1 through 1.3b5. - mod_so combines these two modules into a single module for all - operating systems.

    + extension.

    +

    Warning

    Apache 1.3 modules cannot be directly used with Apache 2.0 - the module must be modified to dynamically @@ -33,6 +25,7 @@

    The module name format changed for Windows with Apache 1.3.15 and 2.0 - the modules are now named as mod_foo.so

    +

    While mod_so still loads modules with ApacheModuleFoo.dll names, the new naming convention is preferred; if you are converting your loadable module for 2.0, @@ -96,7 +89,7 @@ root, and use the LoadModule directive to load it.

    -

    LoadFile Directive

    Description: Link in the named object file or library
    Syntax:LoadFile filename [filename] ...
    Default:none
    Context:server config
    Status:Base (Windows>; Optional (Unix)
    Module:mod_so
    +

    LoadFile Directive

    Description: Link in the named object file or library
    Syntax:LoadFile filename [filename] ...
    Context:server config
    Status:Base (Windows); Optional (Unix)
    Module:mod_so

    The LoadFile directive links in the named object files or libraries when the server is started or restarted; this is used @@ -109,7 +102,7 @@

    LoadFile libexex/libxmlparse.so

    LoadModule Directive

    Description: Links in the object file or library, and adds to the list -of active modules
    Syntax:LoadModule module filename
    Default:none
    Context:server config
    Status:Base (Windows>; Optional (Unix)
    Module:mod_so
    +of active modules
    Syntax:LoadModule module filename
    Context:server config
    Status:Base (Windows); Optional (Unix)
    Module:mod_so

    The LoadModule directive links in the object file or library filename and adds the module structure named module to the list of active modules. Module diff --git a/docs/manual/mod/mod_suexec.html.en b/docs/manual/mod/mod_suexec.html.en index 53e284952d..32c2519c93 100644 --- a/docs/manual/mod/mod_suexec.html.en +++ b/docs/manual/mod/mod_suexec.html.en @@ -4,13 +4,13 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->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 +

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

    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 using the User and - Group directives inside of VirtualHosts.

    +

    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.


    Apache HTTP Server Version 2.0

    IndexHome \ 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 4be6198426..61d512fb2f 100644 --- a/docs/manual/mod/mod_userdir.html.en +++ b/docs/manual/mod/mod_userdir.html.en @@ -2,17 +2,12 @@ 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: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 -http://server.example.com/~bob/
    Syntax:UserDir directory-filename
    Default:UserDir public_html
    Context:server config, virtual -host
    Status:Base
    Module:mod_userdir
    Compatibility:All forms except the UserDir public_html -form are only available in Apache 1.1 or above. Use of the -enabled keyword, or disabled with a -list of usernames, is only available in Apache 1.3 and -above.
    + -->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

    +This module allows user-specific directories to be accessed using the +http://example.com/~user/ syntax. +

    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

    The UserDir directive sets the real directory in a user's home directory to use when a request for a @@ -71,14 +66,11 @@ http://www.foo.com/~*/

    http://www.foo.com/~bob/one/two.html
    Be careful when using this directive; for instance, - "UserDir ./" would map - "/~root" to "/" - which is probably - undesirable. If you are running Apache 1.3 or above, it is - strongly recommended that your configuration include a - "UserDir disabled root" declaration. - See also the Directory - directive and the Security - Tips page for more information. + "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 + more information.

    Additional examples:

    diff --git a/docs/manual/mod/mod_usertrack.html.en b/docs/manual/mod/mod_usertrack.html.en index 716093c6ca..a9246637d1 100644 --- a/docs/manual/mod/mod_usertrack.html.en +++ b/docs/manual/mod/mod_usertrack.html.en @@ -3,9 +3,8 @@ This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->mod_usertrack- Apache HTTP Server
    [APACHE DOCUMENTATION]

    Apache HTTP Server Version 2.0

    Apache Module mod_usertrack

    Description: - This module uses cookies to provide for a - clickstream log of user activity on a site. -
    Status:Extension
    Module Identifier:usertrack_module
    Compatibility:Known as mod_cookies prior to Apache 1.3.

    Summary

    +Clickstream logging of user activity on a site +
    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 @@ -28,8 +27,8 @@ 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.

    + implements the old CookieLog directive, but this + should be upgraded to the above CustomLog directive.

    2-digit or 4-digit dates for cookies?

    @@ -69,7 +68,7 @@ form, but also understands 4-digit years, which can probably reach up until time late in the year "37". -

    CookieDomain Directive

    Description: controls the setting of the domain to which the tracking cookie applies.
    Syntax:CookieDomain domain
    Default:None
    Context:server config, virtual host, directory, .htaccess
    Status:Extension
    Module:mod_usertrack
    +

    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 @@ -78,8 +77,7 @@ 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:
    Syntax:CookieExpires expiry-period
    Default:
    Context:server config, virtual host, directory, .htaccess
    Override:
    Status:Extension
    Module:mod_usertrack
    Compatibility:In 1.3.20 and earlier, not usable in directory and -.htaccess
    +

    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 @@ -90,7 +88,7 @@ time late in the year "37".

    If this directive is not used, cookies last only for the current browser session.

    -

    CookieName Directive

    Description:
    Syntax:CookieName token
    Default:Apache
    Context:server config, virtual host, directory, .htaccess
    Status:Extension
    Module:mod_usertrack
    +

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

    @@ -98,8 +96,8 @@ 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: Controls the format of the cookie header field
    Syntax:CookieStyle - Netscape|Cookie|Cookie2|RFC2109|RFC2965
    Default:
    Context:server config, virtual host, directory, .htaccess
    Status:Extension
    Module:mod_usertrack
    +

    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:

    @@ -118,7 +116,7 @@ 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:
    Syntax:CookieTracking on|off
    Default:
    Context:server config, virtual host, directory, .htaccess
    Override:FileInfo
    Status:Extension
    Module:mod_usertrack
    +

    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 diff --git a/docs/manual/mod/mod_vhost_alias.html.en b/docs/manual/mod/mod_vhost_alias.html.en index 6537c6db0c..532e93daf7 100644 --- a/docs/manual/mod/mod_vhost_alias.html.en +++ b/docs/manual/mod/mod_vhost_alias.html.en @@ -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:Provides for dynamically configured mass virtual -hosting
    Status:Extension
    Module Identifier:vhost_alias_module

    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 @@ -12,7 +12,8 @@ hostingStat huge number of virtual hosts with similar configurations.

    -

    Directives

    See also

    Directory Name Interpolation

    +

    Directives

    See also

    Directory Name Interpolation

    All the directives in this module interpolate a string into @@ -161,8 +162,7 @@ hostingStat 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
    Override:
    Status:Extension
    Module:mod_vhost_alias
    Compatibility:VirtualDocumentRoot is only available in 1.3.7 and -later.
    +for a given virtual hostSyntax:VirtualDocumentRoot interpolated-directoryDefault:noneContext:server config, virtual hostStatus:ExtensionModule:mod_vhost_alias

    The VirtualDocumentRoot directive allows you to determine where Apache will find your documents based on the @@ -175,16 +175,14 @@ later. 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
    Override:
    Status:Extension
    Module:mod_vhost_alias
    Compatibility:VirtualDocumentRootIP is only available in 1.3.7 -and later.
    +for a given virtual hostSyntax:VirtualDocumentRootIP interpolated-directoryDefault:noneContext:server config, virtual hostStatus:ExtensionModule: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
    Override:
    Status:Extension
    Module:mod_vhost_alias
    Compatibility:VirtualScriptAlias is only available in 1.3.7 -and later.
    +a given virtual hostSyntax:VirtualScriptAlias interpolated-directoryDefault:noneContext:server config, virtual hostStatus:ExtensionModule:mod_vhost_alias

    The VirtualScriptAlias directive allows you to determine where Apache will find CGI scripts in a similar @@ -194,8 +192,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 -and later.
    +a given virtual hostSyntax:VirtualScriptAliasIP interpolated-directoryDefault:noneContext:server config, virtual hostStatus:ExtensionModule:mod_vhost_alias

    The VirtualScriptAliasIP directive is like the VirtualScriptAlias