httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stodd...@hyperreal.org
Subject cvs commit: apache-1.3/htdocs/manual/mod core.html
Date Tue, 18 Jan 2000 19:33:04 GMT
stoddard    00/01/18 11:32:58

  Modified:    htdocs/manual dso.html new_features_1_3.html
               htdocs/manual/mod core.html
  Added:       conf     httpd.conf-dist.nw
               htdocs/manual netware.html
  Log:
  Documentation for the Netware port
  Submitted by:	Mike Gardiner
  
  Revision  Changes    Path
  1.1                  apache-1.3/conf/httpd.conf-dist.nw
  
  Index: httpd.conf-dist.nw
  ===================================================================
  #
  # 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
  # sys:/apache/conf/srm.conf and then sys:/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 and
  # sys:/ for NetWare), 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 "sys:/apache"
  
  #
  # 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_status
  
  #
  # 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
  
  #
  # Number of concurrent threads (i.e., requests) the server will allow.
  # Set this value according to the responsiveness of the server (more
  # requests active at once means they're all handled more slowly) and
  # the amount of system resources you'll allow the server to consume.
  #
  ThreadsPerChild 50
  
  #
  # When NetWare creates a thread you need to specify the stack size.
  # You may need to increase this if you get stack overflows.
  # ThreadStackSize 65536
  
  ThreadStackSize 65536
  
  #
  # 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.
  
  # LoadModule anon_auth_module modules/authanon
  # LoadModule cern_meta_module modules/cernmeta
  # LoadModule digest_module modules/digest
  # LoadModule expires_module modules/expires
  # LoadModule headers_module modules/headers
  # LoadModule proxy_module modules/proxy
  # LoadModule rewrite_module modules/rewrite
  # LoadModule speling_module modules/speling
  # LoadModule status_module modules/status
  # LoadModule info_module modules/info
  # LoadModule usertrack_module modules/usrtrack
  
  #
  # 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.
  #
  
  #
  # Port: The port to which the standalone server listens. For
  # ports < 1023, you will need httpd to be run as root initially.
  #
  Port 80
  
  #
  # 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 someone@somewhere.com
  
  #
  # 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 123.45.67.89
  
  #
  # 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 "sys:/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.  
  #
  <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 "sys:/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 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/ "sys:/apache/icons/"
  
  <Directory "sys:/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/ "sys:/apache/cgi-bin/"
  
  #
  # "sys:/apache/cgi-bin" should be changed to whatever your ScriptAliased
  # CGI directory exists, if you have that configured.
  #
  <Directory "sys:/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
  
  #
  # 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 "sys:/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 123.45.67.89:8080
  
  
  #
  # VirtualHost example:
  # Almost any Apache directive may go into a VirtualHost container.
  #
  #<VirtualHost ip.address.of.host.some_domain.com>
  #    ServerAdmin webmaster@host.some_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>
  
  
  
  
  1.15      +1 -0      apache-1.3/htdocs/manual/dso.html
  
  Index: dso.html
  ===================================================================
  RCS file: /home/cvs/apache-1.3/htdocs/manual/dso.html,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- dso.html	1999/06/23 06:55:25	1.14
  +++ dso.html	2000/01/18 19:32:40	1.15
  @@ -193,6 +193,7 @@
   o  Mac OS             (10.0 preview 1)
   o  OpenStep/Mach      (4.2)
   o  DGUX               (??)
  +o  NetWare            (5.1)
   </PRE>
   
   <P>
  
  
  
  1.81      +5 -2      apache-1.3/htdocs/manual/new_features_1_3.html
  
  Index: new_features_1_3.html
  ===================================================================
  RCS file: /home/cvs/apache-1.3/htdocs/manual/new_features_1_3.html,v
  retrieving revision 1.80
  retrieving revision 1.81
  diff -u -r1.80 -r1.81
  --- new_features_1_3.html	1999/08/02 10:13:40	1.80
  +++ new_features_1_3.html	2000/01/18 19:32:42	1.81
  @@ -37,12 +37,15 @@
       modules can be loaded into the server process space only when necessary,
       thus overall memory usage by Apache will be significantly reduced.  DSO
       currently is supported on FreeBSD, OpenBSD, NetBSD, Linux, Solaris, SunOS,
  -    Digital UNIX, IRIX, HP/UX, UnixWare, AIX, ReliantUnix and generic SVR4
  -    platforms.
  +    Digital UNIX, IRIX, HP/UX, UnixWare, NetWare, AIX, ReliantUnix and generic
  +    SVR4 platforms.
   
   <DT><STRONG><A HREF="windows.html">Support for Windows NT/95</A></STRONG>
   <DD>Apache now experimentally supports the Windows NT and Windows 95
       operating systems.
  +
  +<DT><STRONG><A HREF="netware.html">Support for NetWare 5.x</A></STRONG>
  +<DD>Apache now experimentally supports the NetWare 5.x operating systems.
   
   <DT><STRONG><A HREF="sourcereorg.html">Re-organized 
       Sources</A></STRONG>
  
  
  
  1.1                  apache-1.3/htdocs/manual/netware.html
  
  Index: netware.html
  ===================================================================
  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  <HTML>
  <HEAD>
  <TITLE>Using Apache with Novell NetWare 5</TITLE>
  </HEAD>
  
  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  <BODY
   BGCOLOR="#FFFFFF"
   TEXT="#000000"
   LINK="#0000FF"
   VLINK="#000080"
   ALINK="#FF0000"
  >
  <!--#include virtual="header.html" -->
  
  <H1 ALIGN="CENTER">Using Apache With Novell NetWare 5</H1>
  
  <P>This document explains how to install, configure and run
     Apache 1.3 under Novell NetWare 5. Please note that at
     this time, NetWare support is entirely experimental, and is
     recommended only for experienced users. The Apache Group does not
     guarantee that this software will work as documented, or even at
     all. If you find any bugs, or wish to contribute in other ways, please
     use our <A HREF="http://www.apache.org/bug_report.html">bug reporting
     page.</A></P>
  
  <P><STRONG>Warning: Apache on NetWare has not yet been optimized for performance.
  Apache still performs best, and is most reliable on Unix platforms.  Over
  time we will improve NetWare performance. Folks doing comparative reviews
  of webserver performance are asked to compare against Apache
  on a Unix platform such as Solaris, FreeBSD, or Linux.</STRONG></P>
  
  <P>
  
  Most of this document assumes that you are installing Apache from a
  binary distribution. If you want to compile Apache yourself (possibly
  to help with development, or to track down bugs), see the section on
  <A HREF="#comp">Compiling Apache for NetWare</A> below.
  
  <HR>
  
  <UL>
    <LI><A HREF="#req">Requirements</A>
    <LI><A HREF="#down">Downloading Apache for NetWare</A>
    <LI><A HREF="#inst">Installing Apache for NetWare</A>
    <LI><A HREF="#run">Running Apache for NetWare</A>
    <LI><A HREF="#use">Using Apache for NetWare</A>
    <LI><A HREF="#comp">Compiling Apache for NetWare</A>
  </UL>
  
  <HR>
  
  <H2><A NAME="req">Requirements</A></H2>
  
  Apache 1.3 is designed to run on NetWare 5.0 and 5.1.
  <P>
  
  <STRONG>If running on NetWare 5.0 you must install Service Pack 4.</STRONG>
  
  <P>
  <P>
  
  Service pack 4 is available <A HREF="http://support.novell.com/misc/patlst.htm#nw">here.</A>
  
  <H2><A NAME="down">Downloading Apache for NetWare 5</A></H2>
  
  <P>Information on the latest version of Apache can be found on the
  Apache web server at <A
  HREF="http://www.apache.org/">http://www.apache.org/</A>.  This will
  list the current release, any more recent alpha or beta-test releases,
  together with details of mirror web and anonymous ftp sites.</P>
  
  <P>
  <H2><A NAME="inst">Installing Apache for NetWare</A></H2>
  
  There is no Apache install program for NetWare currently.  You will need
  to compile apache and copy the files over to the server manually.  An
  install program will be posted at a later date.
  <P>
  Follow these steps to install Apache on NetWare (assuming you will install to sys:/apache):
  
  <UL>
    <LI>Create a directory called <CODE>Apache</CODE> on a NetWare volume
    <LI>Copy Apache.nlm, Apachec.nlm, htdigest.nlm, and htpasswd.nlm to sys:/apache
    <LI>Create a directory under <CODE>sys:/Apache</CODE> called <CODE>conf</CODE>
    <LI>Copy all the *.conf-dist-nw files to the <CODE>sys:/apache/conf</CODE>
