PC Online 1999 November/PCONLINE_11_99.ISO/filesbbs/OS2/APCHSSL2.ZIP/OS2HTTPD/bin/ServerConfig/ServerConfig.HLP

OS/2 Help File | 1999-06-20 | 70.2 KB | 2,491 lines

ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ

ServerConfig/2

Welcome to ServerConfig/2. An advanced configuration system for Apache and IPS.

ServerConfig/2 is a PM configuration system written in VX-REXX. It allows you
to configure any Apache webserver, InetPowerServer/2 and the TCP/IP Firewall.

Features include:
 Remote Apache configuration access via TCP/IP.
 The remote Apache can be under any UNIX platform.
 Remote Apache Restart/Shutdown.
 IPS user management.
 IPS services management.
 Firewall rules editting.
 Firewall logging.
 On-line help.
 and many more...

Thank you for using ServerConfig/2.


ΓòÉΓòÉΓòÉ 2. ServerConfig/2 ΓòÉΓòÉΓòÉ

ServerConfig/2 Configuration System

ServerConfig/2 can be started from command-line by specifing the configuration
you want to load.

Command-line usage:

ServerConfig.exe [-nolock] [[-a <full path to apache config>]  or [-i <full
path to IPS config>]] or [-f]

-nolock        ServerConfig/2 doesn't lock the configuration files.
-a <path+filename>  Load Apache configuration.
-i <path+filename>  Load InetPowerServer configuration.
-f           Start in the Firewall setup.

The -nolock option will prevent ServerConfig/2 from locking the configuration
file. This feature allows you to edit your configuration while the server
(Apache or IPS) is running. Especialy if you change some settings and you don't
want to shutdown to "rehash" the server.

ServerConfig/2 has the following sections discussed, please read them, they
contain important information. Most of them can also be accessed via the online
help.

Apache:

1) FAQ - Important information
2) A ready-to-run Apache Configuration
3) Sample Apache Configuration
4) Directives (use the help button or press F1 on any entry field)

InetPowerServer:

1) Important information
2) Global section
3) Access section
4) Services section
5) Users section
(use the help button or press F1 on any entry field)

IBM TCP/IP Firewall:

1) Important information
2) Notebook pages (use the help button or press F1 on any entry field)


ΓòÉΓòÉΓòÉ 2.1. Apache ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 2.1.1. FAQ - Important Information ΓòÉΓòÉΓòÉ

Apache FAQ

Q: How do i disable a directive?
A: Simply type <Undefined> on the space provided.

Q: Why doesn't my server reset/shutdown?
A: You are running the daemon from a directory with a space!

Q: I try to load my Apache configuration but not all of it is loaded!
A: You are using an older version of Apache than 1.3.6, or you have
 a very complex configuration that is not recognized.

Q: My Apache will not restart/shutdown remotely!
A1: You are still using an older version of Apache than 1.3.6
A2: Make sure your .pid file is correct.

Q: I can't reset Apache or IPS can't read the configuration file!
A: You need to run ServerConfig/2 with the '-nolock' option so
 that it doesn't lock the configuration file.

IMPORTANT INFORMATION

ServerConfig/2 now fully supports ALL the directives used in the DEFAULT Apache
configuration file with the exception that it doesn't support multiple
configurations.

Apache supports a lot more directives that are not in the default
configuration, so if you find some commands are not loaded, please send me an
email and i'll add support for them.

The source of the daemon included is for ALL unix/linux systems, the code is
using
system-independed C functions and can be compiled by any GCC compiler.

When you load a configuration with comments remember, that when you save it the
comments will be removed.


ΓòÉΓòÉΓòÉ 2.1.2. Sample fully working Apache configuration ΓòÉΓòÉΓòÉ

# This is a fully working Apache configuration, you
# can save it as a file and use it with just a few
# modifications.

# Apache Configuration created by ServerConfig/2 v0.7


# Global Configuration


ServerType standalone
ServerRoot "c:/tcpip/os2httpd"
PidFile logs/httpd.pid
Timeout 300
KeepAlive OFF
MaxKeepAliveRequests 100
KeepAliveTimeout 30
MinSpareServers 1
MaxSpareServers 10
StartServers 2
MaxClients 20
MaxRequestsPerChild 15
ExtendedStatus ON


# Main Configuration


Port 80
User nobody
Group #-1
ServerAdmin [e-mail]
ServerName hicdbs
DocumentRoot "c:/tcpip/os2httpd/html"
UserDir public_html
DirectoryIndex index.html
AccessFileName .htaccess
UseCanonicalName ON
TypesConfig conf/mime.types
DefaultType text/plain
HostnameLookups OFF
ErrorLog logs/error_log
LogLevel notice

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

CustomLog logs/access_log common
ServerSignature EMail

Alias /icons/ "c:/tcpip/os2httpd/icons/"
Alias /hobbes/ "f:/hobbes.incoming/"
Alias /warpukcd/ "d:/"

ScriptAlias /cgi-bin/ "c:/tcpip/os2httpd/cgi-bin/"


# Directories & Files


<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>

<Directory "c:/tcpip/os2httpd/html">
Options FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>

<Files .htaccess>
Order allow,deny
Deny from all
</Files>

