Commit 4424a484 authored by Andre Malo's avatar Andre Malo
Browse files

update transformation 


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/APACHE_2_0_BRANCH@103718 13f79535-47bb-0310-9956-ffa450edef68
parent a8178a1a

docs/manual/mod/mod_auth_ldap.html.en

+13 −10
Changes for docs/manual/mod/mod_auth_ldap.html.en: 13 added lines, 10 removed lines.
Original line number Diff line number Diff line
@@ -315,7 +315,8 @@ require user "Joe Manager"<br /> 


    <p>This directive specifies an LDAP group whose members are

    allowed access. It takes the distinguished name of the LDAP

    group. For example, assume that the following entry existed in

    group. Note: Do not surround the group name with quotes.

    For example, assume that the following entry existed in

    the LDAP directory:</p>

<div class="example"><p><code>

dn: cn=Administrators, o=Airius<br />
@@ -326,7 +327,7 @@ uniqueMember: cn=Fred User, o=Airius<br /> 


    <p>The following directive would grant access to both Fred and

    Barbara:</p>

<div class="example"><p><code>require group "cn=Administrators, o=Airius"</code></p></div>

<div class="example"><p><code>require group cn=Administrators, o=Airius</code></p></div>



    <p>Behavior of this directive is modified by the <code class="directive"><a href="#authldapgroupattribute">AuthLDAPGroupAttribute</a></code> and

    <code class="directive"><a href="#authldapgroupattributeisdn">AuthLDAPGroupAttributeIsDN</a></code>
@@ -340,11 +341,12 @@ uniqueMember: cn=Fred User, o=Airius<br /> 
    that must match for access to be granted. If the distinguished

    name that was retrieved from the directory server matches the

    distinguished name in the <code>require dn</code>, then

    authorization is granted.</p>

    authorization is granted. Note: do not surround the distinguished

    name with quotes.</p>



    <p>The following directive would grant access to a specific

    DN:</p>

<div class="example"><p><code>require dn "cn=Barbara Jenson, o=Airius"</code></p></div>

<div class="example"><p><code>require dn cn=Barbara Jenson, o=Airius</code></p></div>



    <p>Behavior of this directive is modified by the <code class="directive"><a href="#authldapcomparednonserver">AuthLDAPCompareDNOnServer</a></code>

    directive.</p>
@@ -358,7 +360,8 @@ uniqueMember: cn=Fred User, o=Airius<br /> 
        Grant access to anyone who exists in the LDAP directory,

        using their UID for searches.



<div class="example"><p><code>AuthLDAPURL "ldap://ldap1.airius.com:389/ou=People, o=Airius?uid?sub?(objectClass=*)"<br />

<div class="example"><p><code>

 AuthLDAPURL ldap://ldap1.airius.com:389/ou=People, o=Airius?uid?sub?(objectClass=*)<br />

 require valid-user

</code></p></div>

      </li>
@@ -367,7 +370,7 @@ require valid-user 
        The next example is the same as above; but with the fields

        that have useful defaults omitted. Also, note the use of a

        redundant LDAP server. 

<div class="example"><p><code>AuthLDAPURL "ldap://ldap1.airius.com ldap2.airius.com/ou=People, o=Airius"<br />

<div class="example"><p><code>AuthLDAPURL ldap://ldap1.airius.com ldap2.airius.com/ou=People, o=Airius<br />

require valid-user

</code></p></div>

      </li>
@@ -382,7 +385,7 @@ require valid-user 
        choose an attribute that is guaranteed unique in your

        directory, such as <code>uid</code>. 

<div class="example"><p><code>

AuthLDAPURL "ldap://ldap.airius.com/ou=People, o=Airius?cn"<br />

AuthLDAPURL ldap://ldap.airius.com/ou=People, o=Airius?cn<br />

require valid-user

</code></p></div>

      </li>
@@ -391,7 +394,7 @@ require valid-user 
        Grant access to anybody in the Administrators group. The

        users must authenticate using their UID. 

<div class="example"><p><code>

AuthLDAPURL "ldap://ldap.airius.com/o=Airius?uid"<br />

AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid<br />

require group cn=Administrators, o=Airius

</code></p></div>

      </li>
@@ -403,7 +406,7 @@ require group cn=Administrators, o=Airius 
        only to people (authenticated via their UID) who have

        alphanumeric pagers: 

<div class="example"><p><code>

AuthLDAPURL "ldap://ldap.airius.com/o=Airius?uid??(qpagePagerID=*)"<br />

AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(qpagePagerID=*)<br />

require valid-user

</code></p></div>

      </li>
@@ -419,7 +422,7 @@ require valid-user 
        have a pager, but does need to access the same

        resource:</p>

<div class="example"><p><code>

AuthLDAPURL "ldap://ldap.airius.com/o=Airius?uid??(|(qpagePagerID=*)(uid=jmanager))"<br />

AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(|(qpagePagerID=*)(uid=jmanager))<br />

require valid-user

</code></p></div>

docs/manual/mod/mod_auth_ldap.xml

+14 −11
Changes for docs/manual/mod/mod_auth_ldap.xml: 14 added lines, 11 removed lines.
Original line number Diff line number Diff line 
<?xml version="1.0"?>

