an X application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 9.3.9 Recording changes in configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 2.10 The categorization of standard package views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 2.11 List permissions (before the full security review) • Don’t leave your root shell until you TEST your changes • Always have an alternative boot media (USB memory stick, CD, …) Some quotes for new users Here

find more information in either the New Features document, or in the src/CHANGES file. This document describes only the changes from 2.0 to 2.2. If you are upgrading from version 1.3, you should also consult upgrading document. See also Overview of new features in Apache 2.2 Compile Time Configuration Changes The compilation process is very similar to the one used in version 2.0. Your old configure command significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: mod_imap has been renamed to mod_imagemap

find more information in either the New Features document, or in the src/CHANGES file. This document describes only the changes from 2.0 to 2.2. If you are upgrading from version 1.3, you should also consult upgrading document. See also Overview of new features in Apache 2.2 Compile Time Configuration Changes The compilation process is very similar to the one used in version 2.0. Your old configure command significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: mod_imap has been renamed to mod_imagemap

find more information in either the New Features document, or in the src/CHANGES file. This document describes only the changes from 2.0 to 2.2. If you are upgrading from version 1.3, you should also consult upgrading document. See also Overview of new features in Apache 2.2 Compile Time Configuration Changes The compilation process is very similar to the one used in version 2.0. Your old configure command significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: mod_imap has been renamed to mod_imagemap

find more information in either the New Features document, or in the src/CHANGES file. This document describes only the changes from 2.0 to 2.2. If you are upgrading from version 1.3, you should also consult upgrading document. See also Overview of new features in Apache 2.2 Compile Time Configuration Changes The compilation process is very similar to the one used in version 2.0. Your old configure command significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: mod_imap has been renamed to mod_imagemap

more information in either the New Features (p. 4) document, or in the src/CHANGES file. This document describes only the changes from 2.0 to 2.2. If you are upgrading from version 1.3, you should also consult document.1 See also • Overview of new features in Apache 2.2 (p. 4) Compile-Time Configuration Changes The compilation process is very similar to the one used in version 2.0. Your old configure command significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: • mod imap has been renamed to MOD IMAGEMAP

Features document, or in the src/CHANGES file. Application and module developers can find a summary of API changes in the API updates overview. This document describes changes in server behavior that might advantage of new features in 2.4, see the New Features document. This document describes only the changes from 2.2 to 2.4. If you are upgrading from version 2.0, you should also consult the 2.0 to 2.2 upgrading document. See also Overview of new features in Apache HTTP Server 2.4 Compile Time Configuration Changes The compilation process is very similar to the one used in version 2.2. Your old configure command

find more information in either the New Features document, or in the src/CHANGES file. This document describes only the changes from 2.0 to 2.2. If you are upgrading from version 1.3, you should also consult upgrading document. See also Overview of new features in Apache 2.2 Compile Time Configuration Changes The compilation process is very similar to the one used in version 2.0. Your old configure command significant change required will be to account for changes in module names, in particular for the authentication and authorization modules. Some details of changes: mod_imap has been renamed to mod_imagemap

Features document, or in the src/CHANGES file. Application and module developers can find a summary of API changes in the API updates overview. This document describes changes in server behavior that might advantage of new features in 2.4, see the New Features document. This document describes only the changes from 2.2 to 2.4. If you are upgrading from version 2.0, you should also consult the 2.0 to 2.2 upgrading document. See also Overview of new features in Apache HTTP Server 2.4 Compile Time Configuration Changes The compilation process is very similar to the one used in version 2.2. Your old configure command

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915 11.3 API Changes in Apache HTTP Server 2.4 since 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . 931 11.4 Developing document, or in the src/CHANGES file. Application and module developers can find a summary of API changes in the API updates (p. 931) overview. This document describes changes in server behavior that advantage of new features in 2.4, see the New Features document. This document describes only the changes from 2.2 to 2.4. If you are upgrading from version 2.0, you should also consult the 2.0 to 2.2 upgrading