directory
        and rename them all as *.conf files
    <LI>Copy the mime.types and magic files to sys:/apache/conf directory
    <LI>Copy all files and subdirectories of \apache-1.3\htdocs to sys:/apache/htdocs
and
        rename the proper index file (index.html.en) to index.html
    <LI>Copy all files and subdirectories in \apache-1.3\icons to sys:/apache/icons
    <LI>Create the directory sys:/apache/logs on the server
    <LI>Create the directory sys:/apache/cgi-bin on the server
    <LI>Create the directory sys:/apache/modules and copy all nlm modules built into
the
        modules directory
    <LI>Edit the httpd.conf file setting ServerRoot and ServerName to reflect your correct
        server settings
    <LI>Add <CODE>sys:/apache</CODE> to the search path.  EXAMPLE: search
add sys:\apache
  </UL>
  
  <P>Apache may be installed to other volumes besides the default <CODE>sys</CODE>
volume.
  
  <H2><A NAME="run">Running Apache for NetWare</A></H2>
  
  To start Apache just type <STRONG>apache</STRONG> at the console.  This
  will load apache in the OS address space.  If you prefer to load
  Apache in a protected address space you may specify the address space
  with the load statement as follows:
  <P>
  <PRE>
      load address space = apache apache
  </PRE>
  <P>
  This will load Apache into an address space called apache. Running multiple instances
  of Apache concurrently on NetWare is possible by loading each instance into its own
  protected address space.
  
  <P>
  After starting Apache it will be listening to port 80 (unless you
  changed the <SAMP>Port</SAMP>, <SAMP>Listen</SAMP> or
  <SAMP>BindAddress</SAMP> directives in the configuration files).
  To connect to the server and access the default page, launch a browser
  and enter the server's name or address.
  
  This should respond with a welcome page, and a link to the Apache
  manual. If nothing happens or you get an error, look in the
  <SAMP>error_log</SAMP> file in the <SAMP>logs</SAMP> directory.
  
  <P>
  
  Once your basic installation is working, you should configure it
  properly by editing the files in the <SAMP>conf</SAMP> directory.
  
  <P>
  To unload Apache running in the OS address space just type the
  following at the console:
  <PRE>
      unload apache
  </PRE>
  If apache is running in a protected address space specify the 
  address space in the unload statement:
  <PRE>
      unload address space = apache apache
  </PRE>
  
  <P>
  When working with Apache it is important to know how it will find the
  configuration files.  You can specify a configuration file on the command line
  in two ways:
  
  <UL>
  <LI>-f specifies a path to a particular configuration file
  </UL>
  <PRE>    apache -f "vol:/my server/conf/my.conf"</PRE>
  <PRE>    apache -f test/test.conf</PRE>
  
  In these cases, the proper ServerRoot should be set in the configuration file.
  
  <P>
  
  If you don't specify a configuration file name with -f, Apache will
  use the file name compiled into the server, usually "conf/httpd.conf".  Invoking
  Apache with the -V switch will display this value labeled as SERVER_CONFIG_FILE.
  Apache will then determine its ServerRoot by trying the following, in this order:
  
  <UL>
  <LI>A ServerRoot directive via a -C switch.
  <LI>The -d switch on the command line.
  <LI>Current working directory
  <LI>The server root compiled into the server.
  </UL>
  
  <P>
  The server root compiled into the server is usually "sys:/apache".
  invoking apache with the -V switch will display this value
  labeled as HTTPD_ROOT.
  
  <H2><A NAME="use">Configuring Apache for NetWare</A></H2>
  
  Apache is configured by files in the <SAMP>conf</SAMP>
  directory. These are the same as files used to configure the Unix
  version, but there are a few different directives for Apache on
  NetWare. See the <A HREF="./">Apache documentation</A> for all the
  available directives.
  
  <P>
  
  The main differences in Apache for NetWare are:
  
  <UL>
    <LI><P>Because Apache for NetWare is multithreaded, it does not use a
        separate process for each request, as Apache does with
        Unix. Instead there are only threads running: a parent thread, and
        a child which handles the requests. Within the child each request is
        handled by a separate thread.
        <P>
  
        So the "process"-management directives are different:
        <P><A
           HREF="mod/core.html#maxrequestsperchild">MaxRequestsPerChild</A>
           - Like the Unix directive, this controls how many requests a
             process will serve before exiting. However, unlike Unix, a
             process serves all the requests at once, not just one, so if
             this is set, it is recommended that a very high number is
             used. The recommended default, <CODE>MaxRequestsPerChild
             0</CODE>, does not cause the process to ever exit.
        <P><A HREF="mod/core.html#threadsperchild">ThreadsPerChild</A> -
           This directive is new, and tells the server how many threads it
           should use. This is the maximum number of connections the server
           can handle at once; be sure and set this number high enough for
           your site if you get a lot of hits. The recommended default is
           <CODE>ThreadsPerChild 50</CODE>.
        </P><A HREF="mod/core.html#threadstacksize">ThreadStackSize</A>
