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

Backport r1786113 (Wording/formatting/typo fixes.) 

+ s/require/Require/ to help syntax color highlight work correctly. (r1838458 + r1838459 in trunk)

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

docs/manual/mod/core.xml

+16 −15
Original line number Diff line number Diff line
@@ -2005,7 +2005,7 @@ filenames</description> 


    <highlight language="config">

&lt;FilesMatch "^(?&lt;sitename&gt;[^/]+)"&gt;

    require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example

    Require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example

&lt;/FilesMatch&gt;

    </highlight>

</usage>
@@ -2397,8 +2397,8 @@ presence or absence of a specific directive</description> 
    <p>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 <var>directive-name</var> is

    <strong>not</strong> defined.</p>

    and only processes the directives if <var>directive-name</var> is

    <strong>not</strong> available.</p>



    <note>This section should only be used if you need to have one

    configuration file that works across multiple versions of
@@ -2427,30 +2427,31 @@ presence or absence of a specific section directive</description> 
    <var>test</var>&gt;...&lt;/IfSection&gt;</code> 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 <directive type="section">virtualhost</directive> which

    such as <directive type="section">VirtualHost</directive> which

    encloses other directives, and has a directive name with a leading

    "&lt;".  The sec

    "&lt;".</p>



    The directives within an <directive type="section"

    <p>The directives within an <directive type="section"

    >IfSection</directive> section are only processed if the <var>test</var>

    is true. If <var>test</var> is false, everything between the start and

    end markers is ignored.</p>



    <p>The <var>section-name</var> specified must not include the

    leading "&lt;".  The <var>test</var> in the <directive

    type="section">IfSection</directive> section can be one of two

    forms:</p>

    <p>The <var>section-name</var> must be specified without either

    the leading "&lt;" or closing "&gt;".  The <var>test</var> in the

    <directive type="section">IfSection</directive> section can be one

    of two forms:</p>



    <ul>

      <li><var>section-name</var></li>

      <li>!<var>section-name</var></li>

    </ul>



    <p>In the former case, the directives between the start and

    end markers are only processed if a section directive of the given

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

    <var>section-name</var> is <strong>not</strong> defined.</p>

    reverses the test, and only processes the directives if

    <var>section-name</var> is <strong>not</strong> an available

    section directive.</p>



    <p>For example:</p>
@@ -3169,7 +3170,7 @@ matching URLs</description> 


    <highlight language="config">

&lt;LocationMatch "^/combined/(?&lt;sitename&gt;[^/]+)"&gt;

    require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example

    Require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example

&lt;/LocationMatch&gt;

    </highlight>

</usage>