From: Lars Eilebrecht <lars@apache.org>
Date: Sun, 19 Dec 1999 18:46:59 +0000 (+0000)
Subject: Uhm... forgot require directive...
X-Git-Tag: 1.3.10~79
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8467d26cce3a89e2d44669298227ee5d5eab248c;p=apache

Uhm... forgot require directive...


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84322 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html
index 24d81fb128..9dd02ba0b1 100644
--- a/docs/manual/mod/core.html
+++ b/docs/manual/mod/core.html
@@ -2393,7 +2393,9 @@ Access controls which are applied in this way are effective for
 desired.</STRONG> If you wish to apply access controls only to
 specific methods, while leaving other methods unprotected, then place
 the <CODE>require</CODE> statement into a <A
-HREF="#limit">&lt;Limit&gt;</A> section<P><HR>
+HREF="#limit">&lt;Limit&gt;</A> section<P>
+<P>See also <A HREF="#satisfy">Satisfy</A> and <A HREF="mod_access.html">mod_access</A>.
+<HR>
 
 <H2><A NAME="resourceconfig">ResourceConfig directive</A></H2>
 <!--%plaintext &lt;?INDEX {\tt ResourceConfig} directive&gt; -->
@@ -2599,7 +2601,8 @@ they either pass the host restriction or enter a valid username and
 password. This can be used to password restrict an area, but to let
 clients from particular addresses in without prompting for a password.
 <P>
-See also <A HREF="mod_access.html">mod_access</A>.
+See also <A HREF="#require">require</A> and 
+<A HREF="mod_access.html">mod_access</A>.
 
 <P><HR>
 
diff --git a/docs/manual/mod/mod_access.html b/docs/manual/mod/mod_access.html
index a0d17ca15e..81c7e8d3db 100644
--- a/docs/manual/mod/mod_access.html
+++ b/docs/manual/mod/mod_access.html
@@ -29,7 +29,8 @@ hostname or IP address.
 <LI><A HREF="#order">order</A>
 </UL>
 <DL>
-<DD>See also <A HREF="core.html#satisfy">Satisfy</A>.
+<DD>See also <A HREF="core.html#satisfy">Satisfy</A>
+    and <A HREF="core.html#require">require</A>.
 </DL>
 <HR>