Commit 0276bdd0 authored by Andre Malo's avatar Andre Malo
Browse files

fix XML validation errors


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@125651 13f79535-47bb-0310-9956-ffa450edef68
parent 00b06cc5
Loading
Loading
Loading
Loading
+2 −6
Changes for docs/manual/mod/mod_ldap.xml: 2 added lines, 6 removed lines.
Original line number Diff line number Diff line
@@ -470,7 +470,7 @@ Certificate Authority or global client certificates</description>
    certificates and/or client certificates <module>mod_ldap</module>
    should use when establishing an SSL or TLS connection to an LDAP
    server. The type specifies the kind of certificate parameter being
    set, depending on the LDAP toolkit being used. Supported types are:
    set, depending on the LDAP toolkit being used. Supported types are:</p>
    <ul>
      <li>CA_DER - binary DER encoded CA certificate</li>
      <li>CA_BASE64 - PEM encoded CA certificate</li>
@@ -483,7 +483,6 @@ Certificate Authority or global client certificates</description>
      <li>KEY_DER - binary DER encoded private key</li>
      <li>KEY_BASE64 - PEM encoded private key</li>
    </ul>
    </p>
</usage>
</directivesynopsis>

@@ -501,7 +500,7 @@ connection client certificates.</description>
    or TLS connection to an LDAP server. Not all LDAP toolkits support
    per connection client certificates (See the toolkit guide for details).
    The type specifies the kind of certificate parameter being
    set, depending on the LDAP toolkit being used. Supported types are:
    set, depending on the LDAP toolkit being used. Supported types are:</p>
    <ul>
      <li>CERT_DER - binary DER encoded client certificate</li>
      <li>CERT_BASE64 - PEM encoded client certificate</li>
@@ -509,7 +508,6 @@ connection client certificates.</description>
      <li>KEY_DER - binary DER encoded private key</li>
      <li>KEY_BASE64 - PEM encoded private key</li>
    </ul>
    </p>
</usage>
</directivesynopsis>

@@ -526,7 +524,6 @@ connection client certificates.</description>
      <li>SSL - ldaps:// encryption on default port 636</li>
      <li>TLS - STARTTLS encryption on default port 389</li>
    </ul>
    </p>

    <p>Not all LDAP toolkits support all the above modes. An error message
    will be logged at runtime if a mode is not supported, and the
@@ -535,7 +532,6 @@ connection client certificates.</description>

    <p>If an ldaps:// URL is specified, the mode becomes SSL and the setting
    of LDAPTrustedMode is ignored.</p>

</usage>
</directivesynopsis>