Re: Re: [SQL-Ledger-users] Still Cannot install sql-ledger

[Antonio G. <ag...@ib...>]

Try to set the AddHandler Directive inside the definition of the Directory for SQL-Ledger.

By the way set the ServerName Directive too. This is actually commented.

Antonio Gallardo
> 
> From: Ibrahim Shaame <gtk...@ya...>
> Date: 2001/04/30 Mon AM 07:50:57 GMT+06:00
> To: sql...@li...
> Subject: Re: [SQL-Ledger-users] Still Cannot install sql-ledger
> 
> Hi,
>     Thanks for the advice. I have trying to make it work following your tips.
> Unfortunately I have not been able. The problem still persist. I am attaching
> here my httpd.conf file if you can try to seen where I am missing.
> 
> Sorry for bothering everybody, but really I want to run sql-ledger.
> 
> Thanks in advance
> 
> Ibrahim Shaame
> 
> Izzy Blacklock wrote:
> 
> > At 10:12 AM 21/04/01, you wrote:
> > >Following my previous emails, here is a copy of the
> > >screen I receive when calling setup.html (which is a
> > >copy of setup.cgi). Whenever I try to click on "Add
> > >User" (or List Users) I get a message : "Netscape in
> > >unable to find the file or directory named
> > >/var/lib/apache/sql-ledger/admin/$script, Check the
> > >name and try again". When I try to call from
> > >Netscape's File, Open Location, sometimes it says that
> > >file not found and sometimes it brings me to
> > >"http://localhost" with the famous apache page
> > >announcing the success of of its installation.
> > >
> > >Thank you for your hints
> >
> > That's about what I'd expect from opening a cgi script in a web browser! :)
> >
> > I'm new to this as well so please forgive me if I'm wrong, but I think your
> > problem is with your Apache setup.  You have to specifically tell Apache
> > it's ok to run scripts outside of it's default cgi directory.  The answers
> > are in the SQL-Ledger FAQ, but I too had problems understanding at
> > first.  There's so many things to install and configure and if you've never
> > done any of it before, it can be quite a daunting task! :(
> >
> > I think your problem is with Apache, so here's what you need to do for
> > it.  The first thing is to add support for running .pl files as cgi scripts
> > as the first point in the FAQ suggests.  Edit your httpd.conf file (mine
> > was in /etc/httpd/httpd.conf) and searched for "To use CGI scripts".  You
> > should find a section like this:
> >
> > # To use CGI scripts:
> > AddHandler cgi-script .cgi
> >
> > If it isn't there already, add the following as is indicated in the FAQ.
> >
> > AddHandler cgi-script .pl
> >
> > Next I'd skip to the bottom of the FAQ to the section on security and
> > follow all these steps.  Don't make the mistake I did and assume that
> > Apache is running as the default user nobody.nogroup.  I found out mine was
> > running as wwwrun.nogroup  which is the default configuration under
> > SuSE.  If you search your httpd.conf file for "User/Group", you should find
> > entries like this
> >
> > User wwwrun
> > Group nogroup
> >
> > Change step 2 in the FAQ to match these settings.  Of course you will also
> > want to change the path in all these steps to match where you've put the
> > sql-Ledger directory.
> >
> > For step 4, I'd just copy the lines as he has them there (with adjustments
> > to the sql-ledger path if needed) and place them in the httpd.conf
> > file.  If you search for "<Directory" you'll find the section where you
> > want to put them. Just move to the bottom of the last entry (they end with
> > </Directory>) and past it all there.  Make sure the path is correct for
> > where you put sql-ledger.
> >
> > I didn't understand step 5, and step 6 you can probably skip.
> >
> > Hope this helps.
> >
> > ...Izzy
> 
> ##
> ## httpd.conf -- Apache HTTP server configuration file
> ##
> 
> #
> # Based upon the NCSA server configuration files originally by Rob McCool.
> #
> # This is the main Apache server configuration file.  It contains the
> # configuration directives that give the server its instructions.
> # See <URL:http://www.apache.org/docs/> for detailed information about
> # the directives.
> #
> # Do NOT simply read the instructions in here without understanding
> # what they do.  They're here only as hints or reminders.  If you are unsure
> # consult the online docs. You have been warned.  
> #
> # After this file is processed, the server will look for and process
> # /var/lib/apache/conf/srm.conf and then /var/lib/apache/conf/access.conf
> # unless you have overridden these with ResourceConfig and/or
> # AccessConfig directives here.
> #
> # The configuration directives are grouped into three basic sections:
> #  1. Directives that control the operation of the Apache server process as a
> #     whole (the 'global environment').
> #  2. Directives that define the parameters of the 'main' or 'default' server,
> #     which responds to requests that aren't handled by a virtual host.
> #     These directives also provide default values for the settings
> #     of all virtual hosts.
> #  3. Settings for virtual hosts, which allow Web requests to be sent to
> #     different IP addresses or hostnames and have them handled by the
> #     same Apache server process.
> #
> # Configuration and logfile names: If the filenames you specify for many
> # of the server's control files begin with "/" (or "drive:/" for Win32), the
> # server will use that explicit path.  If the filenames do *not* begin
> # with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
> # with ServerRoot set to "/usr/local/apache" will be interpreted by the
> # server as "/usr/local/apache/logs/foo.log".
> #
> 
> ### Section 1: Global Environment
> #
> # The directives in this section affect the overall operation of Apache,
> # such as the number of concurrent requests it can handle or where it
> # can find its configuration files.
> #
> 
> #
> # ServerType is either inetd, or standalone.  Inetd mode is only supported on
> # Unix platforms.
> #
> ServerType standalone
> 
> #
> # ServerRoot: The top of the directory tree under which the server's
> # configuration, error, and log files are kept.
> #
> # NOTE!  If you intend to place this on an NFS (or otherwise network)
> # mounted filesystem then please read the LockFile documentation
> # (available at <URL:http://www.apache.org/docs/mod/core.html#lockfile>);
> # you will save yourself a lot of trouble.
> #
> # Do NOT add a slash at the end of the directory path.
> #
> ServerRoot "/var/lib/apache"
> 
> #
> # The LockFile directive sets the path to the lockfile used when Apache
> # is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
> # USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at
> # its default value. The main reason for changing it is if the logs
> # directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
> # DISK. The PID of the main server process is automatically appended to
> # the filename. 
> #
> #LockFile /var/run/httpd.lock
> 
> #
> # PidFile: The file in which the server should record its process
> # identification number when it starts.
> #
> PidFile /var/run/httpd.pid
> 
> #
> # ScoreBoardFile: File used to store internal server process information.
> # Not all architectures require this.  But if yours does (you'll know because
> # this file will be  created when you run Apache) then you *must* ensure that
> # no two invocations of Apache share the same scoreboard file.
> #
> ScoreBoardFile /var/run/httpd.scoreboard
> 
> #
> # In the standard configuration, the server will process this file,
> # srm.conf, and access.conf in that order.  The latter two files are
> # now distributed empty, as it is recommended that all directives
> # be kept in a single file for simplicity.  The commented-out values
> # below are the built-in defaults.  You can have the server ignore
> # these files altogether by using "/dev/null" (for Unix) or
> # "nul" (for Win32) for the arguments to the directives.
> #
> #ResourceConfig conf/srm.conf
> #AccessConfig conf/access.conf
> 
> #
> # Timeout: The number of seconds before receives and sends time out.
> #
> Timeout 300
> 
> #
> # KeepAlive: Whether or not to allow persistent connections (more than
> # one request per connection). Set to "Off" to deactivate.
> #
> KeepAlive On
> 
> #
> # MaxKeepAliveRequests: The maximum number of requests to allow
> # during a persistent connection. Set to 0 to allow an unlimited amount.
> # We recommend you leave this number high, for maximum performance.
> #
> MaxKeepAliveRequests 100
> 
> #
> # KeepAliveTimeout: Number of seconds to wait for the next request from the
> # same client on the same connection.
> #
> KeepAliveTimeout 15
> 
> #
> # Server-pool size regulation.  Rather than making you guess how many
> # server processes you need, Apache dynamically adapts to the load it
> # sees --- that is, it tries to maintain enough server processes to
> # handle the current load, plus a few spare servers to handle transient
> # load spikes (e.g., multiple simultaneous requests from a single
> # Netscape browser).
> #
> # It does this by periodically checking how many servers are waiting
> # for a request.  If there are fewer than MinSpareServers, it creates
> # a new spare.  If there are more than MaxSpareServers, some of the
> # spares die off.  The default values are probably OK for most sites.
> #
> MinSpareServers 5
> MaxSpareServers 10
> 
> #
> # Number of servers to start initially --- should be a reasonable ballpark
> # figure.
> #
> StartServers 5
> 
> #
> # Limit on total number of servers running, i.e., limit on the number
> # of clients who can simultaneously connect --- if this limit is ever
> # reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
> # It is intended mainly as a brake to keep a runaway server from taking
> # the system with it as it spirals down...
> #
> MaxClients 150
> 
> #
> # MaxRequestsPerChild: the number of requests each child process is
> # allowed to process before the child dies.  The child will exit so
> # as to avoid problems after prolonged use when Apache (and maybe the
> # libraries it uses) leak memory or other resources.  On most systems, this
> # isn't really needed, but a few (such as Solaris) do have notable leaks
> # in the libraries. For these platforms, set to something like 10000
> # or so; a setting of 0 means unlimited.
> #
> # NOTE: This value does not include keepalive requests after the initial
> #       request per connection. For example, if a child process handles
> #       an initial request and 10 subsequent "keptalive" requests, it
> #       would only count as 1 request towards this limit.
> #
> MaxRequestsPerChild 0
> 
> #
> # Listen: Allows you to bind Apache to specific IP addresses and/or
> # ports, in addition to the default. See also the <VirtualHost>
> # directive.
> #
> #Listen 3000
> #Listen 12.34.56.78:80
> 
> #
> # BindAddress: You can support virtual hosts with this option. This directive
> # is used to tell the server which IP address to listen to. It can either
> # contain "*", an IP address, or a fully qualified Internet domain name.
> # See also the <VirtualHost> and Listen directives.
> #
> #BindAddress *
> 
> #
> # Dynamic Shared Object (DSO) Support
> #
> # To be able to use the functionality of a module which was built as a DSO you
> # have to place corresponding `LoadModule' lines at this location so the
> # directives contained in it are actually available _before_ they are used.
> # Please read the file README.DSO in the Apache 1.3 distribution for more
> # details about the DSO mechanism and run `httpd -l' for the list of already
> # built-in (statically linked and thus always available) modules in your httpd
> # binary.
> #
> # Note: The order is which modules are loaded is important.  Don't change
> # the order below without expert advice.
> #
> # Example:
> # LoadModule foo_module libexec/mod_foo.so
> LoadModule env_module         libexec/mod_env.so
> LoadModule config_log_module  libexec/mod_log_config.so
> LoadModule mime_module        libexec/mod_mime.so
> LoadModule negotiation_module libexec/mod_negotiation.so
> LoadModule status_module      libexec/mod_status.so
> LoadModule includes_module    libexec/mod_include.so
> LoadModule autoindex_module   libexec/mod_autoindex.so
> LoadModule dir_module         libexec/mod_dir.so
> LoadModule cgi_module         libexec/mod_cgi.so
> LoadModule asis_module        libexec/mod_asis.so
> LoadModule imap_module        libexec/mod_imap.so
> LoadModule action_module      libexec/mod_actions.so
> LoadModule userdir_module     libexec/mod_userdir.so
> LoadModule alias_module       libexec/mod_alias.so
> LoadModule access_module      libexec/mod_access.so
> LoadModule auth_module        libexec/mod_auth.so
> LoadModule setenvif_module    libexec/mod_setenvif.so
> 
> #  Reconstruction of the complete module list from all available modules
> #  (static and shared ones) to achieve correct module execution order.
> #  [WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE UPDATE THIS, TOO]
> ClearModuleList
> AddModule mod_env.c
> AddModule mod_log_config.c
> AddModule mod_mime.c
> AddModule mod_negotiation.c
> AddModule mod_status.c
> AddModule mod_include.c
> AddModule mod_autoindex.c
> AddModule mod_dir.c
> AddModule mod_cgi.c
> AddModule mod_asis.c
> AddModule mod_imap.c
> AddModule mod_actions.c
> AddModule mod_userdir.c
> AddModule mod_alias.c
> AddModule mod_access.c
> AddModule mod_auth.c
> AddModule mod_so.c
> AddModule mod_setenvif.c
> 
> #
> # ExtendedStatus controls whether Apache will generate "full" status
> # information (ExtendedStatus On) or just basic information (ExtendedStatus
> # Off) when the "server-status" handler is called. The default is Off.
> #
> #ExtendedStatus On
> 
> ### Section 2: 'Main' server configuration
> #
> # The directives in this section set up the values used by the 'main'
> # server, which responds to any requests that aren't handled by a
> # <VirtualHost> definition.  These values also provide defaults for
> # any <VirtualHost> containers you may define later in the file.
> #
> # All of these directives may appear inside <VirtualHost> containers,
> # in which case these default settings will be overridden for the
> # virtual host being defined.
> #
> 
> #
> # If your ServerType directive (set earlier in the 'Global Environment'
> # section) is set to "inetd", the next few directives don't have any
> # effect since their settings are defined by the inetd configuration.
> # Skip ahead to the ServerAdmin directive.
> #
> 
> #
> # Port: The port to which the standalone server listens. For
> # ports < 1023, you will need httpd to be run as root initially.
> #
> Port 80
> 
> #
> # If you wish httpd to run as a different user or group, you must run
> # httpd as root initially and it will switch.  
> #
> # User/Group: The name (or #number) of the user/group to run httpd as.
> #  . On SCO (ODT 3) use "User nouser" and "Group nogroup".
> #  . On HPUX you may not be able to use shared memory as nobody, and the
> #    suggested workaround is to create a user www and use that user.
> #  NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
> #  when the value of (unsigned)Group is above 60000; 
> #  don't use Group nogroup on these systems!
> #
> User nobody
> Group nogroup
> 
> #
> # ServerAdmin: Your address, where problems with the server should be
> # e-mailed.  This address appears on some server-generated pages, such
> # as error documents.
> #
> ServerAdmin ro...@xy...
> 
> #
> # ServerName allows you to set a host name which is sent back to clients for
> # your server if it's different than the one the program would get (i.e., use
> # "www" instead of the host's real name).
> #
> # Note: You cannot just invent host names and hope they work. The name you 
> # define here must be a valid DNS name for your host. If you don't understand
> # this, ask your network administrator.
> # If your host doesn't have a registered DNS name, enter its IP address here.
> # You will have to access it by its address (e.g., http://123.45.67.89/)
> # anyway, and this will make redirections work in a sensible way.
> #
> #ServerName xyzzy.rrnet.com
> 
> #
> # DocumentRoot: The directory out of which you will serve your
> # documents. By default, all requests are taken from this directory, but
> # symbolic links and aliases may be used to point to other locations.
> #
> DocumentRoot "/var/lib/apache/htdocs"
> 
> #
> # Each directory to which Apache has access, can be configured with respect
> # to which services and features are allowed and/or disabled in that
> # directory (and its subdirectories). 
> #
> # First, we configure the "default" to be a very restrictive set of 
> # permissions.  
> #
> Alias /sql-ledger/ /var/lib/apache/sql-ledger/
> <Directory /var/lib/apache/sql-ledger>
> 	AllowOverride None
> 	Options Includes FollowSymLinks ExecCGI
> </Directory>
> <Directory /var/lib/apache/sql-ledger/admin>
> 	AllowOverride FileInfo
> 	Options	FollowSymLinks	ExecCGI
> </Directory>
> <Directory /var/lib/apache/sql-ledger/users>
> 	Options None
> </Directory>		
> <Directory />
>     Options FollowSymLinks
>     AllowOverride None
> </Directory>
> 
> #
> # Note that from this point forward you must specifically allow
> # particular features to be enabled - so if something's not working as
> # you might expect, make sure that you have specifically enabled it
> # below.
> #
> 
> #
> # This should be changed to whatever you set DocumentRoot to.
> #
> <Directory "/var/lib/apache/htdocs">
> 
> #
> # This may also be "None", "All", or any combination of "Indexes",
> # "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
> #
> # Note that "MultiViews" must be named *explicitly* --- "Options All"
> # doesn't give it to you.
> #
>     Options Indexes FollowSymLinks
> 
> #
> # This controls which options the .htaccess files in directories can
> # override. Can also be "All", or any combination of "Options", "FileInfo", 
> # "AuthConfig", and "Limit"
> #
>     AllowOverride None
> 
> #
> # Controls who can get stuff from this server.
> #
>     Order allow,deny
>     Allow from all
> </Directory>
> 
> #
> # UserDir: The name of the directory which is appended onto a user's home
> # directory if a ~user request is received.
> #
> UserDir public_html
> 
> #
> # Control access to UserDir directories.  The following is an example
> # for a site where these directories are restricted to read-only.
> #
> #<Directory /home/*/public_html>
> #    AllowOverride FileInfo AuthConfig Limit
> #    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
> #    <Limit GET POST OPTIONS PROPFIND>
> #        Order allow,deny
> #        Allow from all
> #    </Limit>
> #    <Limit PUT DELETE PATCH PROPPATCH MKCOL COPY MOVE LOCK UNLOCK>
> #        Order deny,allow
> #        Deny from all
> #    </Limit>
> #</Directory>
> 
> #
> # DirectoryIndex: Name of the file or files to use as a pre-written HTML
> # directory index.  Separate multiple entries with spaces.
> #
> DirectoryIndex index.html
> 
> #
> # AccessFileName: The name of the file to look for in each directory
> # for access control information.
> #
> AccessFileName .htaccess
> 
> #
> # The following lines prevent .htaccess files from being viewed by
> # Web clients.  Since .htaccess files often contain authorization
> # information, access is disallowed for security reasons.  Comment
> # these lines out if you want Web visitors to see the contents of
> # .htaccess files.  If you change the AccessFileName directive above,
> # be sure to make the corresponding changes here.
> #
> # Also, folks tend to use names such as .htpasswd for password
> # files, so this will protect those as well.
> #
> <Files ~ "^\.ht">
>     Order allow,deny
>     Deny from all
> </Files>
> 
> #
> # CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each
> # document that was negotiated on the basis of content. This asks proxy
> # servers not to cache the document. Uncommenting the following line disables
> # this behavior, and proxies will be allowed to cache the documents.
> #
> #CacheNegotiatedDocs
> 
> #
> # UseCanonicalName:  (new for 1.3)  With this setting turned on, whenever
> # Apache needs to construct a self-referencing URL (a URL that refers back
> # to the server the response is coming from) it will use ServerName and
> # Port to form a "canonical" name.  With this setting off, Apache will
> # use the hostname:port that the client supplied, when possible.  This
> # also affects SERVER_NAME and SERVER_PORT in CGI scripts.
> #
> UseCanonicalName On
> 
> #
> # TypesConfig describes where the mime.types file (or equivalent) is
> # to be found.
> #
> TypesConfig /var/lib/apache/conf/mime.types
> 
> #
> # DefaultType is the default MIME type the server will use for a document
> # if it cannot otherwise determine one, such as from filename extensions.
> # If your server contains mostly text or HTML documents, "text/plain" is
> # a good value.  If most of your content is binary, such as applications
> # or images, you may want to use "application/octet-stream" instead to
> # keep browsers from trying to display binary files as though they are
> # text.
> #
> DefaultType text/plain
> 
> #
> # The mod_mime_magic module allows the server to use various hints from the
> # contents of the file itself to determine its type.  The MIMEMagicFile
> # directive tells the module where the hint definitions are located.
> # mod_mime_magic is not part of the default server (you have to add
> # it yourself with a LoadModule [see the DSO paragraph in the 'Global
> # Environment' section], or recompile the server and include mod_mime_magic
> # as part of the configuration), so it's enclosed in an <IfModule> container.
> # This means that the MIMEMagicFile directive will only be processed if the
> # module is part of the server.
> #
> <IfModule mod_mime_magic.c>
>     MIMEMagicFile /var/lib/apache/conf/magic
> </IfModule>
> 
> #
> # HostnameLookups: Log the names of clients or just their IP addresses
> # e.g., www.apache.org (on) or 204.62.129.132 (off).
> # The default is off because it'd be overall better for the net if people
> # had to knowingly turn this feature on, since enabling it means that
> # each client request will result in AT LEAST one lookup request to the
> # nameserver.
> #
> HostnameLookups Off
> 
> #
> # ErrorLog: The location of the error log file.
> # If you do not specify an ErrorLog directive within a <VirtualHost>
> # container, error messages relating to that virtual host will be
> # logged here.  If you *do* define an error logfile for a <VirtualHost>
> # container, that host's errors will be logged there and not here.
> #
> ErrorLog /var/log/error_log
> 
> #
> # LogLevel: Control the number of messages logged to the error_log.
> # Possible values include: debug, info, notice, warn, error, crit,
> # alert, emerg.
> #
> LogLevel warn
> 
> #
> # The following directives define some format nicknames for use with
> # a CustomLog directive (see below).
> #
> LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
> LogFormat "%h %l %u %t \"%r\" %>s %b" common
> LogFormat "%{Referer}i -> %U" referer
> LogFormat "%{User-agent}i" agent
> 
> #
> # The location and format of the access logfile (Common Logfile Format).
> # If you do not define any access logfiles within a <VirtualHost>
> # container, they will be logged here.  Contrariwise, if you *do*
> # define per-<VirtualHost> access logfiles, transactions will be
> # logged therein and *not* in this file.
> #
> CustomLog /var/log/access_log common
> 
> #
> # If you would like to have agent and referer logfiles, uncomment the
> # following directives.
> #
> #CustomLog /var/log/referer_log referer
> #CustomLog /var/log/agent_log agent
> 
> #
> # If you prefer a single logfile with access, agent, and referer information
> # (Combined Logfile Format) you can use the following directive.
> #
> #CustomLog /var/log/access_log combined
> 
> #
> # Optionally add a line containing the server version and virtual host
> # name to server-generated pages (error documents, FTP directory listings,
> # mod_status and mod_info output etc., but not CGI generated documents).
> # Set to "EMail" to also include a mailto: link to the ServerAdmin.
> # Set to one of:  On | Off | EMail
> #
> ServerSignature On
> 
> #
> # Aliases: Add here as many aliases as you need (with no limit). The format is 
> # Alias fakename realname
> #
> # Note that if you include a trailing / on fakename then the server will
> # require it to be present in the URL.  So "/icons" isn't aliased in this
> # example, only "/icons/"..
> #
> Alias /icons/ "/var/lib/apache/icons/"
> 
> <Directory "/var/lib/apache/icons">
>     Options Indexes MultiViews
>     AllowOverride None
>     Order allow,deny
>     Allow from all
> </Directory>
> 
> #
> # ScriptAlias: This controls which directories contain server scripts.
> # ScriptAliases are essentially the same as Aliases, except that
> # documents in the realname directory are treated as applications and
> # run by the server when requested rather than as documents sent to the client.
> # The same rules about trailing "/" apply to ScriptAlias directives as to
> # Alias.
> #
> # ScriptAlias /cgi-bin/ "/var/lib/apache/cgi-bin/"
> ScriptAlias /cgi-bin/ "/var/lib/apache/sql-ledger"
> # ScriptAlias /cgi-bin/ "/var/lib/apache/sql-ledger/admin"
> # ScriptAlias /cgi-bin/ "/var/lib/apache/sql-ledger/users"
> 
> 
> 
> #
> # "/var/lib/apache/cgi-bin" should be changed to whatever your ScriptAliased
> # CGI directory exists, if you have that configured.
> #
> <Directory "/var/lib/apache/cgi-bin">
>     AllowOverride None
>     Options None
>     Order allow,deny
>     Allow from all
> </Directory>
> 
> #
> # Redirect allows you to tell clients about documents which used to exist in
> # your server's namespace, but do not anymore. This allows you to tell the
> # clients where to look for the relocated document.
> # Format: Redirect old-URI new-URL
> #
> 
> #
> # Directives controlling the display of server-generated directory listings.
> #
> 
> #
> # FancyIndexing is whether you want fancy directory indexing or standard
> #
> IndexOptions FancyIndexing
> 
> #
> # AddIcon* directives tell the server which icon to show for different
> # files or filename extensions.  These are only displayed for
> # FancyIndexed directories.
> #
> AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
> 
> AddIconByType (TXT,/icons/text.gif) text/*
> AddIconByType (IMG,/icons/image2.gif) image/*
> AddIconByType (SND,/icons/sound2.gif) audio/*
> AddIconByType (VID,/icons/movie.gif) video/*
> 
> AddIcon /icons/binary.gif .bin .exe
> AddIcon /icons/binhex.gif .hqx
> AddIcon /icons/tar.gif .tar
> AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
> AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
> AddIcon /icons/a.gif .ps .ai .eps
> AddIcon /icons/layout.gif .html .shtml .htm .pdf
> AddIcon /icons/text.gif .txt
> AddIcon /icons/c.gif .c
> AddIcon /icons/p.gif .pl .py
> AddIcon /icons/f.gif .for
> AddIcon /icons/dvi.gif .dvi
> AddIcon /icons/uuencoded.gif .uu
> AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
> AddIcon /icons/tex.gif .tex
> AddIcon /icons/bomb.gif core
> 
> AddIcon /icons/back.gif ..
> AddIcon /icons/hand.right.gif README
> AddIcon /icons/folder.gif ^^DIRECTORY^^
> AddIcon /icons/blank.gif ^^BLANKICON^^
> 
> #
> # DefaultIcon is which icon to show for files which do not have an icon
> # explicitly set.
> #
> DefaultIcon /icons/unknown.gif
> 
> #
> # AddDescription allows you to place a short description after a file in
> # server-generated indexes.  These are only displayed for FancyIndexed
> # directories.
> # Format: AddDescription "description" filename
> #
> #AddDescription "GZIP compressed document" .gz
> #AddDescription "tar archive" .tar
> #AddDescription "GZIP compressed tar archive" .tgz
> 
> #
> # ReadmeName is the name of the README file the server will look for by
> # default, and append to directory listings.
> #
> # HeaderName is the name of a file which should be prepended to
> # directory indexes. 
> #
> # The server will first look for name.html and include it if found.
> # If name.html doesn't exist, the server will then look for name.txt
> # and include it as plaintext if found.
> #
> ReadmeName README
> HeaderName HEADER
> 
> #
> # IndexIgnore is a set of filenames which directory indexing should ignore
> # and not include in the listing.  Shell-style wildcarding is permitted.
> #
> IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
> 
> #
> # AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
> # information on the fly. Note: Not all browsers support this.
> # Despite the name similarity, the following Add* directives have nothing
> # to do with the FancyIndexing customization directives above.
> #
> AddEncoding x-compress Z
> AddEncoding x-gzip gz tgz
> 
> #
> # AddLanguage allows you to specify the language of a document. You can
> # then use content negotiation to give a browser a file in a language
> # it can understand.  Note that the suffix does not have to be the same
> # as the language keyword --- those with documents in Polish (whose
> # net-standard language code is pl) may wish to use "AddLanguage pl .po" 
> # to avoid the ambiguity with the common suffix for perl scripts.
> #
> AddLanguage en .en
> AddLanguage fr .fr
> AddLanguage de .de
> AddLanguage da .da
> AddLanguage el .el
> AddLanguage it .it
> 
> #
> # LanguagePriority allows you to give precedence to some languages
> # in case of a tie during content negotiation.
> # Just list the languages in decreasing order of preference.
> #
> LanguagePriority en fr de
> 
> #
> # AddType allows you to tweak mime.types without actually editing it, or to
> # make certain files to be certain types.
> #
> # For example, the PHP3 module (not part of the Apache distribution - see
> # http://www.php.net) will typically use:
> #
> #AddType application/x-httpd-php3 .php3
> #AddType application/x-httpd-php3-source .phps
> 
> AddType application/x-tar .tgz
> 
> #
> # AddHandler allows you to map certain file extensions to "handlers",
> # actions unrelated to filetype. These can be either built into the server
> # or added with the Action command (see below)
> #
> # If you want to use server side includes, or CGI outside
> # ScriptAliased directories, uncomment the following lines.
> #
> # To use CGI scripts:
> #
> AddHandler cgi-script .cgi
> AddHandler cgi-script .pl
> 
> #
> # To use server-parsed HTML files
> #
> #AddType text/html .shtml
> #AddHandler server-parsed .shtml
> 
> #
> # Uncomment the following line to enable Apache's send-asis HTTP file
> # feature
> #
> #AddHandler send-as-is asis
> 
> #
> # If you wish to use server-parsed imagemap files, use
> #
> #AddHandler imap-file map
> 
> #
> # To enable type maps, you might want to use
> #
> #AddHandler type-map var
> 
> #
> # Action lets you define media types that will execute a script whenever
> # a matching file is called. This eliminates the need for repeated URL
> # pathnames for oft-used CGI file processors.
> # Format: Action media/type /cgi-script/location
> # Format: Action handler-name /cgi-script/location
> #
> 
> #
> # MetaDir: specifies the name of the directory in which Apache can find
> # meta information files. These files contain additional HTTP headers
> # to include when sending the document
> #
> #MetaDir .web
> 
> #
> # MetaSuffix: specifies the file name suffix for the file containing the
> # meta information.
> #
> #MetaSuffix .meta
> 
> #
> # Customizable error response (Apache style)
> #  these come in three flavors
> #
> #    1) plain text
> #ErrorDocument 500 "The server made a boo boo.
> #  n.b.  the (") marks it as text, it does not get output
> #
> #    2) local redirects
> #ErrorDocument 404 /missing.html
> #  to redirect to local URL /missing.html
> #ErrorDocument 404 /cgi-bin/missing_handler.pl
> #  N.B.: You can redirect to a script or a document using server-side-includes.
> #
> #    3) external redirects
> #ErrorDocument 402 http://some.other_server.com/subscription_info.html
> #  N.B.: Many of the environment variables associated with the original
> #  request will *not* be available to such a script.
> 
> #
> # The following directives modify normal HTTP response behavior.
> # The first directive disables keepalive for Netscape 2.x and browsers that
> # spoof it. There are known problems with these browser implementations.
> # The second directive is for Microsoft Internet Explorer 4.0b2
> # which has a broken HTTP/1.1 implementation and does not properly
> # support keepalive when it is used on 301 or 302 (redirect) responses.
> #
> BrowserMatch "Mozilla/2" nokeepalive
> BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
> 
> #
> # The following directive disables HTTP/1.1 responses to browsers which
> # are in violation of the HTTP/1.0 spec by not being able to grok a
> # basic 1.1 response.
> #
> BrowserMatch "RealPlayer 4\.0" force-response-1.0
> BrowserMatch "Java/1\.0" force-response-1.0
> BrowserMatch "JDK/1\.0" force-response-1.0
> 
> #
> # Allow server status reports, with the URL of http://servername/server-status
> # Change the ".your_domain.com" to match your domain to enable.
> #
> #<Location /server-status>
> #    SetHandler server-status
> #    Order deny,allow
> #    Deny from all
> #    Allow from .your_domain.com
> #</Location>
> 
> #
> # Allow remote server configuration reports, with the URL of
> #  http://servername/server-info (requires that mod_info.c be loaded).
> # Change the ".your_domain.com" to match your domain to enable.
> #
> #<Location /server-info>
> #    SetHandler server-info
> #    Order deny,allow
> #    Deny from all
> #    Allow from .your_domain.com
> #</Location>
> 
> #
> # There have been reports of people trying to abuse an old bug from pre-1.1
> # days.  This bug involved a CGI script distributed as a part of Apache.
> # By uncommenting these lines you can redirect these attacks to a logging 
> # script on phf.apache.org.  Or, you can record them yourself, using the script
> # support/phf_abuse_log.cgi.
> #
> #<Location /cgi-bin/phf*>
> #    Deny from all
> #    ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi
> #</Location>
> 
> #
> # Proxy Server directives. Uncomment the following lines to
> # enable the proxy server:
> #
> #<IfModule mod_proxy.c>
> #ProxyRequests On
> #
> #<Directory proxy:*>
> #    Order deny,allow
> #    Deny from all
> #    Allow from .your_domain.com
> #</Directory>
> 
> #
> # Enable/disable the handling of HTTP/1.1 "Via:" headers.
> # ("Full" adds the server version; "Block" removes all outgoing Via: headers)
> # Set to one of: Off | On | Full | Block
> #
> #ProxyVia On
> 
> #
> # To enable the cache as well, edit and uncomment the following lines:
> # (no cacheing without CacheRoot)
> #
> #CacheRoot "/var/lib/apache/proxy"
> #CacheSize 5
> #CacheGcInterval 4
> #CacheMaxExpire 24
> #CacheLastModifiedFactor 0.1
> #CacheDefaultExpire 1
> #NoCache a_domain.com another_domain.edu joes.garage_sale.com
> 
> #</IfModule>
> # End of proxy directives.
> 
> ### Section 3: Virtual Hosts
> #
> # VirtualHost: If you want to maintain multiple domains/hostnames on your
> # machine you can setup VirtualHost containers for them.
> # Please see the documentation at <URL:http://www.apache.org/docs/vhosts/>
> # for further details before you try to setup virtual hosts.
> # You may use the command line option '-S' to verify your virtual host
> # configuration.
> 
> #
> # If you want to use name-based virtual hosts you need to define at
> # least one IP address (and port number) for them.
> #
> #NameVirtualHost 12.34.56.78:80
> #NameVirtualHost 12.34.56.78
> 
> #
> # VirtualHost example:
> # Almost any Apache directive may go into a VirtualHost container.
> #
> #<VirtualHost ip.address.of.host.some_domain.com>
> #    ServerAdmin web...@ho...me_domain.com
> #    DocumentRoot /www/docs/host.some_domain.com
> #    ServerName host.some_domain.com
> #    ErrorLog logs/host.some_domain.com-error_log
> #    CustomLog logs/host.some_domain.com-access_log common
> #</VirtualHost>
> 
> #<VirtualHost _default_:*>
> #</VirtualHost>
> 
>