This commit was manufactured by cvs2svn to create branch

New features with this release, as extensions of the Apache functionality

(see also more detailed CHANGES file) in the source directory. For more

information, see http://www.apache.org/docs/1.1/

In addition to a number of bug fixes and internal performance

enhancements, Apache 1.1 has the following specific new user

features:

  *) Caching Proxy Server

       Apache can now act as an HTTP proxy server, allowing clients

       behind firewalls to use the server to access the outside world. In

       addition, it can cache documents it proxies, speeding up access to

       frequently requested documents.

  *) Filetype-based Script "Actions"

       You can now run CGI scripts whenever a file of a certion type is

       requested. Makes it much easier to execute scripts that process

       files.

  *) Support for Keep-Alive Persistent Connections

       Apache now has (optional) support for persistent connections, as

       defined by the HTTP/1.1 draft. This protocol, supported by a

       number of current HTTP servers and browsers (including Netscape

       Navigator 2.0) has been shown to increase speed of document

       transfer by up to 50% in certain cases.

  *) Customizable CGI Environment Variables (not in this release)

       New PassEnv and SetEnv directives allow you to modify the

       environment variables passed to CGI scripts

  *) CERN Metafile Support

       Now emulates the CERN httpd's support for metafiles containing

       additional HTTP headers to be supplied with a document.

  *) Redirect Now Usable in .htaccess Files

       The Redirect directive can now be used in .htaccess files when the

       FileInfo directive has been set on. This allows users to redirect

       parts of their directories without requiring CGI scripts

  *) Improved UserDir Directive (not in this release)

       Now supports the ability to point user's files (as specificed by

       URLs beginning with the "~" character) at directories other than

       those specified by the Unix password file.

  *) Minimal DNS Now Runtime Option

       New HostnameLookups server configuration directive can be used to

       turn On or  Off DNS lookups. This supercedes the -DMINIMAL_DNS

       compile-time configuration option.

  *) Listen to Multiple Addresses and Ports

       Using the new Listen directive, Apache can listen to more than one

       port and IP address, using the same configuration set.

  *) Anonymous HTTP Logins

       New options allow you to allow, using Basic HTTP Authentication,

       anonymous logins, like those of FTP. This allows you to collect

       email addresses of people accessing your site.

  *) File Owner Avialable to Included CGI Scripts

       Server-side includes that call CGI scripts will now set a

       USER_NAME environment variable that contains the owner of the file

       which included it.

  *) Improved Icons

       Thanks to Kevin Hughes, Apache's nifty color GIF icons for

       directory listings have been updated. In addition, the Powered by

       Apache (apache_pb.gif) logo has been included.

  *) Log Rotation

	New support utility to allow log rotation without shutting down the

	server. See support/rotatelogs.c.

NEW AUTHENTICATION MODULES:

Note: These modules are not compiled into the server by default, as

they require special support on the host system. They must be enabled

specifically in the Configuration file.

  *) Support for Unix DB Authentication - mod_db.c

       In addition to DBM support, Apache now contains optional support

       for Berkeley DB databases.

  *) mSQL Database Authentication - mod_auth_msql.html

       Support for the use of mSQL databases for user authentication via

       HTTP is now supported.

/* ====================================================================

 * Copyright (c) 1995 The Apache Group.  All rights reserved.

 *

 * Redistribution and use in source and binary forms, with or without

 * modification, are permitted provided that the following conditions

 * are met:

 *

 * 1. Redistributions of source code must retain the above copyright

 *    notice, this list of conditions and the following disclaimer. 

 *

 * 2. Redistributions in binary form must reproduce the above copyright

 *    notice, this list of conditions and the following disclaimer in

 *    the documentation and/or other materials provided with the

 *    distribution.

 *

 * 3. All advertising materials mentioning features or use of this

 *    software must display the following acknowledgment:

 *    "This product includes software developed by the Apache Group

 *    for use in the Apache HTTP server project (http://www.apache.org/)."

 *

 * 4. The names "Apache Server" and "Apache Group" must not be used to

 *    endorse or promote products derived from this software without

 *    prior written permission.

 *

 * 5. Redistributions of any form whatsoever must retain the following

 *    acknowledgment:

 *    "This product includes software developed by the Apache Group

 *    for use in the Apache HTTP server project (http://www.apache.org/)."

 *

 * THIS SOFTWARE IS PROVIDED BY THE APACHE GROUP ``AS IS'' AND ANY

 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE APACHE GROUP OR

 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

 * OF THE POSSIBILITY OF SUCH DAMAGE.

 * ====================================================================

 *

 * This software consists of voluntary contributions made by many

 * individuals on behalf of the Apache Group and was originally based

 * on public domain software written at the National Center for

 * Supercomputing Applications, University of Illinois, Urbana-Champaign.

 * For more information on the Apache Group and the Apache HTTP server

 * project, please see <http://www.apache.org/>.

 *

 */

                                 Apache

                             Version 1.1 (and up)

