From: William A. Rowe Jr Date: Mon, 6 Aug 2001 19:42:42 +0000 (+0000) Subject: Gone, see .html.en flavors X-Git-Tag: 2.0.23~45 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d51dbc722992d7b90a1c00a84d3f16c5a7c6b158;p=apache Gone, see .html.en flavors git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@89951 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/new_features_2_0.html b/docs/manual/new_features_2_0.html deleted file mode 100644 index 8bb0dc4944..0000000000 --- a/docs/manual/new_features_2_0.html +++ /dev/null @@ -1,99 +0,0 @@ - - -New features with Apache 2.0 - - - - - -

Overview of New Features in Apache 2.0

- -

Enhancements: Core | Module - -

- -

Core Enhancements:

- -

Unix Threading -: On Unix systems with POSIX threads support, Apache can now run in a - hybrid multiprocess, multithreaded mode. This should improve - scalability. - -
New Build System -: The build system has been rewritten from scratch to be based on - autoconf and libtool. This makes Apache's configuration system more - similar to that of other packages. - -
Multiprotocol Support -: Apache now has some of the infrastructure in place to support serving - multiple protocols. mod_echo has been written as an example. - -
Better support for non-Unix platforms: Apache - 2.0 is faster and more stable on non-Unix platforms such as BeOS, - OS/2, and Windows. With the introduction of platform-specific multi-processing modules (MPMs) and the Apache - Portable Runtime (APR), these platforms are now implemented in their - native API, avoiding the often buggy and poorly performing - POSIX-emulation layers. - -
New Apache API -: The API for modules has changed significantly for 2.0. Many of the - module-ordering problems from 1.3 should be gone. 2.0 does much of - this automatically, and module ordering is now done per-hook to - allow more flexibility. Also, new calls have been added that provide - additional module capabilities without patching the core Apache server. - -
IPv6 Support: On systems where IPv6 is supported by the underlying Apache - Portable Runtime library, Apache gets IPv6 listening sockets by - default. Additionally, the Listen, NameVirtualHost, and - <VirtualHost> directives support IPv6 numeric address - strings (e.g., "Listen [fe80::1]:8080").
Filtering: Apache modules may now be written as filters which act on the - stream of content as it is delivered to or from the server. This - allows, for example, the output of CGI scripts to be parsed for - Server Side Include directive by mod_include.

- -

Module Enhancements:

- -

mod_auth_db -: Now supports Berkely DB 3.0 - -
mod_auth_digest -: Includes additional support for session caching across processes -using shared memory. - -
mod_charset_lite: New module in Apache 2.0. -This experimental module allows for character set translation -or recoding. - -
mod_dav -: New module in Apache 2.0. This module implements the -HTTP Distributed Authoring and Versioning (DAV) specification for -posting and maintaining web content. - -
mod_file_cache -: New module in Apache 2.0. This module includes the functionality -of mod_mmap_static in Apache 1.3, plus adds further caching abilities. - -
mod_headers -: This module is much more flexible in Apache 2.0. It can now -modify request headers used by mod_proxy, and it can conditionally set -response headers. - -

- - - - - diff --git a/docs/manual/upgrading.html b/docs/manual/upgrading.html deleted file mode 100644 index 901927f595..0000000000 --- a/docs/manual/upgrading.html +++ /dev/null @@ -1,156 +0,0 @@ - - -Upgrading to 2.0 from 1.3 - - - - - -

Upgrading to 2.0 from 1.3

- -

In order to assist folks upgrading, we maintain a document -describing information critical to existing Apache users. These are -intended to be brief notes, and you should be able to find more -information in either the New -Features document, or in the src/CHANGES file. - -

Compile-Time Configuration Changes

- -

Apache now uses an autoconf and libtool -system for configuring the build processes. -Using this system is similar to, but not the same as, using the APACI -system in Apache 1.3.
In addition to the usual selection of modules which you can choose -to compile, Apache 2.0 has moved the main part of request processing -into Multi-Processing Modules (MPMs).

- -

Run-Time Configuration Changes

- -

Many directives that were in the core server in Apache 1.3 -are now in the MPMs. If you wish the behavior of the server -to be as similar as possible to the behavior of Apache 1.3, -you should select the prefork -MPM. Other MPMs will have different directives to control process -creation and request processing.
Server-Side Includes provided by mod_include are now implemented using -the new -filter system rather than as a handler. -This provides much more power and flexibility, but requires -the use of the SetOutputFilter -to activate server-parsed content. If you were using -AddHandler server-parsed .shtml, you can get -similar functionality using -
-<FilesMatch "\.shtml(\..+)?$"> - SetOutputFilter INCLUDES -</FilesMatch> -
The CacheNegotiatedDocs directive now takes -the argument on or off. Existing -instances of CacheNegotiatedDocs should be replaced -with CacheNegotiatedDocs on.
The ErrorDocument directive no longer uses a quote at -the beginning of the argument to indicate a text message. Instead, -you should enclose the message in double quotes. For example, -existing instances of
ErrorDocument 403 "Some -Message
should be replaced with -
ErrorDocument 403 "Some -Message"
As long as the second argument is not a -valid URL or pathname, it will be treated as a text message.
The AccessConfig and ResourceConfig -directives no longer exist. Existing instances of these directives -can be replaced with the Include directive which -has equivalent functionality. If you were making use of the default -values of these directives without including them in the configuration -files, you may need to add Include conf/access.conf and -Include conf/srm.conf to your httpd.conf. In order to -assure that Apache reads the configuration files in the same order as -was implied by the older directives, the Include -directives should be placed at the end of httpd.conf, with the one for -srm.conf preceding the one for -access.conf.
The BindAddress directive no longer exists. -Equivalent functionality is provided with the more flexible Listen directive. - -
The ServerType directive no longer exists. -The method used to serve requests is now determined by the selection -of MPM. There is currently no MPM designed to be launched by -inetd.
The mod_log_agent and mod_log_referer modules which provided the -AgentLog, RefererLog and -RefererIgnore directives have been removed. Agent and -referer logs are still available using the CustomLog directive of -mod_log_config.
The AddModule and ClearModuleList -directives no longer exist. These directives where used to ensure -that modules could be enabled in the correct order. The new -Apache 2.0 API allows modules to explicitly specify their ordering, -eliminating the need for these directives.

- -

Misc Changes

- -

Graceful restarts of the server are now executed by signaling the -parent process with WINCH rather than -USR1.
The httpd command line option -S -which was used for printing the virtual host configuration has -been replaced by -t -D DUMP_VHOSTS.
The httpd command line option -X has -been removed. Most MPMs allow the same functionality to be requested -by using the -D ONE_PROCESS command line -option. In addition, a -D NO_DETACH command line -option is available.
The module mod_auth_digest, which was experimental in Apache 1.3 -is now a standard module.
The mod_mmap_static module, which was experimental in Apache 1.3 -has been replaced with mod_file_cache.
The distribution has been completely reorganized so that it no -longer contains an independent src directory. Instead, -the sources are logically organized under the main distribution -directory, and installations of the compiled server should be -directed to a separate directory.

- -

Third Party Modules

- -

Extensive changes were made to the server API in Apache 2.0. -Existing modules designed for the Apache 1.3 API will not -work in Apache 2.0 without modification. Details are provided in -the developer documentation.

- - - -