  Apache WWW-server
  Introduction


  This is the main configuration menu for the WWW-server Apache.  Apache
  has a lot of configuration options and is extendable with third-party
  modules.  As a result Linuxconf can only control some of Apache's
  functionality, but it covers the most important parts.  In this window
  you control the server-wide configuration, and can set default values
  which can be overridden for specific parts of the web server contents.

  1.  Administrator email

  This address will be included in error messages to the web clients,
  e.g. when pages can't be found.  It is usually webmaster@domain.


  2.  Domain IP address

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


  3.  Server name

  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
  have to provide it yourself.


  4.  Server aliases

  Alias names for the web server.  Must not be provided here in the main
  configuration, only in virtual domains.


  5.  Document root

  The directory (in the real filesystem) where your main web pages are
  found.

  An example: If you  set 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.  Error log

  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,
  which means that the log path above would result in error messages
  logged to /var/log/httpd/error_log.

  You should monitor this log after reconfiguring, as 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.




  7.  Transfer log

  All accesses to the webserver 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, which most web log analysers understands.


  8.  Agent log

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


  9.  Referer log

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


  10.  Script Alias

  Gives the location of CGI programs.  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 file system.

  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.



  11.  User

  The user the web server should run as.  This means that the web server
  can only read and write those files which that user has right to read
  or write, respectively.  Therefore this should be set to a user with
  very low priviliges, e.g. nobody.

  Even better 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, as the user nobody should not have any rights to write
  files anywhere except in /tmp.


  12.  Group

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



  13.  Tuning



  13.1.  Listen on port

  The TCP port the web server should listen for HTTP requests on.  The
  standard port for HTTP is 80, so if you use another port you have to
  write that in the URL as well.  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/.



  13.2.  Pid file

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


  13.3.  Time out

  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 time,
  freeing the resources it occupies.


  13.4.  Host name lookups

  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 resolving
  which will make the web server feel slow.  It is better to let a log
  file analyser resolve the addresses when processing the log files.



  14.  Features

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


  14.1.  Server side includes

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


  14.2.  IncludesNOEXEC

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


  14.3.  May execute CGI

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


  14.4.  Indexes

  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 the option is
  disabled a 404 Not found is returned instead.





  14.5.  May follow symlinks

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


  14.6.  Follow symlink if owner matches

  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, e.g.
  /etc/passwd.


  14.7.  Multiviews

  Multiviews allow the client browser and the web server to negotiate
  which format and language data should be returned in.  A way to make
  the web server capable of doing this is to store the various languages
  and data formats in files with certain extensions and then enabling
  multiviews.













































