You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Ash Nallawalla <as...@melbpc.org.au> on 1997/12/07 23:18:57 UTC
general/1526: Minor error in FAQ 36
>Number: 1526
>Category: general
>Synopsis: Minor error in FAQ 36
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: doc-bug
>Submitter-Id: apache
>Arrival-Date: Sun Dec 7 14:20:00 PST 1997
>Last-Modified:
>Originator: ash@melbpc.org.au
>Organization:
apache
>Release: N/A
>Environment:
N/A
>Description:
FAQ 36 says:
Why isn't restricting access by host or domain name working correctly?
Two of the most common causes of this are:
An error, inconsistency, or unexpected mapping in the DNS registration
This happens frequently: your configuration restricts access to Host.FooBar.Com, but you can't get in from that host.
>How-To-Repeat:
Read FAQ
>Fix:
Change the last sentence above to read:
"but you can get in from that host. "
%0
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]