From: Marc Slemko Date: Mon, 9 Jun 1997 17:04:36 +0000 (+0000) Subject: Merge FAQ updates from HEAD. X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d15ebc772daff68188095ea820815ad7bfc985f0;p=thirdparty%2Fapache%2Fhttpd.git Merge FAQ updates from HEAD. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3@78280 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/APACHE_1_2_X/htdocs/manual/misc/FAQ.html b/APACHE_1_2_X/htdocs/manual/misc/FAQ.html index 94d257d6614..c12dc31e593 100644 --- a/APACHE_1_2_X/htdocs/manual/misc/FAQ.html +++ b/APACHE_1_2_X/htdocs/manual/misc/FAQ.html @@ -15,7 +15,7 @@

Apache Server Frequently Asked Questions

- $Revision: 1.63 $ ($Date: 1997/06/04 11:42:55 $) + $Revision: 1.63.2.1 $ ($Date: 1997/06/09 17:04:36 $)

The latest version of this FAQ is always available from the main @@ -61,17 +61,17 @@ - - - - - + + + + +

@@ -1275,7 +1289,7 @@
  • Why won't Apache compile with my system's cc? - +

    If the server won't compile on your system, it is probably due to one of the following causes: @@ -1370,7 +1384,7 @@

  • Why do Java applets and applications not work - with documents on my Apache server? + with documents on my Apache server?

    The Java Development Kit (JDK) libraries versions 1.0.2 and 1.1 do not @@ -1385,12 +1399,110 @@ adding the following lines to their configuration files:

    -
    BrowserMatch Java1.0 force-response-1.0 +
    BrowserMatch Java1.0 force-response-1.0
    -
    • +
  • + Why do I get an error about an undefined reference to + "__inet_ntoa" or other __inet_* symbols? + +

    + If you have installed BIND-8 + then this is normally due to a conflict between your include files + and your libraries. BIND-8 installs its include files and libraries + /usr/local/include/ and /usr/local/lib/, while + the resolver that comes with your system is probably installed in + /usr/include/ and /usr/lib/. If + your system uses the header files in /usr/local/include/ + before those in /usr/include/ but you do not use the new + resolver library, then the two versions will conflict. +

    +

    + To resolve this, you can either make sure you use the include files + and libraries that came with your system or make sure to use the + new include files and libraries. Adding -lbind to the + EXTRA_LFLAGS line in your Configuration + file, then re-running Configure should resolve the + problem. +

    +
    +
    • +
  • + Why does accessing directories only work when I include + the trailing "/" (eg. http://foo.domain.com/~user/) + but not when I omit it + (eg. http://foo.domain.com/~user)? + +

    + When you access a directory without a trailing "/", Apache needs + to send what is called a redirect to the client to tell it to + add the trailing slash. If it did not do so, relative URLs would + not work properly. When it sends the redirect, it needs to know + the name of the server so that it can include it in the redirect. + There are two ways for Apache to find this out; either it can guess, + or you can tell it. If your DNS is configured correctly, it can + normally guess without any problems. If it is not, however, then + you need to tell it. +

    +

    + Add a ServerName directive + to the config file to tell it what the domain name of the server is. +

    +
    +
    • +
  • + How do I setup Apache to require a username and + password to access certain documents? + +

    + There are several ways to do this; some of the more popular + ones are to use the mod_auth, + mod_auth_db or mod_auth_dbm modules. +

    +

    + For an explaination on how to implement these restrictions, see + ApacheWeek's + Using User Authentication or + + DBM User Authentication tutorials. +

    +
    +
    • +
  • + How do I setup Apache to allow access to certain + documents only if a site is either a local site or + the user supplies a password and username? + +

    + Use the Satsify directive, + in particular the Satsify Any directive to require + that only one of the access restrictions be met. For example, + adding the following configuration to a .htaccess + or server configuration file would restrict access to people who + either are accessing the site from a host under domain.com or + who can supply a valid username and password: +

    +
    +     deny from all
+     allow from .domain.com
+     AuthType Basic
+     AuthUserFile /usr/local/etc/httpd/conf/htpasswd.users
+     AuthName special directory
+     require valid-user
+     satisfy any
+
    +

    See the user authentication + question and the mod_access + module for details on how the above directives work. +

    +
    +
    • + + +