<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">

<?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?>

<!-- $Revision: 1.6.2.11 $ -->

<!-- $Revision: 1.6.2.12 $ -->



<!--

 Copyright 2002-2004 The Apache Software Foundation
@@ -297,7 +297,8 @@ require user "Joe Manager"<br /> 


    <p>This directive specifies an LDAP group whose members are

    allowed access. It takes the distinguished name of the LDAP

    group. For example, assume that the following entry existed in

    group. Note: Do not surround the group name with quotes.

    For example, assume that the following entry existed in

    the LDAP directory:</p>

<example>

dn: cn=Administrators, o=Airius<br />
@@ -308,7 +309,7 @@ uniqueMember: cn=Fred User, o=Airius<br /> 


    <p>The following directive would grant access to both Fred and

    Barbara:</p>

<example>require group "cn=Administrators, o=Airius"</example>

<example>require group cn=Administrators, o=Airius</example>



    <p>Behavior of this directive is modified by the <directive

    module="mod_auth_ldap">AuthLDAPGroupAttribute</directive> and
@@ -324,11 +325,12 @@ uniqueMember: cn=Fred User, o=Airius<br /> 
    that must match for access to be granted. If the distinguished

    name that was retrieved from the directory server matches the

    distinguished name in the <code>require dn</code>, then

    authorization is granted.</p>

    authorization is granted. Note: do not surround the distinguished

    name with quotes.</p>



    <p>The following directive would grant access to a specific

    DN:</p>

<example>require dn "cn=Barbara Jenson, o=Airius"</example>

<example>require dn cn=Barbara Jenson, o=Airius</example>



    <p>Behavior of this directive is modified by the <directive

    module="mod_auth_ldap">AuthLDAPCompareDNOnServer</directive>
@@ -343,7 +345,8 @@ uniqueMember: cn=Fred User, o=Airius<br /> 
        Grant access to anyone who exists in the LDAP directory,

        using their UID for searches.



<example>AuthLDAPURL "ldap://ldap1.airius.com:389/ou=People, o=Airius?uid?sub?(objectClass=*)"<br />

<example>

 AuthLDAPURL ldap://ldap1.airius.com:389/ou=People, o=Airius?uid?sub?(objectClass=*)<br />

 require valid-user

</example>

      </li>
@@ -352,7 +355,7 @@ require valid-user 
        The next example is the same as above; but with the fields

        that have useful defaults omitted. Also, note the use of a

        redundant LDAP server. 

<example>AuthLDAPURL "ldap://ldap1.airius.com ldap2.airius.com/ou=People, o=Airius"<br />

<example>AuthLDAPURL ldap://ldap1.airius.com ldap2.airius.com/ou=People, o=Airius<br />

require valid-user

</example>

      </li>
@@ -367,7 +370,7 @@ require valid-user 
        choose an attribute that is guaranteed unique in your

        directory, such as <code>uid</code>. 

<example>

AuthLDAPURL "ldap://ldap.airius.com/ou=People, o=Airius?cn"<br />

AuthLDAPURL ldap://ldap.airius.com/ou=People, o=Airius?cn<br />

require valid-user

</example>

      </li>
@@ -376,7 +379,7 @@ require valid-user 
        Grant access to anybody in the Administrators group. The

        users must authenticate using their UID. 

<example>

AuthLDAPURL "ldap://ldap.airius.com/o=Airius?uid"<br />

AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid<br />

require group cn=Administrators, o=Airius

</example>

      </li>
@@ -388,7 +391,7 @@ require group cn=Administrators, o=Airius 
        only to people (authenticated via their UID) who have

        alphanumeric pagers: 

<example>

AuthLDAPURL "ldap://ldap.airius.com/o=Airius?uid??(qpagePagerID=*)"<br />

AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(qpagePagerID=*)<br />

require valid-user

</example>

      </li>
@@ -404,7 +407,7 @@ require valid-user 
        have a pager, but does need to access the same

        resource:</p>

<example>

AuthLDAPURL "ldap://ldap.airius.com/o=Airius?uid??(|(qpagePagerID=*)(uid=jmanager))"<br />

AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(|(qpagePagerID=*)(uid=jmanager))<br />

require valid-user

</example>

docs/manual/mod/mod_file_cache.html.en

+1 −1
Changes for docs/manual/mod/mod_file_cache.html.en: 1 added line, 1 removed line.
Original line number Diff line number Diff line
@@ -131,7 +131,7 @@ 
    



    <div class="note"><h3>Note</h3>

      <p>Don't bother asking for a for a directive which recursively

      <p>Don't bother asking for a directive which recursively

      caches all the files in a directory. Try this instead... See the 

      <code class="directive"><a href="../mod/core.html#include">Include</a></code> directive, and consider

      this command:</p>

docs/manual/mod/mod_file_cache.xml.ko

+1 −1
Changes for docs/manual/mod/mod_file_cache.xml.ko: 1 added line, 1 removed line.
Original line number Diff line number Diff line 
<?xml version="1.0" encoding="EUC-KR"?>

<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">

<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>

<!-- English Revision: 1.3.2.4 -->

<!-- English Revision: 1.3.2.5 -->



<!--

 Copyright 2004 The Apache Software Foundation