From: Ken Coar Date: Sat, 5 Jul 1997 15:46:46 +0000 (+0000) Subject: Numerous HTML cleanups, some minor rewordings and fixes of typos. X-Git-Tag: APACHE_1_3a1~32 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=884fc002bf1dac2dbb993bb0414b6cd527372cc4;p=thirdparty%2Fapache%2Fhttpd.git Numerous HTML cleanups, some minor rewordings and fixes of typos. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@78519 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html index 29c29ec4ddc..80a0593d86e 100644 --- a/docs/manual/misc/FAQ.html +++ b/docs/manual/misc/FAQ.html @@ -15,7 +15,7 @@

Apache Server Frequently Asked Questions

- $Revision: 1.78 $ ($Date: 1997/07/05 15:01:17 $) + $Revision: 1.79 $ ($Date: 1997/07/05 15:46:46 $)

The latest version of this FAQ is always available from the main @@ -261,8 +261,8 @@ programmers that httpd didn't behave as they wanted it to behave. Apache is an entirely volunteer effort, completely funded by its members, not by commercial sales. -

+
  • How does The Apache Group's work relate to other @@ -422,7 +422,7 @@ the server error log. Sometimes this is enough for you to diagnose & fix the problem yourself (such as file permissions or the like). The default location of the error log is - /usr/local/etc/httpd/logs/error_log, but see the + /usr/local/etc/httpd/logs/error_log, but see the ErrorLog @@ -872,21 +872,23 @@ More information is available.

    +
  • - Can I increase FD_SETSIZE on FreeBSD? + Can I increase FD_SETSIZE on FreeBSD?

    - On FreeBSD 2.2 and older FD_SETSIZE, which limits the number of open - files on the system, is limted to 256. This can limit the number of - virtual hosts you are using; especially if they all use different log - files. Increasing this limit (and recompiling apache) is not enough - (As it is on some platforms, such as Solaris), as you also will have - to recompile libc with the changed setting. + On FreeBSD 2.2 and older FD_SETSIZE, which limits the + number of open + files on the system, is limited to 256. This can restrict the number of + virtual hosts you can use; especially if they all use different log + files. Increasing this limit (and recompiling Apache) is not enough, + as it is on some platforms (such as Solaris), as you also will have + to recompile libc with the changed setting. +

    +

    + On FreeBSD 3.0 the default is 1024, so the problem is lessened.

    -

    - On FreeBSD 3.0 the default is 1024, so the problem is lessened. -

    • @@ -965,6 +967,7 @@ warranty, though, and you'll lose all accumulated UNIX guru points.

    +
  • Why doesn't my ErrorDocument 401 work? @@ -1105,7 +1108,7 @@ >Publishing Pages with PUT.

    -
    • +
  • Why isn't FastCGI included with Apache any more? @@ -1141,7 +1144,7 @@ peer" in my error log?

    - This is a normal message and nothing to be alarmed about. It simply + This is a normal message and nothing about which to be alarmed. It simply means that the client cancelled the connection before it had been completely set up - such as by the end-user pressing the "Stop" button. People's patience being what it is, sites with response-time @@ -1218,6 +1221,7 @@ includes. You need to make sure that the versions of both are matched properly. There are two workarounds, either one will solve the problem:

    +

    +

  • @@ -1335,8 +1340,8 @@ >Apache and Secure Transactions.

    -
    • -
  • +
    • +
  • Why do I get core dumps under HPUX using HP's ANSI C compiler? @@ -1498,19 +1503,27 @@ 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_LDFLAGS line in your Configuration - file, then re-running Configure, should resolve the - problem. (Pre 1.3 Apache uses EXTRA_LFLAGS instead.) + EXTRA_LDFLAGS line in your Configuration + file, then re-running Configure, should resolve the + problem. (Apache versions 1.2.* and earlier use + EXTRA_LFLAGS instead.)

    -

    Note: As of BIND 8.1.1, the bind libraries and files are - installed under /usr/local/bind by default. So you +

    + Note:As of BIND 8.1.1, the bind libraries and files are + installed under /usr/local/bind by default, so you should not run into this problem. Should you want to use the bind resolvers you'll have to add the following to the respective lines: - 

    -  EXTRA_CFLAGS=-I/usr/local/bind/include
