From: Ken Coar Date: Sat, 26 Apr 1997 12:21:14 +0000 (+0000) Subject: Added Q&A concerning access restriction by host/domain name, X-Git-Tag: APACHE_1_2b9~4 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1329fb92f95f4d140825e70f86df0997a0e2e018;p=apache Added Q&A concerning access restriction by host/domain name, and cleaned up a couple of nit. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@78025 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html index 40b63846a8..c38a899beb 100644 --- a/docs/manual/misc/FAQ.html +++ b/docs/manual/misc/FAQ.html @@ -8,7 +8,7 @@

Apache Server Frequently Asked Questions

- $Revision: 1.43 $ ($Date: 1997/04/26 06:58:39 $) + $Revision: 1.44 $ ($Date: 1997/04/26 12:21:14 $)

The latest version of this FAQ is always available from the main @@ -25,7 +25,7 @@ - + @@ -42,8 +42,6 @@ - - @@ -127,7 +125,7 @@

  • Why does Apache send a cookie on every response?
  • Why don't my cookies work, I even compiled in - mod_cookies? + mod_cookies?
  • Why do my Java app[let]s give me plain text when I request an URL from an Apache server? @@ -150,6 +148,9 @@
  • The errorlog says Apache dumped core, but where's the dump file?
    • +
  • Why isn't restricting access by host or domain name + working correctly? +
  • Why doesn't Apache include SSL?
    • @@ -254,7 +255,7 @@

    The Apache project's web site includes a page with a partial list of sites running Apache.

    @@ -286,7 +287,7 @@ be swamped by a flood of trivial questions that can be resolved elsewhere. Bug reports and suggestions should be sent via the bug report page. Other questions should be directed to the mod_cookies, do + not compile it into Apache. Note that in 1.2 this module was renamed + to the more correct name mod_usertrack, @@ -888,16 +889,21 @@
  • - Why don't my cookies work, I even compiled in mod_cookies? + Why don't my cookies work, I even compiled in + mod_cookies?

    - Firstly, you do not need to compile in mod_cookies in order - for your scripts to work (see the previous question - for more about mod_cookies). Apache passes on your Set-Cookie header - fine, with or without this module. If cookies do not work it will - be because your script does not work properly or your browser does - not use cookies or is not set-up to accept them. + Firstly, you do not need to compile in + mod_cookies in order for your scripts to work (see the + previous question + for more about mod_cookies). Apache passes on your + Set-Cookie header fine, with or without this module. If + cookies do not work it will be because your script does not work + properly or your browser does not use cookies or is not set-up to + accept them.

    • @@ -1089,6 +1095,50 @@

    +
  • + Why isn't restricting access by host or domain name + working correctly? + +

    + Two of the most common causes of this are: +

    +
      +
    1. 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. + The usual reason for this is that Host.FooBar.Com is + actually an alias for another name, and when Apache performs the + address-to-name lookup it's getting the real name, not + Host.FooBar.Com. You can verify this by checking the + reverse lookup yourself. The easiest way to work around it is to + specify the correct host name in your configuration. +
      2. +
    2. Inadequate checking and verification in your + configuration of Apache +
      + If you intend to perform access checking and restriction based upon + the client's host or domain name, you really need to configure + Apache to double-check the origin information it's supplied. You do + this by adding the -DMAXIMUM_DNS clause to the + EXTRA_CFLAGS definition in your + Configuration file. For example: +
      +
      EXTRA_CFLAGS=-DMAXIMUM_DNS +
      +
      +

      + This will cause Apache to be very paranoid about making sure a + particular host address is really assigned to the name it + claims to be. Note that this can incur a significant + performance penalty, however, because of all the name resolution + requests being sent to a nameserver. +

      +
      3. +
    +
    +
  • Why doesn't Apache include SSL? @@ -1097,7 +1147,7 @@ governments have restrictions upon the import, export, and use of encryption technology. If Apache included SSL in the base package, its distribution would involve all sorts of legal and bureaucratic - issues., and it would no longer be freely available. Also, some of + issues, and it would no longer be freely available. Also, some of the technology required to talk to current clients using SSL is patented by RSA Data Security, who restricts its use without a license.