From: Ken Coar Date: Sun, 20 Apr 1997 02:43:12 +0000 (+0000) Subject: Removed the hand-edited references, now that enlightened ones X-Git-Tag: APACHE_1_2b9~37 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b75843d1d27307e2a3ebb7e7c4908256d54ccfb2;p=apache Removed the hand-edited references, now that enlightened ones have set my feet upon the path and I, too, can do it automagically. Also cleaned up some formatting for consistency, and added explicit ".html" suffixes to links that were missing them (wouldn't work on servers not using negociation/multiviews). git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77939 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html index 4078d3b1a8..e2c1590552 100644 --- a/docs/manual/misc/FAQ.html +++ b/docs/manual/misc/FAQ.html @@ -8,16 +8,16 @@

Apache Server Frequently Asked Questions

-$Revision: 1.25 $ ($Date: 1997/04/18 20:42:19 $) +$Revision: 1.26 $ ($Date: 1997/04/20 02:43:12 $)

-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. +If you are reading a text-only version 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. These references +do not appear, and are not needed, for the hypertext version.

The Questions

- @@ -102,10 +102,6 @@ reference URLs to be found at the end of the document. -
  • References -
    • @@ -133,7 +129,7 @@ reference URLs to be found at the end of the document. the Internet, according to the Netcraft Survey[1]. + >Netcraft Survey.

    @@ -177,7 +173,7 @@ reference URLs to be found at the end of the document. For an independent assessment, see Web Compare[2]'s + >Web Compare's comparison chart.

    @@ -207,7 +203,7 @@ reference URLs to be found at the end of the document. The Apache project's web site includes a page with a partial list of sites running Apache[3]. + >sites running Apache.

    @@ -239,11 +235,11 @@ reference URLs to be found at the end of the document. Bug reports and suggestions should be sent via the bug report page[4]. + >the bug report page. Other questions should be directed to the comp.infosystems.www.servers.unix[5] + >comp.infosystems.www.servers.unix newsgroup, where some of the Apache team lurk, in the company of many other httpd gurus who should be able to help. @@ -261,12 +257,12 @@ reference URLs to be found at the end of the document. Indeed there is. See the main Apache web site[6]. + >Apache web site. There is also a regular electronic publication called Apache Week[7] + >Apache Week available.

    @@ -279,7 +275,7 @@ reference URLs to be found at the end of the document. project's main web page[6]. + >main web page.

    @@ -304,7 +300,7 @@ reference URLs to be found at the end of the document. the server error log (see the ErrorLog[8] + >ErrorLog directive). Somethimes this is enough for you to diagnose & fix the problem yourself (such as file permissions or the like).

    @@ -315,7 +311,7 @@ reference URLs to be found at the end of the document. the bug database[9]). + >bug database. 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 @@ -334,7 +330,6 @@ reference URLs to be found at the end of the document. 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 @@ -350,7 +345,7 @@ reference URLs to be found at the end of the document. Group know about the problem by logging a bug report[9]. + >logging a bug report.

    If your problem involves the server crashing and generating a core @@ -403,7 +398,7 @@ reference URLs to be found at the end of the document. Apache recognises all files in a directory named as a ScriptAlias[10] + >ScriptAlias 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 @@ -418,7 +413,7 @@ reference URLs to be found at the end of the document. this, you need to use something like the AddHandler[11] + >AddHandler

    directive.
      @@ -434,7 +429,7 @@ reference URLs to be found at the end of the document.
    1. Make sure that the directory location is covered by an Options[12] + >Options declaration that includes the ExecCGI option.
    @@ -488,13 +483,13 @@ reference URLs to be found at the end of the document.
  • Build your server with the mod_include[13] + >mod_include module. This is normally compiled in by default.
  • Make sure your server configuration files have an Options[12] + >Options directive which permits Includes.
  • Make sure that the directory where you want the SSI documents to @@ -503,7 +498,7 @@ reference URLs to be found at the end of the document. with the following AddHandler[11] + >AddHandler directive: 
          AddHandler server-parsed .shtml
@@ -538,12 +533,12 @@ reference URLs to be found at the end of the document.
   mod_expires[14]
+  >mod_expires
   documentation for more details.)  Another possibility is to use the
   XBitHack Full[15]
+  >XBitHack Full
   mechanism, which tells Apache to send (under certain circumstances
   detailed in the XBitHack directive description) a
   Last-Modified header based upon the last modification
@@ -585,7 +580,7 @@ reference URLs to be found at the end of the document.
   content negotiation[16]
+  >content negotiation
   description page.
   
    
   
    
@@ -610,7 +605,7 @@ reference URLs to be found at the end of the document.
   virtual host  needs two file descriptors.  Each 
   Listen[17]
+  >Listen
   directive also needs a file descriptor.  
   
    
   
    
@@ -629,7 +624,7 @@ reference URLs to be found at the end of the document.
    
  • Reduce the number of
        Listen[17]
+       >Listen
        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.
@@ -637,7 +632,7 @@ reference URLs to be found at the end of the document.
    
  • Reduce the number of log files.  You can use 
        mod_log_config[18]
+       >mod_log_config
        to log all requests to a single log file while including the name
        of the virtual host in the log file.
    
    • 
@@ -647,7 +642,7 @@ reference URLs to be found at the end of the document.
        how to do this is available in the
        performance hints[19]
+       >performance hints
        page.
  • "Don't do that" - try to run with fewer virtual hosts @@ -655,7 +650,7 @@ reference URLs to be found at the end of the document.
  • Spread your operation across multiple server processes (using Listen[17] + >Listen for example, but see the first point) and/or ports.
    • @@ -745,7 +740,7 @@ reference URLs to be found at the end of the document. with a method and hostname such as "http://host/foo/bar". See the ErrorDocument[20] + >ErrorDocument documentation for details. This was incorrectly documented in the past.

    @@ -758,7 +753,7 @@ reference URLs to be found at the end of the document. Your Group[21] + >Group directive (probably in conf/httpd.conf) needs to name a group that actually exists in the /etc/group file (or your system's equivalent). @@ -768,190 +763,43 @@ reference URLs to be found at the end of the document.
  • Why does Apache send a cookie on every response?

    - Apache does not send automatically send a cookie on every - response, unless you have re-compiled it with the + Apache does not send automatically send a cookie on every + response, unless you have re-compiled it with the mod_cookies[22] module. - This module was distributed with Apache prior to 1.2. - 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 + HREF="../mod/mod_cookies.html" + >mod_cookies + module. + This module was distributed with Apache prior to 1.2. + 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 mod_usertrack[23], and cookies - have to be specifically enabled with the + HREF="../mod/mod_usertrack.html" + >mod_usertrack, + and cookies + have to be specifically enabled with the CookieTracking[24] - directive. + HREF="../mod/mod_usertrack.html#cookietracking" + >CookieTracking + directive.

  • 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 this 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. +

    + -
    - -

    - 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 -
    [22] -
    -
    http://www.apache.org/docs/mod/mod_cookies -
    -
    [23] -
    -
    http://www.apache.org/docs/mod/mod_usertrack -
    -
    [24] -
    -
    http://www.apache.org/docs/mod/mod_usertrack#cookietracking -
    -
    - +
    +