<Directory "c:/tcpip/os2httpd/icons">
Options MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

<Directory "f:/hobbes.incoming">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

<Directory "d:/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

<Directory "cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>

# Indexing


IndexOptions FancyIndexing
DefaultIcon /icons/unknown.gif
ReadmeName README
HeaderName HEADER
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
LanguagePriority en fr de


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 .rar .arj
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^^
AddDescription "GZIP compressed document" .gz
AddDescription "tar archive" .tar
AddDescription "GZIP compressed tar archive" .tgz
AddDescription "ZIP compressed tar archive" .zip
AddDescription "RAR compressed tar archive" .rar
AddDescription "ARJ compressed tar archive" .arj
AddEncoding x-compress Z
AddEncoding x-gzip gz
AddLanguage en .en
AddLanguage fr .fr
AddLanguage de .de
AddLanguage da .da
AddLanguage el .el
AddLanguage it .it
AddHandler imap-file map
AddHandler type-map var


BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch MSIE ErrorDocument 402 http://www.software.ibm.com/os/warp
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0


# Misc


<IfModule mod_mime_magic.c>
MIMEMagicFile conf/magic
</IfModule>

<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from hicdbs 10.10.10.1
</Location>


# Virtual Hosts


ΓòÉΓòÉΓòÉ 2.1.3. Sample Apache configuration ΓòÉΓòÉΓòÉ

#
# 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
# @@ServerRoot@@/conf/srm.conf and then @@ServerRoot@@/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 "@@ServerRoot@@"

#
# 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 logs/accept.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile logs/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 logs/apache_runtime_status

#
# In the standard configuration, the server will process httpd.conf,
# 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 in httpd.conf-dist 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.
#
MaxRequestsPerChild 30

#
# 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

#
# 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 #-1 on these systems!
#
User nobody
Group #-1

#
# 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 [e-mail]

#
# 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 new.host.name

#
# 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 "@@ServerRoot@@/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.
#
<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 "@@ServerRoot@@/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 /*/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.
#
<Files .htaccess>
 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 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 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 logs/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 logs/access_log common

#
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#
#CustomLog logs/referer_log referer
#CustomLog logs/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 logs/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/ "@@ServerRoot@@/icons/"

<Directory "@@ServerRoot@@/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/ "@@ServerRoot@@/cgi-bin/"

#
# "@@ServerRoot@@/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "@@ServerRoot@@/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

#
# 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)
# will typically use:
#
#AddType application/x-httpd-php3 .phtml
#AddType application/x-httpd-php3-source .phps

#
# 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

#
# 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 "@@ServerRoot@@/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 [e-mail]_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>


ΓòÉΓòÉΓòÉ 2.1.4. Directives ΓòÉΓòÉΓòÉ

Directives

These are the Apache configuration directives. You can view them online
by pressing F1 or by pressing the Help button.


ΓòÉΓòÉΓòÉ 2.1.4.1. ServerType ΓòÉΓòÉΓòÉ

ServerType is either inetd, or standalone.  Inetd mode is only supported on
Unix platforms.


ΓòÉΓòÉΓòÉ 2.1.4.2. ServerRoot ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.3. LockFile ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.4. PidFile ΓòÉΓòÉΓòÉ

PidFile: The file in which the server should record its process
identification number when it starts.


ΓòÉΓòÉΓòÉ 2.1.4.5. ScoreBoardFile ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.6. Timeout ΓòÉΓòÉΓòÉ

Timeout: The number of seconds before receives and sends time out.


ΓòÉΓòÉΓòÉ 2.1.4.7. KeepAlive ΓòÉΓòÉΓòÉ

KeepAlive: Whether or not to allow persistent connections (more than
one request per connection). Set to "Off" to deactivate.


ΓòÉΓòÉΓòÉ 2.1.4.8. MaxKeepAliveRequests ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.9. KeepAliveTimeout ΓòÉΓòÉΓòÉ

KeepAliveTimeout: Number of seconds to wait for the next request from the
same client on the same connection.


ΓòÉΓòÉΓòÉ 2.1.4.10. SpareServers ΓòÉΓòÉΓòÉ

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 in httpd.conf-dist are probably OK
for most sites.


ΓòÉΓòÉΓòÉ 2.1.4.11. StartServers ΓòÉΓòÉΓòÉ

Number of servers to start initially --- should be a reasonable ballpark
figure.


ΓòÉΓòÉΓòÉ 2.1.4.12. MaxClients ΓòÉΓòÉΓòÉ

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...


ΓòÉΓòÉΓòÉ 2.1.4.13. MaxRequestsPerChild ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.14. Listen ΓòÉΓòÉΓòÉ

Listen: Allows you to bind Apache to specific IP addresses and/or ports, in
addition to the default. See also the <VirtualHost>
directive.

Listen port
Listen ipaddress:port

Example:

Listen 3000
Listen 12.34.56.78:80


ΓòÉΓòÉΓòÉ 2.1.4.15. BindAddress ΓòÉΓòÉΓòÉ

BindAddress: You can support virtual hosts with this option. This directiv
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.


ΓòÉΓòÉΓòÉ 2.1.4.16. LoadModule ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 2.1.4.17. ExtendedStatus ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.18. Port ΓòÉΓòÉΓòÉ

