httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_authz_host.xml mod_authz_host.html.en
Date Thu, 31 Jul 2003 18:56:40 GMT
slive       2003/07/31 11:56:40

  Modified:    docs/manual/mod mod_authz_host.xml mod_authz_host.html.en
  Log:
  As suggested by Marc Slemko, document the double reverse
  effect of Allow/Deny.
  
  Revision  Changes    Path
  1.6       +10 -6     httpd-2.0/docs/manual/mod/mod_authz_host.xml
  
  Index: mod_authz_host.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_authz_host.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -d -b -u -r1.5 -r1.6
  --- mod_authz_host.xml	11 Apr 2003 01:25:52 -0000	1.5
  +++ mod_authz_host.xml	31 Jul 2003 18:56:40 -0000	1.6
  @@ -82,12 +82,16 @@
         </example>
         <p>Hosts whose names match, or end in, this string are allowed
         access. Only complete components are matched, so the above
  -      example will match <code>foo.apache.org</code> but it will
  -      not match <code>fooapache.org</code>. This configuration will
  -      cause the server to perform a reverse DNS lookup on the
  -      client IP address, regardless of the setting of the <directive
  -      module="core">HostnameLookups</directive>
  -      directive.</p></dd>
  +      example will match <code>foo.apache.org</code> but it will not
  +      match <code>fooapache.org</code>. This configuration will cause
  +      Apache to perform a double reverse DNS lookup on the client IP
  +      address, regardless of the setting of the <directive
  +      module="core">HostnameLookups</directive> directive.  It will do
  +      a reverse DNS lookup on the IP address to find the associated
  +      hostname, and then do a forward lookup on the hostname to assure
  +      that it matches the original IP address.  Only if the forward
  +      and reverse DNS are consistent and the hostname matches will
  +      access be allowed.</p></dd>
   
         <dt>A full IP address</dt>
   
  
  
  
  1.11      +9 -5      httpd-2.0/docs/manual/mod/mod_authz_host.html.en
  
  Index: mod_authz_host.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_authz_host.html.en,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -d -b -u -r1.10 -r1.11
  --- mod_authz_host.html.en	29 May 2003 16:13:13 -0000	1.10
  +++ mod_authz_host.html.en	31 Jul 2003 18:56:40 -0000	1.11
  @@ -106,11 +106,15 @@
         </code></p></div>
         <p>Hosts whose names match, or end in, this string are allowed
         access. Only complete components are matched, so the above
  -      example will match <code>foo.apache.org</code> but it will
  -      not match <code>fooapache.org</code>. This configuration will
  -      cause the server to perform a reverse DNS lookup on the
  -      client IP address, regardless of the setting of the <code class="directive"><a
href="../mod/core.html#hostnamelookups">HostnameLookups</a></code>
  -      directive.</p></dd>
  +      example will match <code>foo.apache.org</code> but it will not
  +      match <code>fooapache.org</code>. This configuration will cause
  +      Apache to perform a double reverse DNS lookup on the client IP
  +      address, regardless of the setting of the <code class="directive"><a href="../mod/core.html#hostnamelookups">HostnameLookups</a></code>
directive.  It will do
  +      a reverse DNS lookup on the IP address to find the associated
  +      hostname, and then do a forward lookup on the hostname to assure
  +      that it matches the original IP address.  Only if the forward
  +      and reverse DNS are consistent and the hostname matches will
  +      access be allowed.</p></dd>
   
         <dt>A full IP address</dt>
   
  
  
  

Mime
View raw message