-
           This directive tells the server what size of stack to use for
           the individual threads.  The recommended default is
           <CODE>ThreadStackSize 65536</CODE>.
        <P>
    <LI><P>The directives that accept filenames as arguments now must use
        NetWare filenames instead of Unix ones. However, because Apache
        uses Unix-style names internally, you must use forward slashes, not
        backslashes. Volumes can be used; if omitted, the drive with the
        Apache executable will be assumed.</P>
    <LI><P>Apache for NetWare contains the ability to load modules at runtime,
        without recompiling the server. If Apache is compiled normally, it
        will install a number of optional modules in the
        <CODE>\Apache\modules</CODE> directory. To activate these, or other
        modules, the new <A HREF="mod/mod_so.html#loadmodule">LoadModule</A>
        directive must be used. For example, to active the status module,
        use the following (in addition to the status-activating directives
        in <CODE>access.conf</CODE>):</P>
  <PRE>
      LoadModule status_module modules/status
  </PRE>
        <P>Information on <A HREF="mod/mod_so.html#creating">creating loadable
           modules</A> is also available.</P>
  </UL>
  
  <H2><A NAME="comp">Compiling Apache for NetWare</A></H2>
  
  <P>Compiling Apache requires MetroWerks CodeWarrior 5 to be properly
     installed. 
     
  <P>First, unpack the Apache distribution into an appropriate
     directory.  Then go to the <CODE>src</CODE> subdirectory of the Apache
     distribution and unzip <CODE>ApacheNW.mcp.gz</CODE>. You may use a
     recent version of WinZip to accomplish this or gzip for Windows. The main
     Metrowerks project file for Apache <CODE>(ApacheNW.mcp)</CODE> is now ready
     to use. Just double click on it from within explorer and it should
     automatically launch MetroWerks CodeWarrior.
  </P>
  
  <P>All major pieces of Apache may be built using the ApacheNW.mcp project
     file. This includes modules such as status, info, and proxy. In addition,
     the following project files have been provided as well:
  <PRE>   
         /apache-1.3/src/support/htpasswd.mcp.gz
         /apache-1.3/src/support/htdigest.mcp.gz
  </PRE>
  
  </P>
  <CODE>htpasswd.mcp.gz</CODE> and <CODE>htdigest.mcp.gz</CODE> will