Port: The port to which the standalone server listens. For
ports < 1023, you will need httpd to be run as root initially.


ΓòÉΓòÉΓòÉ 2.1.4.19. User/Group ΓòÉΓòÉΓòÉ

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 #-1 on these systems!


ΓòÉΓòÉΓòÉ 2.1.4.20. ServerAdmin ΓòÉΓòÉΓòÉ

ServerAdmin: Your address, where problems with the server should be
e-mailed.  This address appears on some server-generated pages, such
as error documents.


ΓòÉΓòÉΓòÉ 2.1.4.21. ServerName ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.22. DocumentRoot ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.23. Directory ΓòÉΓòÉΓòÉ

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).

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.


ΓòÉΓòÉΓòÉ 2.1.4.24. UserDir ΓòÉΓòÉΓòÉ

UserDir: The name of the directory which is appended onto a user's home
directory if a ~user request is received.


ΓòÉΓòÉΓòÉ 2.1.4.25. DirectoryIndex ΓòÉΓòÉΓòÉ

DirectoryIndex: Name of the file or files to use as a pre-written HTML
directory index.  Separate multiple entries with spaces.


ΓòÉΓòÉΓòÉ 2.1.4.26. AccessFileName ΓòÉΓòÉΓòÉ

AccessFileName: The name of the file to look for in each directory
for access control information.


ΓòÉΓòÉΓòÉ 2.1.4.27. CacheNegotiatedDocs ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.28. UseCanonicalName ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.29. TypesConfig ΓòÉΓòÉΓòÉ

TypesConfig describes where the mime.types file (or equivalent) is
to be found.


ΓòÉΓòÉΓòÉ 2.1.4.30. DefaultType ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.31. HostnameLookups ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.32. ErrorLog ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.33. LogLevel ΓòÉΓòÉΓòÉ

LogLevel: Control the number of messages logged to the error_log.
Possible values include: debug, info, notice, warn, error, crit,
alert, emerg.


ΓòÉΓòÉΓòÉ 2.1.4.34. TransferLog ΓòÉΓòÉΓòÉ

The TransferLog directive adds a log file in the format defined by the most
recent LogFormat directive, or Common Log Format if no other default format has
been specified.


ΓòÉΓòÉΓòÉ 2.1.4.35. LogFormat ΓòÉΓòÉΓòÉ

The following directives define some format nicknames for use with
a CustomLog directive (see below).


ΓòÉΓòÉΓòÉ 2.1.4.36. CustomLog ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.37. ServerSignature ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 2.1.4.38. Alias ΓòÉΓòÉΓòÉ

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/"..


ΓòÉΓòÉΓòÉ 2.1.4.39. ScriptAlias ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.40. Redirect ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 2.1.4.41. IndexOptions ΓòÉΓòÉΓòÉ

FancyIndexing is whether you want fancy directory indexing or standard


ΓòÉΓòÉΓòÉ 2.1.4.42. AddIcon ΓòÉΓòÉΓòÉ

AddIcon* directives tell the server which icon to show for different files or
filename extensions.  These are only displayed for FancyIndexed directories.


ΓòÉΓòÉΓòÉ 2.1.4.43. DefaultIcon ΓòÉΓòÉΓòÉ

DefaultIcon is which icon to show for files which do not have an icon
explicitly set.


ΓòÉΓòÉΓòÉ 2.1.4.44. ReadmeName-HeaderName ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.45. IndexIgnore ΓòÉΓòÉΓòÉ

IndexIgnore is a set of filenames which directory indexing should ignore and
not include in the listing.  Shell-style wildcarding is permitted.


ΓòÉΓòÉΓòÉ 2.1.4.46. LanguagePriority ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.47. MetaDir ΓòÉΓòÉΓòÉ

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


ΓòÉΓòÉΓòÉ 2.1.4.48. MetaSuffix ΓòÉΓòÉΓòÉ

MetaSuffix: specifies the file name suffix for the file containing the meta
information.


ΓòÉΓòÉΓòÉ 2.1.4.49. ErrorDocument ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.50. BrowserMatch ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.51. VirtualHost ΓòÉΓòÉΓòÉ

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.


ΓòÉΓòÉΓòÉ 2.1.4.52. NameVirtualHost ΓòÉΓòÉΓòÉ

If you want to use name-based virtual hosts you need to define at least one IP
address (and port number) for them.


ΓòÉΓòÉΓòÉ 2.2. IPS ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 2.2.1. Important information ΓòÉΓòÉΓòÉ

InetPowerServer/2 Information

IPS support is now complete, everything is supported by ServerConfig/2.

Your users will be automaticaly loaded when you first load your .cfg file.
Althoguh they are totaly independed from the main configuration file. So if you
save the main configuration, users are not updated. To updated user settings
you need to click on Save from the users settings notebook.

To use the Generate Password option, you must have pwd2.exe in your IPS bin
path (its there by default, unless you removed it).

If you want to edit your configuration file while IPS is running and you don't
want to shutdown, then use the '-nolock' option at the command-line so that
ServerConfig/2 will not lock the configuration file and thus IPS will be able
to read it while you make changes.