What is it?

-----------

Apache is an HTTP server designed as a plug-in replacement for the NCSA

server version 1.3 (or 1.4). It fixes numerous bugs in the NCSA server and

includes many frequently requested new features, and has an API which

allows it to be extended to meet users' needs more easily.

Documentation

-------------

All the documentation is on-line on the WWW, via <URL:http://www.apache.org/>.

Installation

------------

Unless you grabbed a binary distribution of Apache, you must compile

it for your specific platform.  In order to compile it, you must set

compile-time options (in particular, system type) for your system by

editing a Configuration file, run a script which generates a Makefile

and a small piece of C code, and then compile it.

For instructions on compilation, see the file 'INSTALL' in the src/ directory.

After compilation, you will have a binary called "httpd" in the src/

directory.  If you received a binary distribution of apache, you

should have this file already.

The next step is to edit the configuration files for the server.  In

the subdirectory called "conf" you should find distribution versions

of the three configuration files: srm.conf-dist, access.conf-dist, and

httpd.conf-dist.  Copy them to srm.conf, access.conf, httpd.conf

respectively.

First edit httpd.conf.  This sets up general attributes about the

server - the port number, the user it runs as, etc.  Next edit the

srm.conf file - this sets up the root of the document tree, special

functions like server-parsed HTML or internal imagemap parsing, etc.

Finally, edit the access.conf file to at least set the base cases of

access. Documentation for all of these is located at

<URL:http://www.apache.org/docs/>.

Finally, make a call to httpd, with a -f to the full path to the

httpd.conf file.  I.e., the common case:

  /usr/local/etc/apache/src/httpd -f /usr/local/etc/apache/conf/httpd.conf

And voila!  The server should be running.

By default the srm.conf and access.conf files are located by name - to

specifically call them by other names, use the AccessConfig and

ResourceConfig directives in httpd.conf.

The Latest Version

------------------

Details of the latest version are in the apache project page (above).

NOTE: At the time of release of Apache 1.1, two modules had updated

versions which were not sufficiently tested for inclusion into the 1.1

distribution: mod_auth_msql and mod_cern_meta.  The newer versions are

available from http://www.apache.org/dist/contrib/modules/ - if you

plan on using this functionality we encourage you to give the newer

modules a test drive, and let us know of any problems.  In particular,

mod_cern_meta is now configurable per-directory, and the configuration

directives have changed.  We can not promise that the existing

configuration directives provided by the mod_cern_meta included in the

distribution will be supported in the future.

Licencing

---------

Please see the file called LICENSE.

1. Don't commit several unrelated changes in one go. Each change should be

committed separately (that is, it can affect multiple files, but it should all

be part of a single change).

2. When committing, make sure that the CVS log message explains what the

patches do and why.

3. Don't edit CHANGES files unless there is a change which is visible to a user

of Apache. CVS logs provide a detailed history of all changes (if people follow

rule 2), so there is no need to duplicate it in CHANGES.

4. Don't change src/Configuration.tmpl to your local configuration. Copy it to

Configuration (which is _not_ version controlled) and change that.

#!/usr/local/bin/perl

print "Content-type: text/html\n\n";

while (($key, $val) = each %ENV) {

	print "$key = $val<BR>\n";

}