  Apache Web Server


  This is the main configuration menu for the WWW-server Apache.  Apache
  provides many configuration options and is extendable with third-party
  modules.  As a result _L_i_n_u_x_c_o_n_f can only control some of Apache's
  functionality -- the most important parts.  In this window, you con-
  trol the server-wide configuration.  You can also set default values,
  which can be overridden, for specific parts of the Web server con-
  tents.

  11..  AAddmmiinniissttrraattoorr eemmaaiill

  This address will be included in error messages to Web clients
  (browsers), for example, when pages can't be found.  This email
  address is usually webmaster@domain.


  22..  DDoommaaiinn IIPP aaddddrreessss

  If you want to let several virtual domains share a single IP address,
  you must enter that address here.


  33..  SSeerrvveerr nnaammee

  The name of the Web server.  If name resolving works (using DNS or
  /etc/hosts) you should not have to enter anything here.  However, if
  Apache is unable to determine the hostname at startup, or if the
  hostname is not the same as the official name of the Web server, you
  need to provide it yourself.


  44..  SSeerrvveerr aalliiaasseess

  Alias names for the Web server.  Names _m_u_s_t _n_o_t be provided here in
  the main configuration; this is only for virtual domains.


  55..  DDooccuummeenntt rroooott

  The directory (in the real filesystem) from which your Web server will
  be serving most of its Web pages.

  For example: If you  set the document root to /home/httpd/html, then
  accesses to http://your.webserver.com/index.html would return the file
  /home/httpd/html/index.html.  An access to
  http://your.webserver.com/foo/gazonk.gif would return
  /home/httpd/html/foo/gazonk.gif.


  66..  EErrrroorr lloogg

  The path to the log file for error messages.  Usually, it is
  logs/error_log, which is relative to the ServerRoot.  Often the
  directory logs in ServerRoot is a symbolic link to /var/log/httpd.
  Then the log path above would result in error messages being logged to
  /var/log/httpd/error_log.

  You should monitor this log after reconfiguring, since most
  configuration errors are logged here (Linuxconf, sadly, catches only a
  few of them.)  Additionally, any failed accesses by clients (non-
  existent pages, failed authorization and so on) are also logged here.


  77..  TTrraannssffeerr lloogg

  All accesses to the Web server will be logged in this file.  Usually,
  it is logs/access_log.  Every access is logged on a single line in the
  Common Log Format (most Web logfile analyzers understand this format).


  88..  AAggeenntt lloogg

  The browsers used to access the Web server are logged in this file.


  99..  RReeffeerreerr lloogg

  If an access was the result of a user following a link from some page
  to the accessed page, then the other, referring page is logged in this
  file.


  1100..  SSccrriipptt AAlliiaass

  Provides the location for CGI programs.  This should be two paths,
  separated by whitespace.  The first path is the path used in URL that
  triggers execution of a CGI program; the second path is where those
  CGI programs are stored in the real filesystem.

  For example, if the script alias is /cgi-bin/home/httpd/cgi then a
  request for http://your.webserver.com/cgi-bin/feedback.py would
  execute and return the output of /home/httpd/cgi/feedback.py.


  1111..  UUsseerr

  The user the web server should run as.  This means that the Web server
  can only read and write those files which that a user has rights to
  read or write, respectively.  Therefore, this should be set to a user
  with very low privileges, for example, nobody.

  An even better idea is to create a user specifically for the Web
  server.  This is very important, if you want to let the Web server
  write files in some directory, since the user "nobody" should not have
  privileges to write files anywhere except in /tmp.


  1122..  GGrroouupp

  The group the Web server should run as.  See the discussion of User
  above, but apply it to groups instead of users.


  1133..  TTuunniinngg


  1133..11..  LLiisstteenn oonn ppoorrtt

  The TCP port on which the Web server should listen for HTTP requests.
  The standard port for HTTP is 80, so if you use another port you need
  to include it in the URL.  For example, if you let your Web server
  listen on port 8000, then the URL to your server would be
  http://your.webserver.com:8000/.


  1133..22..  PPiidd ffiillee

  The Web server stores the PID of its main process in this file.  You
  will probably not need to modify this.


  1133..33..  TTiimmee oouutt

  How many seconds the Web server will wait for a request to be sent
  after a client has connected to the server.  If a client connects but
  doesn't send any request, it will be disconnected after this amount of
  time.


  1133..44..  HHoosstt nnaammee llooookkuuppss

  Whether the Web server should attempt to find out the host names of
  connecting clients.  If this is disabled, only the IP address of the
  client will be logged.  If you enable it, the host name will be logged
  instead, if it is possible to resolve the IP address to a name.

  There are two disadvantages of enabling host name lookups.  Every
  access results in network traffic to resolve the address, and the
  accessed page can't be returned until after the address is resolved,
  so your Web server will be slowed down.  If you're interested in
  seeing the host names of machines accessing your Web server, a better
  idea is to let a log file analyzer resolve the addresses as it
  processes the log files.


  1144..  FFeeaattuurreess

  This controls various features beyond simply returning the contents of
  a file.  In most cases this is controlled by the sub-directory specs
  instead.


  1144..11..  SSeerrvveerr ssiiddee iinncclluuddeess

  If enabled, files with the extension .shtml are processed to expand
  server side includes tags before the results are returned to the
  client.


  1144..22..  IInncclluuddeessNNOOEEXXEECC

  Also enables server side includes, but the SSI tag #exec and
  #include:ing CGI-scripts are disabled.


  1144..33..  MMaayy eexxeeccuuttee CCGGII

  Allow CGI scripts.  Usually only enabled in the sub-directory spec for
  the CGI directory.


  1144..44..  IInnddeexxeess

  When accessing an URL ending in a directory the file index.html in
  that directory is returned.  If that file doesn't exist, and this
  option is enabled, a directory listing is returned.  If this option is
  disabled, a 404 Not found is returned instead.


  1144..55..  MMaayy ffoollllooww ssyymmlliinnkkss

  If an accessed directory or file is a symbolic link, the access will
  only be allowed if this feature is enabled.


  1144..66..  FFoollllooww ssyymmlliinnkk iiff oowwnneerr mmaattcchheess

  As above, but additionally, the owner of the symbolic link and its
  target file must be the same.  This allows users to have symbolic
  links to their own files, but not to sensitive system files like
  /etc/passwd.


  1144..77..  MMuullttiivviieewwss

  Multiviews allows the client browser and the Web server to negotiate
  the format and language in which data should be returned. To make the
  Web server capable of doing this, you can store the various languages
  and data formats in files with certain extensions and then enable
  multiviews.