ΓòÉΓòÉΓòÉ 2.2.2. Global section ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 2.2.2.1. SiteDescription ΓòÉΓòÉΓòÉ

Informational text describing your site.

ex: My super site


ΓòÉΓòÉΓòÉ 2.2.2.2. SiteAdminUser ΓòÉΓòÉΓòÉ

UserID for the main administrative user. Also known as root on UNIX systems.

ex: admin


ΓòÉΓòÉΓòÉ 2.2.2.3. SiteAdminMail ΓòÉΓòÉΓòÉ

E-mail address for the main administrative user.

ex: [e-mail]


ΓòÉΓòÉΓòÉ 2.2.2.4. UserDirectory ΓòÉΓòÉΓòÉ

Directory for the user files, relative to IPS-root or absolute. OS format.

ex: .\cfg\main\users


ΓòÉΓòÉΓòÉ 2.2.2.5. StatDirectory ΓòÉΓòÉΓòÉ

Directory for the stat files, relative to IPS-root or absolute. OS format.

ex: .\cfg\main\stats


ΓòÉΓòÉΓòÉ 2.2.2.6. HomeDirectoryRoot ΓòÉΓòÉΓòÉ

Root directory for the users home directories. UNIX format.

ex: /c/tcpip/ips/cfg/main/home


ΓòÉΓòÉΓòÉ 2.2.2.7. GroupsDefined ΓòÉΓòÉΓòÉ

A list of defined user groups. Group names divided by a space.

ex: users admins other


ΓòÉΓòÉΓòÉ 2.2.2.8. ServiceSections ΓòÉΓòÉΓòÉ

A list of service sections are defined with a names divided by a space.
ServerConfig/2 configures thouse names automaticaly from the services notebook
page.


ΓòÉΓòÉΓòÉ 2.2.3. Access section ΓòÉΓòÉΓòÉ

To edit a new access line you can either type it yourself or click on the
"Generate" button to use the access-line-editor  that will help you do it for
you.

To modify a line you can just double-click on it and it will come up in the
access-line-editor.

In the [ACCESS] section you list accesses defined for you files systems. Access
masks are OS style path masks. This may include * and ? wild-chars anywhere in
the path. You should note that the first matching mask is used. This format is
also used for the [ACCESS] section in the user files.

Format: pathMask;Owner;Group;UnixAccess;ExtendedAccess

PathMask
          Mask which must match to make this access line active

Owner
          UserID of the user given the owner rights of this access line. Also
known as the
          owner of the items.

Group
          GroupID of whose members are give the group rights of this access
line.

UnixAccess
          UNIX style access numbers. This number consist of three digits one
for each of
          the owner, group and other settings; meaning that the user Owner is
given the
          access of the first digit, users which are members of the Group are
giving the
          access of the second digit, and all other users are given the access
of the third
          and last digit.
          Each digit are made added together from these accesses:
          1=Execute (or list) access
          2=Write access
          4=Read access.

ExtendedAccess
          Special IPS additions to the standard UNIX accesses. Works the same
way as
          above with one digit for owner, group and other.
          Available extended accesses include:
          1=Limit delete.

Example:
e:\pub\incoming\*;admin;users;777;011
e:\pub\*;admin;users;755;000
e:\;admin;users;111;000
;admin;users;711;000
*;admin;users;700;000


ΓòÉΓòÉΓòÉ 2.2.4. Services section ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 2.2.4.1. Common parameters ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 2.2.4.1.1. Host ΓòÉΓòÉΓòÉ

Host name this service should identify itself as.

ex: mysite.com


ΓòÉΓòÉΓòÉ 2.2.4.1.2. Protocol ΓòÉΓòÉΓòÉ

What protocol should this services run. Possible choices are:

          telnetd for shell login
          ftpd for File Transfer Protocol (rfc959)
          smtpd for Simple Mail Transfer Protocol (rfc821)
          pop3d for Post Office Protocol - Version 3 (rfc1939)


ΓòÉΓòÉΓòÉ 2.2.4.1.3. Address ΓòÉΓòÉΓòÉ

Optional parameter used to select which IP address the service should listen on
for multiple homed setup on a machine with multiple IP addresses. The address
should be specified in as four decimal numbers separated with only a dot.


ΓòÉΓòÉΓòÉ 2.2.4.1.4. Port ΓòÉΓòÉΓòÉ

Optional parameter used to run services on non-standard ports. Please keep in
mind that many fire-walls could block users for accessing services on
non-standard ports.

ex: 21


ΓòÉΓòÉΓòÉ 2.2.4.1.5. Timeout ΓòÉΓòÉΓòÉ

Time in seconds the connection can be inactive before it is closed.

ex: 300


ΓòÉΓòÉΓòÉ 2.2.4.1.6. LogFile ΓòÉΓòÉΓòÉ

Name of file to log all activity on this service. This file should always have
the default extension of .log.

ex: ftp.log


ΓòÉΓòÉΓòÉ 2.2.4.1.7. LogFlag ΓòÉΓòÉΓòÉ

