From b8f5b06e2da09fcce721b4a37ba73b338310e00f Mon Sep 17 00:00:00 2001 From: Ken Coar Date: Tue, 15 Apr 1997 21:17:46 +0000 Subject: [PATCH] More cleanup, primarily to get into a format that's equally usable as text (e.g., from a newsgroup) and as hypertext. Addition of a `references' section, and `footnotes' in a manner similar to _Apache Week_'s text format. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77903 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/misc/FAQ.html | 260 +++++++++++++++++++++++++++++++------- 1 file changed, 212 insertions(+), 48 deletions(-) diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html index c6a1677a7f..59c1f5bc90 100644 --- a/docs/manual/misc/FAQ.html +++ b/docs/manual/misc/FAQ.html @@ -8,7 +8,12 @@

Apache Server Frequently Asked Questions

-$Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) +$Revision: 1.24 $ ($Date: 1997/04/15 21:17:46 $) +

+

+Throughout the text of this FAQ you may find numbers enclosed in +brackets (such as "[12]"). These refer to the list of +reference URLs to be found at the end of the document.

The Questions

@@ -92,6 +97,10 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) +
  • References +
    • @@ -119,7 +128,7 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) the Internet, according to the Netcraft Survey. + >Netcraft Survey[1].

    @@ -163,7 +172,8 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) For an independent assessment, see http://webcompare.iworld.com/compare/chart.html. + >Web Compare[2]'s + comparison chart.

    Apache has been shown to be substantially faster than many other @@ -189,11 +199,10 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) release patches and new versions as soon as they are available.

    - See + The Apache project's web site includes a page with a partial list of http://www.apache.org/info/apache_users.html - for a partial list of sites running Apache. + >sites running Apache[3].

    @@ -205,7 +214,7 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $)
  • to continue as a public domain HTTP server,
  • to keep up with advances in HTTP protocol and web developments in - general + general,
  • to collect suggestions for fixes/improvements from its users,
    • @@ -225,11 +234,11 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) Bug reports and suggestions should be sent via the bug report page . + >the bug report page[4]. Other questions should be directed to the comp.infosystems.www.servers.unix + >comp.infosystems.www.servers.unix[5] newsgroup, where some of the Apache team lurk, in the company of many other httpd gurus who should be able to help. @@ -244,16 +253,16 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) NAME="more" >Is there any more information available on Apache?

    - Indeed there is. See the main Apache Web site at + Indeed there is. See the main http://www.apache.org/. - There is also a regular electronic publication called Apache - Week available; you can find out more about this at + >Apache web site[6]. + There is also a regular electronic publication called http://www.apacheweek.com/. + >Apache Week[7] + available.

    @@ -261,10 +270,11 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) NAME="where" >Where can I get Apache?

    - You can find the source for Apache at the main web page, + You can find out how to download the source for Apache at the + project's http://www.apache.org/. + >main web page[6].

    @@ -289,7 +299,7 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) the server error log (see the ErrorLog + >ErrorLog[8] directive). Somethimes this is enough for you to diagnose & fix the problem yourself (such as file permissions or the like).

    @@ -297,10 +307,10 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $)
  • Check the Apache bug database

    Most problems that get reported to The Apache Group are recorded in - the bug database (available at + the http://www.apache.org/bugdb.cgi). + >bug database[9]). Please check the existing reports, open and closed, before adding one. If you find that your issue has already been reported, please don't add @@ -319,6 +329,7 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) comp.infosystems.www.servers.unix + [5] newsgroup. Many Apache users, and some of the developers, can be found roaming its virtual halls, so it is suggested that you seek wisdom there. The chances are good that you'll get a faster answer @@ -331,10 +342,10 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $)

    If you've gone through those steps above that are appropriate and have obtained no relief, then please do let The Apache - Group know about the problem by logging a bug report (see + Group know about the problem by http://www.apache.org/bugdb.cgi). + >logging a bug report[9].

    If your problem involves the server crashing and generating a core @@ -387,7 +398,7 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) Apache recognises all files in a directory named as a ScriptAlias + >ScriptAlias[10] as being eligible for execution rather than processing as normal documents. This applies regardless of the file name, so scripts in a ScriptAlias directory don't need to be named @@ -398,15 +409,18 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $)

    To persuade Apache to execute scripts in other locations, such as in directories where normal documents may also live, you must tell it how - to recognise them - and also that it's okey to execute them. + to recognise them - and also that it's okey to execute them. For + this, you need to use something like the + AddHandler[11]

    + directive.
    1. In an appropriate section of your server configuration files, add a line such as 
      -     AddHandler cgi-script .cgi
+     AddHandler cgi-script .cgi
      The server will then recognise that all files in that location (and its logical descendants) that end in ".cgi" @@ -415,7 +429,7 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $)
    2. Make sure that the directory location is covered by an Options + >Options[12] declaration that includes the ExecCGI option.
    @@ -469,23 +483,25 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $)
  • Build your server with the mod_include + >mod_include[13] module. This is normally compiled in by default.
  • Make sure your server configuration files have an Options + >Options[12] directive which permits Includes.
  • Make sure that the directory where you want the SSI documents to live is covered by the "server-parsed" content handler, either explicitly or in some ancestral location. That can be done - with the following: + with the following + AddHandler[11] + directive: 
    -     AddHandler server-parsed .shtml
+     AddHandler server-parsed .shtml
    This indicates that all files ending in ".shtml" in that location (or its descendants) should be parsed. Note that using @@ -517,12 +533,12 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) mod_expires + >mod_expires[14] documentation for more details.) Another possibility is to use the XBitHack Full + >XBitHack Full[15] mechanism, which tells Apache to send (under certain circumstances detailed in the XBitHack directive description) a Last-Modified header based upon the last modification @@ -564,7 +580,7 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) content negotiation + >content negotiation[16] description page.

    @@ -587,8 +603,10 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) Each log file requires a file descriptor, which means that if you are using seperate access and error logs for each virtual host each virtual host needs two file descriptors. Each - Listen directive also needs - a file descriptor. + Listen[17] + directive also needs a file descriptor.

    Typical values for <n> that we've seen are in @@ -603,27 +621,37 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) As to what you can do about this:

      -
    1. Reduce the number of Listen +
    2. Reduce the number of + Listen[17] directives. If there are no other servers running on the machine and all of them are running on the same port, you normally don't need any Listen directives at all.
    3. Reduce the number of log files. You can use - log_mod_config to log - all requests to a single log file while including the name + mod_log_config[18] + to log all requests to a single log file while including the name of the virtual host in the log file.
    4. Increase the number of file descriptors available to the server (see your system's documentation on the limit or ulimit commands). For some systems, information on - how to do this is available in the performance - hints page. + how to do this is available in the + performance hints[19] + page.
    5. "Don't do that" - try to run with fewer virtual hosts
    6. Spread your operation across multiple server processes (using - Listen for example, - but see the first point) and/or ports + Listen[17] + for example, but see the first point) and/or ports.

    @@ -710,8 +738,10 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $)

    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 - ErrorDocument documentation - for details. This was incorrectly documented in the past. + ErrorDocument[20] + documentation for details. This was incorrectly documented in the past.

    • @@ -723,7 +753,7 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $) Your Group + >Group[21] directive (probably in conf/httpd.conf) needs to name a group that actually exists in the /etc/group file (or your system's equivalent). @@ -731,6 +761,140 @@ $Revision: 1.23 $ ($Date: 1997/04/12 22:52:43 $)
    +
    + +

    + References +

    +     +
    +
    [1] +
    +
    http://www.netcraft.com/Survey/ +
    +
    [2] +
    +
    http://webcompare.iworld.com/compare/chart.html +
    +
    [3] +
    +
    http://www.apache.org/info/apache_users.html +
    +
    [4] +
    +
    http://www.apache.org/bug_report.html +
    +
    [5] +
    +
    news:comp.infosystems.www.servers.unix +
    +
    [6] +
    +
    http://www.apache.org/ +
    +
    [7] +
    +
    http://www.apacheweek.com/ +
    +
    [8] +
    +
    http://www.apache.org/docs/mod/core.html#errorlog +
    +
    [9] +
    +
    http://www.apache.org/bugdb.cgi +
    +
    [10] +
    +
    http://www.apache.org/docs/mod/mod_alias.html#scriptalias +
    +
    [11] +
    +
    http://www.apache.org/docs/mod/mod_mime.html#addhandler +
    +
    [12] +
    +
    http://www.apache.org/docs/mod/core.html#options +
    +
    [13] +
    +
    http://www.apache.org/docs/mod/mod_include.html +
    +
    [14] +
    +
    http://www.apache.org/docs/mod/mod_expires.html +
    +
    [15] +
    +
    http://www.apache.org/docs/mod/mod_include.html#xbithack +
    +
    [16] +
    +
    http://www.apache.org/docs/content-negotiation.html +
    +
    [17] +
    +
    http://www.apache.org/docs/mod/core.html#listen +
    +
    [18] +
    +
    http://www.apache.org/docs/mod/mod_log_config.html +
    +
    [19] +
    +
    http://www.apache.org/docs/misc/perf.html +
    +
    [20] +
    +
    http://www.apache.org/docs/mod/core.html#errordocument +
    +
    [21] +
    +
    http://www.apache.org/docs/mod/core.html#group +
    +
    -- 2.40.0