From: Joe Orton Date: Thu, 31 May 2018 15:13:38 +0000 (+0000) Subject: Transforms. X-Git-Tag: 2.4.34~125 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3fa1768df42768b765e976590b938e9c6d981074;p=apache Transforms. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1832625 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 7206d845f5..e529e0b94c 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -74,7 +74,10 @@ available
  • HttpProtocolOptions
  • <If>
  • <IfDefine>
    • +
  • <IfDirective>
    • +
  • <IfFile>
  • <IfModule>
    • +
  • <IfSection>
  • Include
  • IncludeOptional
  • KeepAlive
    • @@ -828,12 +831,12 @@ which no other media type configuration could be found. Status:Core Module:core -

    In its one parameter form, Define is equivalent - to passing the -D argument to httpd. It - can be used to toggle the use of - <IfDefine> sections - without needing to alter -D arguments in any startup - scripts.

    +

    In its one parameter form, Define is + equivalent to passing the -D argument to + httpd. It can be used to toggle the use of + <IfDefine> + sections without needing to alter -D arguments in any + startup scripts.

    In addition to that, if the second parameter is given, a config variable is set to this value. The variable can be used in the configuration using @@ -2251,6 +2254,88 @@ if a test is true at startup </IfDefine> + +

    top
    +

    <IfDirective> Directive

    + + + + + + + + +
    Description:Encloses directives that are processed conditional on the +presence or absence of a specific directive
    Syntax:<IfDirective [!]directive-name> ... + </IfDirective>
    Context:server config, virtual host, directory, .htaccess
    Override:All
    Status:Core
    Module:core
    Compatibility:Available in 2.4.34 and later.
    +

    The <IfDirective test>...</IfDirective> + section is used to mark directives that are conditional on the presence of + a specific directive. The directives within an <IfDirective> section are only processed if the test + is true. If test is false, everything between the start and + end markers is ignored.

    + +

    The test in the <IfDirective> section can be one of two forms:

    + + + +

    In the former case, the directives between the start and end + markers are only processed if a directive of the given name is + available at the time of processing. The second format reverses the test, + and only processes the directives if the directive-name is + not defined.

    + +
    This section should only be used if you need to have one + configuration file that works across multiple versions of + httpd, regardless of whether a particular + directive is available. In normal operation, directives need not + be placed in <IfDirective> + sections.
    + +

    See also

    + +
    +
    top
    +

    <IfFile> Directive

    + + + + + + + +
    Description:Encloses directives that will be processed only +if file exists at startup
    Syntax:<IfFile [!]parameter-name> ... + </IfFile>
    Context:server config, virtual host, directory, .htaccess
    Status:Core
    Module:core
    Compatibility:Available in 2.4.34 and later.
    +

    The <IfFile filename>...</IfFile> + section is used to mark directives that are conditional on + the existence of a file on disk. The directives within an + <IfFile> section are only + processed if the filename exists. If filename + doesn't exist, everything between the start and end markers is + ignored. filename can be an absolute path or a path + relative to the server root.

    + +

    The filename in the <IfFile + > section directive can take the same forms as the + test variable in the <IfDefine + > section, i.e. the test can be negated if the + ! character is placed directly before filename. +

    + +

    If a relative filename is supplied, the check is + ServerRoot relative. In the case where + this directive occurs before the ServerRoot, + the path will be checked relative to the compiled-in server root or + the server root passed in on the command line via the -d + parameter.

    + +
    top

    <IfModule> Directive

    @@ -2304,6 +2389,64 @@ later. placed in <IfModule> sections.
    + +
    top
    +

    <IfSection> Directive

    + + + + + + + + +
    Description:Encloses directives that are processed conditional on the +presence or absence of a specific section directive
    Syntax:<IfSection [!]section-name> ... + </IfSection>
    Context:server config, virtual host, directory, .htaccess
    Override:All
    Status:Core
    Module:core
    Compatibility:Available in 2.4.34 and later.
    +

    The <IfSection + test>...</IfSection> section is used + to mark directives that are conditional on the presence of a + specific section directive. A section directive is any directive + such as <virtualhost> which + encloses other directives, and has a directive name with a leading + "<". The sec + + The directives within an <IfSection> section are only processed if the test + is true. If test is false, everything between the start and + end markers is ignored.

    + +

    The section-name specified must not include the + leading "<". The test in the <IfSection> section can be one of two + forms:

    + + + +

    In the former case, the directives between the start and + end markers are only processed if a section directive of the given + name is available at the time of processing. The second format + reverses the test, and only processes the directives if the + section-name is not defined.

    + +

    For example:

    + + 
    <IfSection VirtualHost>
+   ...
+</IfSection>
    + + +
    This section should only be used if you need to have one + configuration file that works across multiple versions of httpd, + regardless of whether a particular section directive is + available. In normal operation, directives need not be placed in + <IfSection> sections.
    + +

    See also

    +
    top

    Include Directive

    diff --git a/docs/manual/mod/core.xml.de b/docs/manual/mod/core.xml.de index 9b2692789e..8aca1b3b10 100644 --- a/docs/manual/mod/core.xml.de +++ b/docs/manual/mod/core.xml.de @@ -1,7 +1,7 @@ - + + + diff --git a/docs/manual/mod/core.xml.ja b/docs/manual/mod/core.xml.ja index 35f409b74f..8f3e1d6d8f 100644 --- a/docs/manual/mod/core.xml.ja +++ b/docs/manual/mod/core.xml.ja @@ -1,7 +1,7 @@ - + +