Level of logging to perform. These levels are Protocol dependent. You should
set the level for those log entries you don't want.

          FTPd:

          1=PASS, USER
          2=APPE, DELE, RETR, RNFR, RNTO, STOR
          4=CDUP, CWD, LIST, NLST, XCUP, XCWD
          8=MKD, RMD, XMKD, XRMD
          16=MDTM, SIZE, TYPE
          32=PORT, REST
          64=PWD, SITE, SYST, XPWD

          ABOR, FEAT, HELP, MODE, NOOP, PASV, QUIT, REIN, STAT,

          SMTPd:

          1=HELO
          2=MAIL, RCPT
          4=DATA
          8=RSET

          POP3d:

          1=PASS, USER
          2=DELE, RETR
          4=LIST, STAT
          8=RSET

          QUIT


ΓòÉΓòÉΓòÉ 2.2.4.1.8. DebugFlag ΓòÉΓòÉΓòÉ

Level of debug logging to perform. This is added together from these levels;

          1=Incoming commands
          2=Outgoing command replies
          4=Long commands or replies
          8=Trace internals

Level 8 should only be used if requested by support personnel.


ΓòÉΓòÉΓòÉ 2.2.4.1.9. ClientAddress ΓòÉΓòÉΓòÉ

List of IP or Host masks to allow or deny access. First matching mask will be
used.

ex: 127.* !*
Will allow access from all IP's starting with 127. and deny all others.


ΓòÉΓòÉΓòÉ 2.2.4.1.10. rxOnConnect ΓòÉΓòÉΓòÉ

Path of RexxHook called when a new user connects. Script should return 0 if
connection are ok, or a response if not.

ex: .\scr\ftpd\rxOnConnect.cmd


ΓòÉΓòÉΓòÉ 2.2.4.1.11. rxOnCommand ΓòÉΓòÉΓòÉ

Path of RexxHook called when each command is received before it is executed.
Script should return 0 or a changed command line.

ex: .\scr\ftpd\rxOnCommand.cmd


ΓòÉΓòÉΓòÉ 2.2.4.1.12. rxOnPass ΓòÉΓòÉΓòÉ

Path of RexxHook called when the password for a guest session is received.
Script should return 0 if ok, or a response to reject the log-in.

ex: .\scr\ftpd\rxOnPass.cmd


ΓòÉΓòÉΓòÉ 2.2.4.1.13. rxOnRetr ΓòÉΓòÉΓòÉ

Path of RexxHook called before a file is sent to the user. Script should return
0 if the transfer are to proceed, and a response if it is rejected.

ex: .\scr\ftpd\rxOnRetr.cmd


ΓòÉΓòÉΓòÉ 2.2.4.1.14. RxOnSite ΓòÉΓòÉΓòÉ

Path of RexxHook called before executing internal SITE commands, this script
could return 0 to allow internal execution of the command or it could reject it
by returning a response.

ex: .\scr\ftpd\rxOnSite.cmd


ΓòÉΓòÉΓòÉ 2.2.4.1.15. rxOnStor ΓòÉΓòÉΓòÉ

Path of RexxHook called before a file is received from the user. Script should
return 0 if the transfer are to proceed, and a response if it is rejected.

ex: .\scr\ftpd\rxOnStor.cmd


ΓòÉΓòÉΓòÉ 2.2.4.1.16. rxOnUser ΓòÉΓòÉΓòÉ

Path of RexxHook called after a user name is received and a user file found.
Script should return 0 if log-in are ok, a response to reject.

ex: .\scr\ftpd\rxOnUser.cmd


ΓòÉΓòÉΓòÉ 2.2.4.1.17. rxOnData ΓòÉΓòÉΓòÉ

Path of RexxHook called after the .msg file is received before it is delivered.

ex: .\scr\smtpd\rxOnData.cmd


ΓòÉΓòÉΓòÉ 2.2.4.2. FTP parameters ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 2.2.4.2.1. RootDirectory ΓòÉΓòÉΓòÉ

Basic root directory of FTPd. UNIX format.


ΓòÉΓòÉΓòÉ 2.2.4.2.2. MaxUserBandwidth ΓòÉΓòÉΓòÉ

Maximum retrieve bandwidth for each normal user session.


ΓòÉΓòÉΓòÉ 2.2.4.2.3. MaxAnonBandwidth ΓòÉΓòÉΓòÉ

Maximum retrieve bandwidth for each guest session.


ΓòÉΓòÉΓòÉ 2.2.4.2.4. TimeoutMax ΓòÉΓòÉΓòÉ

Maximum time-out allowed by SITE IDLE command.

ex: 900


ΓòÉΓòÉΓòÉ 2.2.4.2.5. WelcomeFile ΓòÉΓòÉΓòÉ

Path of initial welcome files. OS format.

ex: .\msg\welcome.msg


ΓòÉΓòÉΓòÉ 2.2.4.2.6. HideIfNoAccess ΓòÉΓòÉΓòÉ

Hide files and directories which the user has no access to from directory
listings.


ΓòÉΓòÉΓòÉ 2.2.4.2.7. MinFreeSpace ΓòÉΓòÉΓòÉ

Do not allow uploads on disks with less than xx MB free space.

ex: 10


ΓòÉΓòÉΓòÉ 2.2.4.2.8. DisableEA ΓòÉΓòÉΓòÉ

Disable EA access system. (1=disable)


