I've just completed the presentation of a LAMP deployment course
, teaching Linux - Apache - MySQL - PHP and on one of the machines we built (compiled from scratch) the very latest Apache httpd - version 2.2.0. With a major new release of a product, there's always a "what's changed" concern at build (and run) time ... I noted:
a) Installed server pointed just to a page that said "It works" rather than to a more formal page. I'm happy with this - having a formal page made it look like a real web site and not an in-progress setup
b) The configuration files for certain features have been split off into extra files that are included and the whole of each of the includes can be commented in / out. Another good move.
c) There's a backup (a directory called original) of the shipped httpd.conf and extra friends. Yet another step forward; the first thing I've always had to remember in the past is to take a safety-net copy of the config before I start messing (as one does on a course!) with it.
d) The server is configured to start up as user daemon and group daemon. We change this to user and group apache, but I'm still glad to see the change away from more dangerous accounts such as nobody which has / had a security issue if you were also running things like an NFS server.
During the compile (on Red Hat Fedora 3) the compile hung at one point; I changed the configuration option for the compiler from -O2 to -O1 (a very old trick indeed that one - learnt 20 years ago) and it went through on the second attempt. Possibly just a "core 3" issue.
Note - this was a quick and dirty test / install - I cannot report on details of how the new release runs in a production environment or how any of the options / modules go. We tested straightforward web pages, Perl scripts through CGI, users home directories through ~username. Oh - and we also installed PHP 5.1.1 and MySQL support (running 5.0.16) which went fine just by following the instructions for "Apache 2.0". Having our fingers crossed helped us as we did this, but I don't think it made any difference to how the system worked.
For Tomcat / Java users, I see that mod_jk and the AJP connector are now part of the standard server that's downloaded, although the course completed did NOT include Apache Tomcat for once, so I didn't have a chance to verify / first test that part. From a user's perspective, THANK GOODNESS for this addition as it's been a nightmare for as long as I can remember to find exactly the right version of the connector - especially if you happen to be installing from binary. (written 2005-12-10, updated 2006-06-05)
Associated topics are indexed underA602 - Web Application Deployment - Apache httpd - Sourcing, Installation, Testing 
Automed web site testing scripted in Ruby using watir-webdriver - (2011-09-09) 
Global and Enable - two misused words! - (2009-11-30) 
Choosing the right version of Java and Tomcat - (2009-05-16) 
Where is my new Apache httpd installed - (2009-03-22) 
Using ApacheBench and jconsole to test and monitor Tomcat - (2009-03-14) 
Summary - Apache httpd build on Linux - (2008-12-14) 
What is built in to this httpd and PHP? - (2008-08-23) 
Apache httpd, MySQL, PHP - installation procedure - (2008-08-01) 
Configuring Apache httpd - (2008-07-12) 
Connecting to MySQL 5 from PHP on Mac OSX Leopard - (2007-12-03) 
Upgrade Mac OSX to Leopard, Web Server Apache httpd config lost - (2007-11-29) 
DHCP automatic IP address v Static IP - (2007-08-06) 
Apache httpd , browser, MySQL and MySQL client downloads - (2007-02-28) 
Notes from the white board - (2006-12-14) 
Browser -> httpd -> Tomcat -> MySQL. Restarting. - (2006-10-28) 
Stopping and restarting Apache httpd cleanly - (2006-03-29) 
2006 - Making business a pleasure - (2006-01-01) 
Apache httpd - serving web documents from different directories - (2005-12-12)
Some other Articles