Commit e45a7689 authored by Christophe Jaillet's avatar Christophe Jaillet
Browse files

Add some compatibility note + some small syntax highlight sugar. 

(1828478 in trunk)

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1834775 13f79535-47bb-0310-9956-ffa450edef68
parent 737551b7

docs/manual/mod/core.xml

+10 −8
Original line number Diff line number Diff line
@@ -2278,28 +2278,28 @@ if file exists at startup</description> 
<contextlist><context>server config</context><context>virtual host</context>

<context>directory</context><context>.htaccess</context>

</contextlist>

<compatibility>Available in 2.4.34 and later.</compatibility>

<compatibility>Available in 2.4.34 and later</compatibility>



<usage>

    <p>The <code>&lt;IfFile <var>filename</var>&gt;...&lt;/IfFile&gt;

    </code> section is used to mark directives that are conditional on

    the existence of a file on disk. The directives within an

    <directive type="section">IfFile</directive> section are only

    processed if the <var>filename</var> exists. If <var> filename</var>

    processed if <var>filename</var> exists. If <var>filename</var>

    doesn't exist, everything between the start and end markers is

    ignored. <var>filename</var> can be an absolute path or a path

    relative to the server root.</p>



    <p>The <var>filename</var> in the <directive type="section">IfFile

    </directive> section directive can take the same forms as the

    <var>test</var> variable in the <directive type="section">IfDefine

    </directive> section, i.e. the test can be negated if the <code>

    <p>The <var>filename</var> in the <directive type="section"

    >IfFile</directive> section directive can take the same forms as the

    <var>test</var> variable in the <directive type="section" module="core"

    >IfDefine</directive> section, i.e. the test can be negated if the <code>

    !</code> character is placed directly before <var>filename</var>.

    </p>

   

    <p>If a relative <var>filename</var> is supplied, the check is

    <directive>ServerRoot</directive> relative.  In the  case where

    this directive occurs before the <directive>ServerRoot</directive>,

    <directive module="core">ServerRoot</directive> relative. In the case where

    this directive occurs before the <directive module="core">ServerRoot</directive>,

    the path will be checked relative to the compiled-in server root or

    the server root passed in on the command line via the <code>-d</code>

    parameter.</p>
@@ -2373,6 +2373,7 @@ presence or absence of a specific directive</description> 
<contextlist><context>server config</context><context>virtual host</context>

<context>directory</context><context>.htaccess</context>

</contextlist>

<compatibility>Available in 2.4.34 and later</compatibility>

<override>All</override>

<compatibility>Available in 2.4.34 and later.</compatibility>
@@ -2418,6 +2419,7 @@ presence or absence of a specific section directive</description> 
<contextlist><context>server config</context><context>virtual host</context>

<context>directory</context><context>.htaccess</context>

</contextlist>

<compatibility>Available in 2.4.34 and later</compatibility>

<override>All</override>

<compatibility>Available in 2.4.34 and later.</compatibility>