ΓòÉΓòÉΓòÉ 2.2.4.2.9. DisableDircount ΓòÉΓòÉΓòÉ

Disable display of subdirectory count. (1=disable)


ΓòÉΓòÉΓòÉ 2.2.4.2.10. LimitSameHost ΓòÉΓòÉΓòÉ

This setting is not IPS hardcoded, but its supported in the rxOnConnect.cmd
script.

The script will default to 2 connections if this variable is not set. Else it
will limit the number of remote hosts that connect at the same time to the
number given here.

ex: 3


ΓòÉΓòÉΓòÉ 2.2.4.3. POP3 parameters ΓòÉΓòÉΓòÉ

No extra parameters, see Common parameters.


ΓòÉΓòÉΓòÉ 2.2.4.4. SMTP parameters ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 2.2.4.4.1. ForwardAddres ΓòÉΓòÉΓòÉ

Like ClientAddress, but control the host allowed to forward message through
this server.

ex: *


ΓòÉΓòÉΓòÉ 2.2.4.4.2. ForwardToServer ΓòÉΓòÉΓòÉ

When set will cause IPS to forward all outgoing message to one specific SMTP
server.

ex: 10.10.10.2


ΓòÉΓòÉΓòÉ 2.2.4.4.3. QueueDirectory ΓòÉΓòÉΓòÉ

Directory messages are queued in.

ex: .\que\mail


ΓòÉΓòÉΓòÉ 2.2.4.4.4. LocalDomains ΓòÉΓòÉΓòÉ

List of domains which are handled by this server.

ex: 127.0.0.1 localhost


ΓòÉΓòÉΓòÉ 2.2.4.5. TELNET parameters ΓòÉΓòÉΓòÉ

No extra parameters, see Common parameters.


ΓòÉΓòÉΓòÉ 2.2.5. Users section ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 2.2.5.1. Username ΓòÉΓòÉΓòÉ

This is the name of the user which must match the file name if the user account
should work. Since file names in OS/2 are not case sensitive this is where
the correct case is important.


ΓòÉΓòÉΓòÉ 2.2.5.2. Fullname ΓòÉΓòÉΓòÉ

Users full name.


ΓòÉΓòÉΓòÉ 2.2.5.3. Aliases ΓòÉΓòÉΓòÉ

User aliases, names the user is also known as. Each name must be separated by a
space.


ΓòÉΓòÉΓòÉ 2.2.5.4. Password ΓòÉΓòÉΓòÉ

Users password encrypted with the .\bin\pwd2. ServerConfig/2 allows you to
automaticaly Generate passwords without the need to use pwd2, just click on the
Generate button.

When making a new user you can add a - in front of a non encrypted password and
it
will be encrypted on the first login. Or just use the button to generate it
on-the-fly.


ΓòÉΓòÉΓòÉ 2.2.5.5. Anonymous ΓòÉΓòÉΓòÉ

Set to True if this is an anonymous user account, else set to False


ΓòÉΓòÉΓòÉ 2.2.5.6. Administrator ΓòÉΓòÉΓòÉ

Set to True if this is an administrative user accounts, else set to False.


ΓòÉΓòÉΓòÉ 2.2.5.7. RootDirectory ΓòÉΓòÉΓòÉ

If this user should have another virtual root then set this. The virtual root
for the
users is the RootDirectory setting in the FTP section + the setting here.


ΓòÉΓòÉΓòÉ 2.2.5.8. LoginDirectory ΓòÉΓòÉΓòÉ

If you want to direct a user to a specified directory at login, please set this
here,
this is relative to the virtual root for the user.


ΓòÉΓòÉΓòÉ 2.2.5.9. ChangePassword ΓòÉΓòÉΓòÉ

Set to True if this account can change its password, else set to False.


ΓòÉΓòÉΓòÉ 2.2.5.10. MaxBandwidth ΓòÉΓòÉΓòÉ

Maximum retrieve bandwidth for each normal user session.
(KB/S)


ΓòÉΓòÉΓòÉ 2.2.5.11. ClientAddress ΓòÉΓòÉΓòÉ

List of IP or Host masks to allow or deny access. First matching mask will be
used.

ex: 127.* !*
Will allow access from all IP's starting with 127. and deny all others.


ΓòÉΓòÉΓòÉ 2.2.5.12. MemberOfGroups ΓòÉΓòÉΓòÉ

List of the groups this user is a member of. ServerConfig/2 allows you to
choose the groups by selecting them from the list box. The syndax in the config
is Group names divided by a space.


ΓòÉΓòÉΓòÉ 2.2.5.13. APOPSecret ΓòÉΓòÉΓòÉ

This is a temporary setting for the POP3 server. This is a password for the POP
command. Its also unencrypted.


ΓòÉΓòÉΓòÉ 2.2.5.14. Statistics ΓòÉΓòÉΓòÉ

IPS stores the individual user statistics. They are read-only and can only be
reset back to zero.

The statistics will not be saved untill you Save the user.

Pressing Cancel will reset the statistics back to normal.


ΓòÉΓòÉΓòÉ 2.3. Firewall ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 2.3.1. Important information ΓòÉΓòÉΓòÉ

FIREWALL Configuration System

