Received: by taz.hyperreal.com (8.8.4/V2.0) id IAA21578;
 Thu, 27 Mar 1997 08:30:05 -0800 (PST)
Received: by taz.hyperreal.com (8.8.4/V2.0) id IAA21569;
 Thu, 27 Mar 1997 08:30:01 -0800 (PST)
Date: Thu, 27 Mar 1997 08:30:01 -0800 (PST)
Message-Id: <199703271630.IAA21569@taz.hyperreal.com>
From: "R. P. C. Rodgers" <rodgers@nlm.nih.gov>
Reply-To: "R. P. C. Rodgers" <rodgers@nlm.nih.gov>
To: apache-bugdb@apache.org
Cc: apache-bugdb@apache.org
Subject: config/270: access.conf does not support access from a single host
 specified by hostname
In-Reply-To: Your message of Thu, 27 Mar 1997 08:22:38 -0800 (PST)
	<199703271622.IAA19027@taz.hyperreal.com>
Sender: apache-bugdb-owner@apache.org
Precedence: bulk


>Number:         270
>Category:       config
>Synopsis:       access.conf does not support access from a single host specified by hostname
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Mar 27 08:30:01 1997
>Originator:     rodgers@nlm.nih.gov
>Organization:
apache
>Release:        1.2b7
>Environment:
Solaris 2.5.1, gcc 2.7.2
>Description:
The conf/access.conf file is used to configure access to the server.
Although the online manual suggests that a series of configuration
commands of the form:
   deny from all
   allow from ugweb.cs.ualberta.ca
should be possible, it does not work as described (access is denied to host
ugweb), whereas:
   deny from all
   allow from .cs.ualberta.ca
does allow access to host ugweb, as well as all of its peers in the domain
cs.ualberta.ca.  Preceding the hostname in the first example with "." does
not function as a work-around.  Either the document should be clarified, or
(preferably) the code modified.
>How-To-Repeat:
The above example should suffice
>Fix:
Hack the access code
>Audit-Trail:
>Unformatted: