From: Ken Coar Date: Wed, 9 Jul 1997 10:15:42 +0000 (+0000) Subject: Bring the 1.2 FAQ (which is what appears on the Apache site) X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d76a179806499cb9831375ee7d028cbaf0dfc3a1;p=thirdparty%2Fapache%2Fhttpd.git Bring the 1.2 FAQ (which is what appears on the Apache site) up-to-date with the latest changes. This one file, at least, needs to be kept in sync since it doesn't contain any 1.3-isms. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3@78576 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 ef0c292be0d..5181781dd96 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.2.8 $ ($Date: 1997/07/05 17:30:58 $) + $Revision: 1.63.2.9 $ ($Date: 1997/07/09 10:15:42 $)

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

  • Why was Apache created?
  • How does The Apache Group's work relate to - other servers? + other servers?
  • Why the name "Apache"?
    • @@ -116,7 +116,7 @@
  • What does it mean when my CGIs fail with "Premature end of script - headers"? + headers"?
  • How do I enable SSI (parsed HTML)?
    • @@ -147,7 +147,7 @@
  • Why does Apache send a cookie on every response?
    • -
  • Why don't my cookies work, I even compiled in +
  • Why don't my cookies work, I even compiled in mod_cookies?
  • Why do my Java app[let]s give me plain text @@ -191,7 +191,7 @@
  • How do I add browsers and referrers to my logs?
    • -
  • Why do I get an error about an undefined +
  • Why do I get an error about an undefined reference to "__inet_ntoa" or other __inet_* symbols?
    • @@ -227,8 +227,6 @@

    The Answers

    -

    -

    Background

    @@ -259,7 +257,7 @@

    To address the concerns of a group of WWW providers and part-time httpd programmers that httpd didn't behave as they wanted it to behave. - Apache is an entirely volunteer effort, completely funded by its + Apache is an entirely volunteer effort, completely funded by its members, not by commercial sales.

    @@ -293,7 +291,7 @@ For an independent assessment, see Web Compare's + >Web Compare's comparison chart.

    @@ -419,10 +417,10 @@

    Apache tries to be helpful when it encounters a problem. In many cases, it will provide some details by writing one or messages to - the server error log. Sometimes this is enough for you to diagnose + 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 + The default location of the error log is + /usr/local/etc/httpd/logs/error_log, but see the ErrorLog @@ -512,7 +510,7 @@ NCSA httpd 1.4 and NCSA httpd 1.5.

    - NCSA httpd appears to be moving toward adding experimental features + NCSA httpd appears to be moving toward adding experimental features which are not generally required at the moment. Some of the experiments will succeed while others will inevitably be dropped. The Apache philosophy is to add what's needed as and when it is needed. @@ -579,7 +577,7 @@

  • What does it mean when my CGIs fail with "Premature end of script headers"? - +

    It means just what it says: the server was expecting a complete set of HTTP headers (one or more followed by a blank line), and didn't get @@ -596,7 +594,7 @@

    The second most common cause of this (aside from people not outputting the required headers at all) is a result of an interaction - with Perl's output buffering. To make Perl flush its buffers + with Perl's output buffering. To make Perl flush its buffers after each output statement, insert the following statements around the print or write statements that send your HTTP headers: @@ -617,7 +615,7 @@

    - This is generally only necessary when you are calling external + This is generally only necessary when you are calling external programs from your script that send output to stdout, or if there will be a long delay between the time the headers are sent and the actual content starts being emitted. To maximise performance, you should @@ -627,7 +625,7 @@

    If your script isn't written in Perl, do the equivalent thing for - whatever language you are using (e.g., for C, call + whatever language you are using (e.g., for C, call fflush() after writing the headers).

    @@ -639,7 +637,7 @@ SSI (an acronym for Server-Side Include) directives allow static HTML documents to be enhanced at run-time (e.g., when delivered to a client by Apache). The format of SSI directives is covered - in the mod_include manual; + in the mod_include manual; suffice it to say that Apache supports not only SSI but xSSI (eXtended SSI) directives.

    @@ -766,7 +764,7 @@ HREF="../mod/mod_proxy.html" >proxy module. If compiled - in, this will make Apache act as a caching-proxy server. + in, this will make Apache act as a caching-proxy server.

    • @@ -776,7 +774,7 @@

    "Multiviews" is the general name given to the Apache server's ability to provide language-specific document variants in - response to a request. This is documented quite thoroughly in the + response to a request. This is documented quite thoroughly in the

    - You are probably running into resource limitations in your - operating system. The most common limitation is the - per-process limit on file descriptors, - which is almost always the cause of problems seen when adding - virtual hosts. Apache often does not give an intuitive error - message because it is normally some library routine (such as - gethostbyname()) which needs file descriptors and - doesn't complain intelligibly when it can't get them. + You are probably running into resource limitations in your + operating system. The most common limitation is the + per-process limit on file descriptors, + which is almost always the cause of problems seen when adding + virtual hosts. Apache often does not give an intuitive error + message because it is normally some library routine (such as + gethostbyname()) which needs file descriptors and + doesn't complain intelligibly when it can't get them.

    Each log file requires a file descriptor, which means that if you are using separate access and error logs for each virtual host, each - virtual host needs two file descriptors. Each + virtual host needs two file descriptors. Each Listen - directive also needs a file descriptor. + directive also needs a file descriptor.

    Typical values for <n> that we've seen are in @@ -830,17 +828,17 @@ Listen - directives. If there are no other servers running on the machine + directives. If there are no other servers running on the machine on the same port then you normally don't need any Listen directives at all. By default Apache listens to all addresses on port 80. -

  • Reduce the number of log files. You can use +
  • Reduce the number of log files. You can use mod_log_config to log all requests to a single log file while including the name - of the virtual host in the log file. You can then write a + of the virtual host in the log file. You can then write a script to split the logfile into separate files later if necessary.
    • @@ -879,7 +877,7 @@

    On FreeBSD 2.2 and older FD_SETSIZE, which limits the - number of open + 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, @@ -974,7 +972,7 @@

    You need to use it with a URL in the form "/foo/bar" and not one with a method and - hostname such as "http://host/foo/bar". See the + hostname such as "http://host/foo/bar". See the ErrorDocument @@ -1002,7 +1000,7 @@

    Apache does not send automatically send a cookie on every - response, unless you have re-compiled it with the + response, unless you have re-compiled it with the mod_cookies @@ -1011,11 +1009,11 @@ This module may help track users, and uses cookies to do this. If you are not using the data generated by mod_cookies, do not compile it into Apache. Note that in 1.2 this module was renamed - to the more correct name + to the more correct name mod_usertrack, - and cookies + and cookies have to be specifically enabled with the

    -
    BrowserMatch Java1.0 force-response-1.0 +
    BrowserMatch Java1.0 force-response-1.0 +
    + BrowserMatch JDK/1.0 force-response-1.0

    @@ -1130,7 +1130,7 @@
  • Why am I getting "httpd: could not set socket option TCP_NODELAY" in my error log? - +

    This message almost always indicates that the client disconnected before Apache reached the point of calling setsockopt() @@ -1142,7 +1142,7 @@

  • Why am I getting "connection reset by peer" in my error log? - +

    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 @@ -1224,7 +1224,7 @@