OS/2 TCP/IP version 4.1/4.2/4.21 comes with its own firewall. TCP/IP
4.1/4.2/4.21 is BSD 4.4 compliant and the firewall is nearly completely the
same like the AIX/BSD firewall. This configuration system helps you configure
this firewall and allows you to do this in an easy way, since the configuration
files are quite complex.

To use the firewall you need to have the FWIP.SYS loaded from your config.sys,
ServerConfig/2 will notify you if it can't find it there. There are also some
other device drivers that are used by the firewall, but they are optional and
depend only on the types of services, for example MD5.SYS is used for tunneling
encryption.

For the full documentation of the AIX firewall can be found at this PDF file
(3.8megs):
http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg242577.pdf


ΓòÉΓòÉΓòÉ 2.3.2. Firewall Management ΓòÉΓòÉΓòÉ

FIREWALL Management

This notebook page allows you to Start/Stop/Initialize the firewall, and also
change system wide parameters.

Firewall loggin
Enable logging of the firewall. You can define which rules are logged from the
individual rules settings. This setting does not affect the Error log file.

IP Forwarding
Enables IP forwarding, use this if your machine is a router/gateway.

Syn flood protection
Protects you from Syn flood attacks.


ΓòÉΓòÉΓòÉ 2.3.3. Rules ΓòÉΓòÉΓòÉ

FIREWALL Rules

This page controls the rules that the firewall will use to permit or deny
packets. Each line is a different rule, and they are read by the firewall in a
top-to-bottom order. If a packet is matched with a rule, then the action
defined by the rule is done (permit or deny, log etc), else its automaticaly
denied and logged.

You can right-click to get a popup menu, from where you can move rules up and
down. You can also use the menu from the menu bar.

If you double-click on a rule you will get a detailed information window from
where you can change the idividual fields of the rule.


ΓòÉΓòÉΓòÉ 2.3.4. Interfaces ΓòÉΓòÉΓòÉ

FIREWALL Interfaces

This notebook page defines the interfaces that are seen by the firewall as
secure. You can define rules that can apply to secure or non-secure interfaces,
all the interfaces that are not defined here and considered non-secure. You
define not the interface name, but the IP address of the interface.

For example, if you have a connection to the internet and a connection to your
local intranet, you should define the IP address of your intranet here, but not
the IP of the internet connection. Thus you will be able to address them with
different rules.


ΓòÉΓòÉΓòÉ 2.3.5. Error Log ΓòÉΓòÉΓòÉ

FIREWALL Error Log

This page shows you the error log file of the firewall.

If you see an entry like: OPENLOG: facility = 32: error code = 3, it means that
you haven't started the firewall logging facility, you can ignore this error.


ΓòÉΓòÉΓòÉ 3. ServerConfig Daemon ΓòÉΓòÉΓòÉ

ServerConfig Daemon

The Daemon comes in two parts. One is the PM GUI Daemon for OS/2 only, and the
other is the source code in C of the plain Daemon. The later can theoreticaly
be compiled under any unix/linux system. I have tested it with Slackware/RedHat
Linux, FreeBSD and BeOS (!). It can also be compiled under OS/2 with emx/gcc
thus allows you to DETACH it in your config.sys.

The Daemon by default when compiled under unix/linux systems will look for its
configuration file under /etc, and under OS/2 in its current directory. If you
want to specify a different place or name then pass it as a parameter.

Remote configuration works great. I can't guarantee anything, i haven't tested
this feature with many different kinds of systems. Please remember that the
password is not encrypted in any way.

The Daemon is now complete, but remember that if you stop and start it again,
you will get an error from the TCPIP port, thats because the port didn't
timeout, and you'll have to wait or use another port. You can also kill a port
with 3rd pary programs.


ΓòÉΓòÉΓòÉ 4. History ΓòÉΓòÉΓòÉ

History Information

1.3 - New cool features :)

   Thanx go to warper_ and ltning for their patience
   while i was debugging.

   New feature, history support for the last four configs loaded.

   IPS: Improved the code when creating a new configuration.

   Firewall: Complete support for tunneling.

   Firewall: The firewall was enabled by mistake, fixed.

   Firewall: Protocol option was 'any' but must be 'all', fixed.

   Changed colours. If you like them tell me about it.

1.2 - Firewall added!

   Full TCPIP Firewall support. This firewall is included
   in tcpip 4.1/4.2/4.21.

   Support for the new IPS 0.85 version, added all the new
   options, plus some more help support.

   Improved startup speed by 40%, by not loading all the
   notebook pages at once.

   Minor costmetic fixes.

1.1 - Maintenance release.

   Apache: Browse buttons and enhanced listboxes.

   IPS: Browse and Edit buttons on all rexx scripts.

   General cosmetic fixes.

