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
Run-Time Configuration Changes
Misc Changes
Third Party Modules

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.
The proxy module has been revamped to bring it up to HTTP/1.1. Among the important changes, proxy access control is now placed inside a <Proxy> block rather than a <Directory proxy:> block.
The handling of PATH_INFO (trailing path information after the true filename) has changed for some modules. Modules that were previously implemented as a handler but are now implemented as a filter may no longer accept requests with PATH_INFO. Filters such as INCLUDES are implemented on top of the core handler, and therefore reject requests with PATH_INFO. You can use the AcceptPathInfo directive to force the core handler to accept requests with PATH_INFO and thereby restore the ability to use PATH_INFO in server-side includes.
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 and Port directives no longer exist. Equivalent functionaliHTTP/1.1 200 OK Date: Mon, 07 Jul 2025 06:16:40 GMT Server: Apache/2.0.42 (Win32) PHP/5.2.10 Content-Location: upgrading.html.en Vary: negotiate,accept-language,accept-charset TCN: choice Accept-Ranges: bytes Content-Length: 10652 Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Content-Type: text/html; charset=ISO-8859-1 Content-Language: en Upgrading to 2.0 from 1.3 - Apache HTTP Server
Modules | Directives | FAQ | Glossary | Sitemap
Apache HTTP Server Version 2.0
Apache > HTTP Server > Documentation > Version 2.0
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