-  EXTRA_LDFLAGS=-L/usr/local/bind/lib
-  EXTRA_LIBS=-lbind
-
    +

    +

    +

    +
    EXTRA_CFLAGS=-I/usr/local/bind/include +
    + EXTRA_LDFLAGS=-L/usr/local/bind/lib +
    + EXTRA_LIBS=-lbind     +
    +
    +

  • @@ -1579,12 +1592,18 @@

    -
    deny from all
    - allow from .domain.com
    - AuthType Basic
    - AuthUserFile /usr/local/etc/httpd/conf/htpasswd.users
    - AuthName special directory
    - require valid-user
    +
    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
    @@ -1622,110 +1641,118 @@

    • -
  • When I run it under Linux I get "shmget: function not found", what should I do?

    - Your kernel has been built without SysV IPC support. You will have to - rebuild the kernel with that support enabled (it's under the - "General Setup" submenu). Documention for - kernel building is beyond the scope of this FAQ, you should consult - the Kernel - HOWTO, or the documentation provided with your distribution, - or a Linux - newsgroup/mailing list. As a last resort workaround, you can - comment out the #define HAVE_SHMGET definition in the - LINUX section of - src/conf.h and rebuild the server. This will produce - a server which is slower and less reliable. + Your kernel has been built without SysV IPC support. You will have to + rebuild the kernel with that support enabled (it's under the + "General Setup" submenu). Documentation for + kernel building is beyond the scope of this FAQ; you should consult + the + Kernel HOWTO, + or the documentation provided with your distribution, or a + Linux newsgroup/mailing list. + As a last-resort workaround, you can + comment out the #define HAVE_SHMGET definition in the + LINUX section of + src/conf.h and rebuild the server. This will produce + a server which is slower and less reliable.

    • -
  • Why does my authentification give me a server error?

    - Under normal circumstances, the apache access control modules will - pass unrecognized userids on to the next access control module in - line. Only if the userid is recognized, the password is validated - (or not) will it give the usual success or authentification failed - messages. -

    -

    - However if the last access module in line 'declines' the validation - request (because it has never heard of the userid or because it is not - configured) the http_request handler will give one of the following, - confusing, errors: + Under normal circumstances, the Apache access control modules will + pass unrecognized user IDs on to the next access control module in + line. Only if the user ID is recognized and the password is validated + (or not) will it give the usual success or "authentification + failed" messages. +

    +

    + However, if the last access module in line 'declines' the validation + request (because it has never heard of the user ID or because it is not + configured), the http_request handler will give one of + the following, confusing, errors: +

      -
    • check access -
    • check user. No user file? -
    • check access. No groups file? -
    - This does not mean that you have to add a 'AuthUserFile /dev/null' - line as some magazines suggest ! -

    -

    - The solution is to ensure that at least the last module is authoritative - and CONFIGURED. By default mod_auth is authoritative - and will give an OK/Denied, but only if it is configured with the - proper AuthUserFile. Likewise if a valid group is required. (Remember - that the modules are processed in the reverse order they appear in - your compile-time Configuration file.) -

    -

    - A typical situation for this error is when you are using the - mod_auth_dbm, mod_auth_msql, mod_auth_mysql, mod_auth_anon or - mod_auth_cookie on their own. These are by default not - authoritative, and this will pass the buck on to the (non-existent) next - authentification module when the user ID is not in their respective - database. Just add the appropriate 'XXXAuthoritative yes' line to - the configuration. -

    -

    - In general it is a good idea (though not terribly efficient) to have the - file based mod_auth a module of last resort. This allows you to access - the web server with a few special passwords even if the databases are - down or corrupted. This does cost a file-open/seek/close for each - request in a protected area. -

    +
  • check access +
    • +
  • check user. No user file? +
    • +
  • check access. No groups file? +
    • + +

    + This does not mean that you have to add an + 'AuthUserFile /dev/null' line as some magazines suggest! +

    +

    + The solution is to ensure that at least the last module is authoritative + and CONFIGURED. By default, mod_auth is + authoritative and will give an OK/Denied, but only if it is configured + with the proper AuthUserFile. Likewise, if a valid group + is required. (Remember that the modules are processed in the reverse + order from that in which they appear in your compile-time + Configuration file.) +

    +

    + A typical situation for this error is when you are using the + mod_auth_dbmmod_auth_msql, + , mod_auth_anon or + mod_auth_cookie modules on their own. These are by + default not authoritative, and this will pass the + buck on to the (non-existent) next authentification module when the + user ID is not in their respective database. Just add the appropriate + 'XXXAuthoritative yes' line to the configuration. +

    +

    + In general it is a good idea (though not terribly efficient) to have the + file-based mod_auth a module of last resort. This allows + you to access the web server with a few special passwords even if the + databases are down or corrupted. This does cost a + file open/seek/close for each request in a protected area. +

    -
  • Do I have to keep the (mSQL) authentification information on the same machine? -

    - Some organizations feel very strongly about keeping the authentification - information on a different machine than the webserver. With the - mod_auth_msql, mod_auth_mysql and other SQL modules connecting to - (R)DBMses this is quite well possible. Just configure an explicit host - to contact. -

    -

    - Be aware that with mSQL and Oracle, opening and closing these database - connections is very expensive and time consuming. You might want to - look at the code in the auth_modules and play with the compile time - flags to alleviate this somewhat; if your RDBMS licences alows for it. -

    +

    + Some organizations feel very strongly about keeping the authentification + information on a different machine than the webserver. With the + mod_auth_msql, mod_auth_mysql, and other SQL + modules connecting to (R)DBMses this is quite possible. Just configure + an explicit host to contact. +

    +

    + Be aware that with mSQL and Oracle, opening and closing these database + connections is very expensive and time consuming. You might want to + look at the code in the auth_* modules and play with the + compile time flags to alleviate this somewhat, if your RDBMS licences + allow for it. +

    • -
  • Why is my mSQL authentification terribly slow? -

    - You have probably configured the Host by specificing a FQHN, - and thus the libmsql will use a full blown tcp/ip socket to talk to - the database, rather than a fast internal device. Both the libmsql, - the mSQL faq and the mod_auth_msql documentation warn you about this. If - you have to use different hosts, check out the mod_auth_msql code for - some compile time flags which might, or might not suit you. -

    -
    +

    + You have probably configured the Host by specificing a FQHN, + and thus the libmsql will use a full blown tcp/ip socket to talk to + the database, rather than a fast internal device. The + libmsql, the mSQL FAQ, and the mod_auth_msql + documentation warn you about this. If you have to use different + hosts, check out the mod_auth_msql code for + some compile time flags which might - or might not - suit you. +

    +