You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by nd...@apache.org on 2004/05/21 20:52:13 UTC
cvs commit: httpd-2.0/docs/manual/mod mod_auth_ldap.html.en mod_file_cache.html.en mod_file_cache.xml
nd 2004/05/21 11:52:13
Modified: docs/manual/mod mod_auth_ldap.html.en mod_file_cache.html.en
mod_file_cache.xml
Log:
update transformation
Revision Changes Path
1.26 +12 -10 httpd-2.0/docs/manual/mod/mod_auth_ldap.html.en
Index: mod_auth_ldap.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_auth_ldap.html.en,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -u -r1.25 -r1.26
--- mod_auth_ldap.html.en 3 Apr 2004 16:24:57 -0000 1.25
+++ mod_auth_ldap.html.en 21 May 2004 18:52:12 -0000 1.26
@@ -315,7 +315,8 @@
<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 @@
<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 @@
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,7 @@
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 />
+AuthLDAPURL ldap://ldap1.airius.com:389/ou=People, o=Airius?uid?sub?(objectClass=*)<br />
require valid-user
</code></p></div>
</li>
@@ -367,7 +369,7 @@
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 +384,7 @@
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 +393,7 @@
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 +405,7 @@
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 +421,7 @@
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>
1.21 +1 -1 httpd-2.0/docs/manual/mod/mod_file_cache.html.en
Index: mod_file_cache.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_file_cache.html.en,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -u -r1.20 -r1.21
--- mod_file_cache.html.en 25 Apr 2004 22:53:11 -0000 1.20
+++ mod_file_cache.html.en 21 May 2004 18:52:12 -0000 1.21
@@ -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>
1.8 +2 -2 httpd-2.0/docs/manual/mod/mod_file_cache.xml
Index: mod_file_cache.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_file_cache.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -u -r1.7 -r1.8
--- mod_file_cache.xml 17 Apr 2004 10:49:22 -0000 1.7
+++ mod_file_cache.xml 21 May 2004 18:52:12 -0000 1.8
@@ -125,7 +125,7 @@
</section>
<note><title>Note</title>
- <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
<directive module="core">Include</directive> directive, and consider
this command:</p>