1.0 - This is not a beta anymore :)

   Apache Management system. Allows you to launch,
   initialize and shutdown Apache from ServerConfig/2.
   It can also load WebExplorer or Netscape. Make sure
   you have emxkill.exe in your path or in the current dir.

   New command-line option: "-nolock", prevents locking
   of the configuration file, so that Apache or IPS can
   "rehash" while editing.
   (Requested by ltning from Norway)

   The title bar now shows the current configuration file
   been edited. If its a Remote configuration, then it
   displays the IP address of the remote host.
   (Requested by Thomas from Germany)

   IPS: Auto-generate directory access & permissions! You
   can click on the Generate button to add new lines or
   you can double-click on a line to edit it!

   IPS: Services and Users views can now be viewed as
   Icons or Details. Its also saved in the ini file.

   IPS: Added ClientAddress and MaxBandwidth options
   per user.

   Improved On-line help for Apache.

   Added On-line help for IPS.

   Fixed tabs to place cursor correctly.

   IPS: Users stats page also shows the last date/time
   the user accessed the system.

1.0 pre final - Released to do final test before the final.

   ServerConfig/2 now works under Object REXX.

   Greater speed and improved code.

   INI file that holds the last possition of the window
   on the desktop.

   Fixed the help problem where the help button
   would not work on some systems.

   Command-line bug fixed.

   IPS: User statistics Reset button.

   INSTALLER: Fixed progress bar.

0.9 - Changed interface to a more warp4-look.
  WarpSans font is now used everywhere.

  Added command-line options. Usage:
  ServerConfig.exe -a <full path to apache config>
  ServerConfig.exe -i <full path to IPS config>

  IPS: Comments and extra lines are not lost!
  Thanks go to pfg for the 9 hours of debuging with me :)

  IPS: Fixed bug with user file that doesn't have correct field [].

  IPS: Clone User menu option added. At the moment you can only
  clone one user at a time, the currently sellected one.

  Cosmetic changes + code improvements + lock config file.

0.8 - Fixed buttons to have a bigger responce area.

  Apache: Added the TransferLog directive under Main.

  Installer: Fixed bugs in the installation program, now it doesn't
  have the path length limitation, plus some other cosmetic bugs.

  IPS: Services and Users are in containers now.

  IPS: Full support for user files. Create/Delete/Rename user files,
  Access section per user, and statistics are supported.

  IPS: Updated code to work with the new config options for 0.81.

  IPS: Now you can auto generate passwords if you have pwd2.exe
  in your ips\bin path.

  IPS: The Save function will not save the individual users. This is
  done while editing the users. That allows the management of users
  without the need to change the main configuration.

0.7 - Fixed a bug in the unix/linux daemon with weird characters.

  Updated the progress bar.

  IPS configuration support has finished, although you can't save yet.

  I have included my own configuration for Apache, it used for a real
  server. If help is not enough help, then its a good idea to check it out
  and see what i am using. You can also save it as a file and just make
  few modifications and use it as your own.

0.6 - Added a slider bar to show percent complete of remote save/load.

  Fixed the <FilesMatch directive and moved it with the <Files and
  the <Directory page.

  Fixed the case sensitivity bug with the spin buttons.

  IPS: Most of the work is finished, now individual configuration of
  each service is possible. User configuration is not yet complete.

0.5 - Started support for the InetPowerServer/2. Development has just
  started, and as of this version its not complete.

  Completed the Apache directives documentation, now you can
  press F1 and get help on a particular directive.

  Added support for Redirect and Action directives. ServerConfig/2
  must now support all the config directives.

  LINUX Support! You can now run the Linux version of the daemon
  and you will be able to configure your Linux Apache webserver
  from your OS/2 system. Thanks go to dink for his bugfix.

  Even better news, the source code that is included for the daemon
  will compile and run in every unix/linux system out there, the code
  has been optimized to use system-independed functions.
  This means the daemon will work on FreeBSD, Linux or whatever.
  Thanks go to JE_Hoover for giving me access to his shell.
  Thanks also go to Brian "Beej" Hall, for the great help of his web page.

0.4 - Fixed Daemon's way of shutting down the TCPIP socket.

  Fixed Timeout directive that didn't read correctly.

  Fixed ErrorDocument and BrowserMatch directives, they can be found
  in the Indexing, page 2.

  Remote RESET and SHUTDOWN supported. You need the file emxkill.exe
  in your daemons current directory or in your path.

  Cosmetic changes in the interface.

0.3 - Fixed Save/Save As, now there is no delay, things are saved much faster
  than before. Thanx go to JE_Hoover for helping me.

  Added backed files support. Now when you save/save as, and the file
  already exists, it will be renamed to .bak.

  New/Load/Save buttons on the main window, New option in menu.

  Partial help support.

  New icons.

  Remote configuration support.

0.2 - Fixed bug in Save, Indexing would get lost. Save As.. worked fine though.
  Thanx go to Paulchen for pointing out the problem.

0.1 - Initial release


ΓòÉΓòÉΓòÉ 5. Future ΓòÉΓòÉΓòÉ

Ideas for future releases

1) I want to add encryption for the password, and a few
 other commands like starting the server from remote.

2) Support for SQL and SSL configurations.

3) Add container/icons support for individual VirtualHosts.

Please send me your ideas.


ΓòÉΓòÉΓòÉ 6. Feedback ΓòÉΓòÉΓòÉ

Feedback Information

You can contact the author in the following places:

Email: [e-mail]
IRC: sehh in efnet

Please send me your suggestions and comments.

Latest versions of ServerConfig/2 can be found in this website:

http://www.ecs.soton.ac.uk/~dm898/sc/