also need
  to be unzipped before they can be used with MetroWerks CodeWarrior.
  
  <P>Once Apache has been compiled, it needs to be installed in its server
     root directory. The default is the <CODE>sys:/Apache</CODE>
     directory. </P>
  <P>
  Before running the server you must fill out the conf directory.
  Copy the *.conf-dist-nw from the distribution conf directory
  and rename *.conf.  Edit the ServerRoot entries to your
  actual server root (for example "sys:/apache").  Copy over
  the conf/magic and conf/mime.types files as well.
  
  <!--#include virtual="footer.html" -->
  </BODY>
  </HTML>
  
  
  
  
  1.162     +34 -4     apache-1.3/htdocs/manual/mod/core.html
  
  Index: core.html
  ===================================================================
  RCS file: /home/cvs/apache-1.3/htdocs/manual/mod/core.html,v
  retrieving revision 1.161
  retrieving revision 1.162
  diff -u -r1.161 -r1.162
  --- core.html	2000/01/12 15:54:46	1.161
  +++ core.html	2000/01/18 19:32:49	1.162
  @@ -88,6 +88,7 @@
   <LI><A HREF="#servertype">ServerType</A>
   <LI><A HREF="#startservers">StartServers</A>
   <LI><A HREF="#threadsperchild">ThreadsPerChild</A>
  +<LI><A HREF="#threadstacksize">ThreadStackSize</A>
   <LI><A HREF="#timeout">TimeOut</A>
   <LI><A HREF="#usecanonicalname">UseCanonicalName</A>
   <LI><A HREF="#user">User</A>
  @@ -3043,7 +3044,7 @@
   <A
    HREF="directive-dict.html#Status"
    REL="Help"
  -><STRONG>Status:</STRONG></A> core (Windows)<BR>
  +><STRONG>Status:</STRONG></A> core (Windows, NetWare)<BR>
   <STRONG>Compatibility:</STRONG> Available only with Apache 1.3 and later
   with Windows
   
  @@ -3058,6 +3059,38 @@
   
   <HR>
   
  +<H2><A NAME="threadstacksize">ThreadStackSize</A></H2>
  +<A
  + HREF="directive-dict.html#Syntax"
  + REL="Help"
  +><STRONG>Syntax:</STRONG></A> ThreadStackSize <EM>number</EM><BR>
  +<A
  + HREF="directive-dict.html#Default"
  + REL="Help"
  +><STRONG>Default:</STRONG></A> <CODE>ThreadStackSize 65536</CODE><BR>
  +<A
  + HREF="directive-dict.html#Context"
  + REL="Help"
  +><STRONG>Context:</STRONG></A> server config<BR>
  +<A
  + HREF="directive-dict.html#Status"
  + REL="Help"
  +><STRONG>Status:</STRONG></A> core (NetWare)<BR>
  +<STRONG>Compatibility:</STRONG> Available only with Apache 1.3 and later
  +with NetWare
  +
  +<P>This directive tells the server what stack size to use for each of the
  +   running threads. If you ever get a stack overflow you will need to bump
  +   this number to a higher setting.
  +   
  +<P>This directive has no effect on other systems.
  +<HR>
  +
  +
  +
  +
  +
  +
   <H2><A NAME="timeout">TimeOut directive</A></H2>
   <!--%plaintext &lt;?INDEX {\tt TimeOut} directive&gt; -->
   <A
  @@ -3144,9 +3177,6 @@
   ancient clients that do not provide a <CODE>Host:</CODE> header. With
   this option Apache does a reverse DNS lookup on the server IP address
   that the client connected to in order to work out self-referential URLs.
  -This can have adverse performance implications, especially if you use
  -<CODE>%V</CODE> in a <A HREF="mod_log_config.html#customlog">CustomLog</A>

  -directive.
   
   <P><STRONG>Warning:</STRONG> if CGIs make assumptions about the values
of
   <CODE>SERVER_NAME</CODE> they may be broken by this option.  The client
  
  
  

Mime
View raw message